HTTP Security Headers Scanner
Scan a site for HSTS, CSP, X-Frame-Options and X-Content-Type-Options.
What is HTTP Security Headers Scanner?
HTTP security headers let a website set browser-side protections. This scanner checks Strict-Transport-Security (HSTS), Content-Security-Policy (CSP), X-Frame-Options, and X-Content-Type-Options on the HTTPS response.
What this check looks for
HSTS tells browsers to use HTTPS for future visits. CSP limits which sources can provide scripts and other page content. X-Frame-Options can prevent other sites from embedding a page, and X-Content-Type-Options: nosniff stops browsers from guessing a response's file type. These controls are delivered in HTTP response headers and should be tested on the final, redirected page.
Why Headers matters
A missing header removes a layer of protection against a specific class of browser attack. For example, framing restrictions can help prevent clickjacking, while a carefully designed CSP can limit the impact of injected content. Headers are not a substitute for fixing application vulnerabilities, and overly strict values can break legitimate site features.
How to fix it
Set the headers at the web server, application, or CDN layer so they appear on the final HTTPS response. Start with a CSP that matches the scripts, styles, and services your site actually uses, then test it before enforcing a stricter policy. Enable HSTS only after HTTPS works across the affected hostnames. Recheck the live response after deployment because a proxy or redirect can change which headers reach visitors.
Example configuration
Strict-Transport-Security: max-age=31536000; includeSubDomains Content-Security-Policy: default-src 'self' X-Frame-Options: DENY X-Content-Type-Options: nosniff