Check HTTP response headers for browser security protections and weak directives.
The frame below runs the same code as this page, in the reader's own browser. Nothing is sent to us, and nothing is sent to you.
Pick a dark background and the text and panels follow it, so the frame stays readable on a dark page.
Captured headers are compared with transport, sniffing, framing, referrer, permissions, and content-security checks; findings identify missing, weak, or conflicting directives. The checker evaluates headers and does not change a server.
Strict-Transport-Security: max-age=31536000 X-Content-Type-Options: nosniff X-Frame-Options: DENY Content-Security-Policy: default-src 'self'
Security Headers Analysis
Score: 55/100 (Grade: D)
Present: 4/11
Details:
[+] content-security-policy: default-src 'self'
PRESENT - Prevents XSS and data injection attacks
[+] strict-transport-security: max-age=31536000
PRESENT - Forces HTTPS connections
[+] x-content-type-options: nosniff
PRESENT - Prevents MIME type sniffing
[+] x-frame-options: DENY
PRESENT - Prevents clickjacking
[-] x-xss-protection
MISSING (optional) - Legacy XSS filter (deprecated)
[-] referrer-policy
MISSING (recommended) - Controls referrer information
[-] permissions-policy
MISSING (recommended) - Controls browser features
[-] cross-origin-opener-policy…
Production audits, preview CI, and penetration-test reviews check security headers.