Nomlen logo
Free security audit· A–F grade in seconds

Security headers checker with an A–F grade

Fetch any server's live response headers, grouped and graded — with a security-header score at a glance.

Live fetchSecurity header scoreNo login needed
Inspect any site’s response headers
Try github.com, cloudflare.com, or your own site.
What you get

See what attackers see, fix what matters

One audit grades your headers and tells you exactly what to add.

A–F security grade

Get an instant A–F grade summarising your header posture, so you can benchmark progress as you harden your site.

HSTS and CSP checks

Verify the headers that matter most — Strict-Transport-Security, Content-Security-Policy and more — with pass/fail detail on each.

Full response-header audit

Every response header is listed and explained, including the informational ones, so nothing hides in your server's replies.

Missing-header fixes

Each missing or weak header comes with the exact header to add, so your developers can implement fixes without research.

Stop second-guessing.

Find your domain in the next 30 seconds.

Free forever. No login required. 1,100+ TLDs in one query — plus AI suggestions and the premium marketplace.

1,147
TLDs
200ms
Avg lookup
100
Suggestions/query
FAQ

Security headers checker FAQs

Security headers are response headers that tell browsers how to defend your page — the essentials are Strict-Transport-Security, Content-Security-Policy and X-Frame-Options. This checker scores your site on each and flags what is missing. All three take minutes to configure and are checked automatically on this page.
They switch on free browser defenses against clickjacking, cross-site scripting and protocol downgrades. Missing headers do not guarantee a vulnerability, but they remove protection layers that cost nothing to add and take minutes to configure. Run this checker after deploying to confirm each header is actually being sent.
It tells browsers to only ever load your site over HTTPS for a set duration — even if a user types http://. That closes the window for downgrade attacks on the very first request to your domain. Include subdomains in the policy once you are confident the main domain is stable.
No. A static marketing page has different needs than a banking app. Treat the score as a prompt to double-check intent — add the headers your site's risk profile justifies, and document why the rest are skipped. Re-check after every major deploy, since headers are easy to drop accidentally.
Content-Security-Policy-Report-Only lets you test a policy without blocking content. The browser evaluates the rules and can send violation reports, but it does not enforce them. This is the safest way to discover which scripts, styles, fonts and connections a new CSP would break before switching to the enforcing Content-Security-Policy header.
Without nosniff, some browsers may guess a file's content type instead of trusting the declared type. That MIME-sniffing behavior can turn a file that was supposed to be an image or download into executable content in the wrong context. Setting X-Content-Type-Options: nosniff is a small, low-risk defense, provided your server already sends correct Content-Type values.
No. Security headers reduce several browser-side attack surfaces, but they do not patch vulnerable software, weak passwords, broken access control, exposed backups or injection flaws. Treat a strong grade as evidence that one layer is configured well, then continue with updates, least-privilege accounts, backups and application-level security testing.