HTTP Security Headers Checker
Check four response-header settings locally. See the evidence for HSTS, nosniff, framing and referrer policy, with a grade based on four documented checks.
Interpret a security header grade
HTTP Security Headers Checker: how to use it
- Paste saved response headers with the status line. Supply the starting URL when known.
- Select Review security headers. Read the evidence for each of the four checks.
- Use the report to review the captured configuration in the context of this resource.
Limits and notes
Paste HTTP/1.0, HTTP/1.1, HTTP/2 or HTTP/3 status lines followed by one field per line. Each capture supports 100 response blocks, 5,000 fields and one million characters. The grade assigns one point per documented check on the last recorded response. Unknown transport, custom framing allowlists and missing explicit policies need review. This limited grade cannot establish site security.
How your privacy works →HTTP Security Headers Checker: common questions
How is the header grade calculated?
Each of four documented rules earns one point. Grades A, B, C, D and F represent four, three, two, one and zero points respectively.
Why does HSTS need a starting URL?
The HSTS observation uses the inferred transport of the final response. Provide an HTTPS starting URL or an earlier absolute redirect to establish that transport.