Who you are trusting.

Webcuris asks you to point a scanner at systems you care about, and sometimes to connect a read-only credential to a cloud account. Every one of those is a decision about trusting whoever runs it. This page is that answer, and nothing else.

The operator

This deployment has not named its operator.

No operator has been configured for this deployment, so this page cannot tell you who runs it. That is a real gap, not a formatting choice — and you should weigh it accordingly before connecting anything.

An operator sets OPERATOR_LEGAL_NAME or OPERATOR_NAME, SECURITY_CONTACT_EMAIL in the deployment environment.

No accountable person is named anywhere on this deployment, under either role.

What we claim, and where to check it

Every claim on this site points at its own evidence.

A security vendor asking to be trusted should be checkable rather than reassuring. These are the four claims that matter most, each with the page that lets you verify it — including the one that lists what this product cannot do.

Every finding carries a confidence level

Visible on any scan result and in every export.

What confidence means

The limitations are published before you sign up

No SOC 2, no third-party penetration test, compliance mappings are context rather than audit evidence.

Security Policy

Scanning is authorised, and passive by default

Checks that go beyond an ordinary browser visit stay locked until domain ownership is proven.

What runs against what

What is stored, and for how long, is written down

Including commit author names read from scanned repositories — data about people who never signed up.

Privacy and retention
What we are not

Small, and not pretending otherwise.

Webcuris is not a large security organisation, and the site does not imply one. There is no SOC 2 report, no third-party penetration test of this service, and no 24/7 response desk. Those are stated here and on the Security Policy because you would find out eventually, and finding out later is worse for both of us.

What it does have is a scanner that says how sure it is, limitations written down in advance, and a named person to complain to. For a great many teams that is a better trade than a louder tool that is confident about everything.

Contact

Talk to us.

Questions about what the engine checks, whether it fits your estate, or what it deliberately refuses to do. A person reads every message.

  1. 01You writePlain form, no qualifying call, no obligation. The marketing checkbox is optional and unticked.
  2. 02A person reads itMessages land with the team, not a queue-bot. Nothing is auto-replied.
  3. 03You get an answerTo the address you gave — including “this product is not the right fit”, when that is the honest answer.
Prefer email?
Use the form — no address is published on this deployment.
Reporting a vulnerability?
Read the disclosure policy first — it tells you what is in scope and what to expect.
New messagereplies go to your email

Personal addresses (gmail, outlook, and similar) are not accepted.

+91

0 / 4000