About the Quiet Watch scanner

You are probably here because you saw leak-scanner in your server logs. Here is exactly what it is and how to make it stop.

What it does

Quiet Watch runs a read-only check that looks for website faults the owner usually cannot see from their own desk: expired certificates, a domain about to lapse, mail records pointing at a dead host, a contact page returning 404.

When we find something serious we may email the business once to tell them. That is the whole purpose.

What it never does

✗	Submit a form, or send any POST request whatsoever
✗	Log in, create an account, or touch a payment page
✗	Add anything to a cart or complete a checkout
✗	Scan for vulnerabilities or attempt any exploit
✗	Collect personal data about your customers

It reads publicly available pages, exactly as a search engine does. Active checks such as testing whether a contact form truly delivers are only ever run for paying clients who have signed a written authorization naming their own domain.

How politely

• Obeys robots.txt, including Crawl-delay
• At most one request every 2 seconds to any one site
• At most 25 pages per site, two links deep
• Identifies itself honestly in the User-Agent, with a link to this page

In practice a full check is a few dozen requests spread over a couple of minutes. You should never notice it.

Data we hold

Your domain name, the public DNS and HTTP responses we observed, and any business contact details already published on your own website or in OpenStreetMap. Nothing else. Ask and we will tell you precisely what we have, or delete it.