Is there actually a website at that address?
A parked domain, a security challenge, a builder’s placeholder and an empty shell all answer 200 OK. Audit tools happily produce a full report about every one of them. This asks the question first.
Useful before you pay anyone to look at a site — yours, a competitor’s, or one you have just been handed.
A domain or a full address. Both work.
Why this is worth thirty seconds. It is not hypothetical. This engine once produced 76 findings about a domain that was for sale and 38 about a page nobody had looked at, and three real florists were audited as somebody’s block page. Every one of those reports was tidy, internally consistent and about nothing.
What this is not. One fetch and a handful of facts. The audit itself runs a ten-rung refusal ladder on the raw response, the rendered page and the redirect chain, and this deliberately does less rather than approximating it. Where the two disagree, the audit is right.
Nothing is stored. The address is fetched from this site rather than from your browser, so your browser never talks to the site you are checking, and the address you type is not saved or logged by us.
A site that refuses us is telling you something. If the answer
is a challenge page or a timeout, that is worth knowing on its own:
whatever turned us away is turning away some proportion of whoever else
arrives that way. One live site answered us with an anti-robot page at
403, and an hour later with its real article — and during the first
spell the same product was serving its own /robots.txt
containing Disallow: /. Both are invisible from inside the
site. The robots check reads
that one; run either again later if the answer surprises you.