Domain ownership verification
Why we ask for it, what a public scan does, and what changes once a domain is verified.
1. Why verification exists
Scanning a site you do not control can cross the line from reading public information into unauthorised testing. We therefore run passive, read-only checks by default, and only enable active probes after the person requesting the scan demonstrates control of the domain. Verification is a safeguard for site owners as much as for us.
2. What an unverified (public) scan does
A public scan reads a single homepage, public DNS / TLS / RDAP records, response headers, and crawler-published files such as robots.txt, sitemap.xml, favicon.ico and llms.txt. It does not:
- probe sensitive paths (.env, .git, backups or admin login pages);
- connect to non-web ports, enumerate subdomains, or probe HTTP methods;
- re-fetch pages with a spoofed search-engine user agent, or send bulk link-check requests;
- crawl beyond the public page cap, or ignore robots.txt disallow rules.
Requests use an identifiable user agent with a contact link, are rate-limited per IP and per target domain, and are recorded in an internal scan log. Checks that require authorisation appear in the report as skipped — ownership verification required, never as a passed check.
3. The three verification methods
Pick whichever is easiest. The token is unique to your browser session and shown on the scan page.
- DNS TXT: add a TXT record at
_auditcheck.<your-domain>with the valueauditcheck-verify=<token>; - Verification file: create
/.well-known/auditcheck-verify.txtat the web root containing only the token; - Meta tag: add
<meta name="auditcheck-verify" content="<token>">to the homepage <head>.
The challenge expires after a few days. A completed verification is valid for a limited period, is bound to your browser session, and covers the domain and its subdomains. Clearing cookies or switching devices means verifying again, or using the manual approval route below.
4. What changes after verification
Active checks and full-site crawling (up to the authenticated page cap) become available for that domain. Findings remain informational and the report is still not a penetration test, security certification or compliance attestation. We never attempt to log in, bypass access controls, modify data, or test credentials.
5. What we store, and how to opt out
Verification stores only the domain, token, matched method, timestamps and a short session identifier — no page contents. If you operate a site and do not want it checked at all, email security@auditcheck.site with the hostname: we will add it to a suppression list and delete stored reports on request. If you cannot modify DNS or upload a file, contact support@auditcheck.site with evidence of authorisation for a manual approval. All approvals and revocations are recorded in an administrator audit log.
Last updated / 最后更新:2026-11-15 · auditcheck.site