HTTP Security Headers Grader
Enter a URL to grade nine HTTP security headers, with a score from 0 to 100 and a letter grade from A+ to F.
What it checks
- Strict-Transport-Security: present, max-age of at least six months, and includeSubDomains
- Content-Security-Policy: missing fails; no script directive, or unsafe-inline / unsafe-eval applying to scripts, warns
- X-Content-Type-Options set to nosniff, and frame protection through CSP frame-ancestors, otherwise X-Frame-Options DENY or SAMEORIGIN
- Referrer-Policy, Permissions-Policy and Cross-Origin-Resource-Policy: checked for presence
- Cross-Origin-Opener-Policy set to same-origin, and X-Powered-By and ASP.NET version headers checked
How to read the result
- Each check is pass, warn or fail. A warn earns half of the check's weight, so a missing HSTS or CSP costs more than a missing Referrer-Policy.
- Letter grades: A+ from 95, A from 85, B from 70, C from 55 and D from 40. Anything lower is F.
- A high grade shows that these headers are set. It does not mean the application is free of vulnerabilities.
What it does not tell you
The grade covers nine headers from one GET request, following redirects. It does not check CORS, cookies or the rest of your CSP, and it does not test the application. The Server header is not graded, because this tool's requests leave through Cloudflare, which replaces it. This is not a penetration test.
Data sources
Response headers from one live HTTPS GET request made by the tool; the host is checked for public addresses before the request and any redirect target is checked after it.
No login · 30 calls / hour / IP · Data stored in the EU
FAQ
Why did my grade drop after adding a CSP?
The check reads the enforced policy only. Inline scripts are judged on script-src-elem and script-src-attr, which fall back to script-src and then default-src; eval is judged on script-src, then default-src. A policy scores as warn, which earns half the points, if it has none of these directives or if the list allows unsafe-inline (unless a nonce, hash or strict-dynamic is also present) or unsafe-eval. unsafe-inline in style-src does not count. Host allow-lists and wildcards are not evaluated, and a Report-Only policy is ignored.
Does this tool check cookies or CORS?
No. The separate cookie checker covers cookie flags. CORS headers are not checked by any tool on this page.
Go deeper: Web Pentest engine (OWASP Top 10 and configuration checks)
Guide: Security Headers: From Grade F to A Without Outages