Scanning
Reading the report
The hacker steps, what to do first, the developer section, "not checked" and rescan comparisons.
Every report has the same shape, so you and your agent always know where to look. You can read it on the scan page or download it as Markdown.
Sections
- Verdict. One line: Not safe: fix now, Needs work or No urgent problems found, and why, in plain words.
- What to do first. Up to three things, most urgent first.
- How a hacker would attack your site. Eleven steps, in the order a hacker takes them. Each one says what a hacker tries and which tools they use, what we did the same way, what we found (what it means for you and what to do), and which checks passed. Steps that need a verified domain say so.
- Software we found. Every product and version, with a status and the public source to check it yourself.
- For your developer. For each finding: the evidence we saw, the exact fix (config lines or code for the setup we detected) and how to check it, plus a ready prompt for Claude Code, Codex or Cursor. On the scan page this part is folded away.
- Exactly what we did and what we did not try. Request counts, data sources and the limits of an outside scan.
- Every check we ran. A table with each check's result.
Severities
| Severity | Meaning | Example |
|---|---|---|
| Critical | Fix today. Secrets or data are exposed right now. | Downloadable .env file or database dump |
| High | Fix this week. Direct path to a serious attack. | Exposed .git folder, public phpMyAdmin |
| Medium | Missing protection that makes common attacks easier. | No Content-Security-Policy, TLS 1.0 still accepted |
| Low | Worth fixing, small risk on its own. | Missing Referrer-Policy, no CAA record |
| Info | Good practice, no direct risk. | No security.txt |
“Not checked” is not a pass
If a check could not finish, for example because a request timed out or was blocked by a firewall, it is listed as not checked. We never treat missing information as safe, and the report never says your site is “secure”.
Rescan comparison
When you rescan a site, the new report starts with Compared with your previous scan:
- Fixed: found last time, gone now, and the check ran properly.
- Still open: found both times.
- New: not there last time.
- Could not recheck: gone, but its check did not complete this time, so we cannot call it fixed.
Finding IDs (such as hsts-missing) stay the same between scans, so agents can match them reliably.