← Blog

Your scan result belongs to the domain, not to you

Scan a domain, close the tab, send the link to a colleague -- and until recently the colleague got a bare form, not your result. Only logged-in users who had saved a domain got a stored result; anonymous scans lived in a browser session and died with it. If a hundred people scanned the same domain in an hour, we probed that server a hundred times and remembered nothing.

The scan results are tied to the domain, not to the user
The scan results are tied to the domain, not to the user

That's last decade. That's backwards. A real health check measures the domain, not the person asking. SSL Labs and urlscan figured this out years ago -- the result belongs to the domain.

One living result per domain

Every completed standard scan now writes a canonical per-domain report: one row per domain holding the latest usable result, stamped with the time the scan finished. Open /?domain=example.com -- logged in or not -- and you see it, with the age shown right in the banner: "cached result from 14:32 (12m ago)". No pretending it's fresh.

Anonymous scans finally survive too. The domain doesn't care who asked -- the scan ran, so the result exists. Once again, the result belongs to the domain, remember? A saved user's per-owner copy still keeps your private history; the canonical page is the public, shared truth.

What never lands in the store

A few rules keep the results consistent:

One scan serves everyone, for 15 minutes

If you need to scan it a lot, then verify it, otherwise wait for cooldown
If you need to scan it a lot, then verify it, otherwise wait for cooldown

Rescans are throttled per domain, not per person. Inside the rescan window (default 15 minutes) a new submit gets the stored result with a "rescans allowed every 15 minutes" note -- a popular domain costs one scan per interval, not one per click. Verified owners of the domain skip the throttle entirely: prove it's yours and the "Run live check" button really means now. But only if you have an account and you verify the domain. If you are developing and debugging a website, get an account and verify -- it's free for one domain!

Frozen snapshot vs living document

Snapshot any scan and share it if you like
Snapshot any scan and share it if you like

Two link types, two different promises. /?s=<token> shares are immutable snapshots -- byte-identical to what you saw, revocable, forever frozen at that moment. ?domain= is the living page: same result today, newer result tomorrow when someone rescans. Share the snapshot when "look at this exact failure" is the point; link the domain when "see how it's doing" is.

Is your site OK? Run a free health check — HTTP, HTTPS, TLS, DNS, mail security and more in seconds. Check a domain →