Security headers checker

Fetch a public URL and grade its HTTP security headers, from Strict-Transport-Security and CSP through framing, MIME-sniffing, referrer and permissions policies.

The check runs from this server. Only public http and https sites on ports 80 and 443 are allowed.

Which headers are graded

The checker fetches a public http or https URL from this server (ports 80 and 443 only), follows up to five redirects, and looks at the final response headers:

Private and local addresses are blocked, as with the other HTTP tools. For certificate expiry see the SSL checker.

Frequently asked questions

What are HTTP security headers?

They are response headers that tell browsers how to treat a page: whether to force HTTPS (HSTS), which scripts may run (CSP), whether the page may be framed, whether to MIME-sniff, how much referrer data to send, and which browser features the page may use.

How is the A–F grade calculated?

Six checks are scored: Strict-Transport-Security, Content-Security-Policy, X-Frame-Options (or CSP frame-ancestors), X-Content-Type-Options, Referrer-Policy and Permissions-Policy. Each is pass, weak or fail (HSTS is skipped on a plain HTTP final URL). The score is the average of those checks: A is 90 or above, B 80, C 70, D 60, and F below 60. A weak value counts as half a pass.

What is a good HSTS value?

On HTTPS, a useful starting point is Strict-Transport-Security: max-age=31536000; includeSubDomains. max-age is in seconds; 31536000 is one year. preload is optional and should only be added if you understand the HSTS preload list. HSTS is ignored if the page is served over HTTP.

Does a good grade mean the site is secure?

No. Headers are only one layer. This grade describes the final response this server received, after following redirects. It does not test cookies, TLS configuration beyond the connection, or whether a CSP actually matches the page’s scripts.