FREE WEBSITE TOOL
Security headers checker
Review the browser protections returned with your page. See the exact header values and a practical interpretation for each one.
What is checked
The checker fetches a public page response and reads HSTS, Content Security Policy, MIME sniffing protection, Referrer Policy, Permissions Policy, Cross-Origin Opener Policy and frame protection. The values are shown alongside a plain-language purpose and suggested next step. This makes it possible to inspect whether a header is absent and whether a declared value appears to fit the actual site.
How to read the result
A present header is useful evidence, but its presence alone does not prove an effective configuration. For example, a Content Security Policy can be overly permissive or break scripts the site relies on. Changes to HSTS should be planned after HTTPS works across the relevant hosts. A missing optional policy may be lower priority than an insecure checkout or a broken form. Review the effect of each change in a real browser.
Manual verification and limits
This is a response-header snapshot, not a vulnerability scan, penetration test or security certification. It does not validate every policy directive or reproduce user-specific responses. The worker fetches public resources and may see different headers from an authenticated visitor. Test important pages and forms after changing a policy. Keep the exact value and timestamp with a release record to simplify troubleshooting.
Save evidence of a fix
A completed check is saved to this browser's workspace, where you can view the snapshot or run it again. Export the result as JSON or CSV for a release record. Browser snapshots do not trigger automatic monitoring, and clearing browser data removes them.
Open browser workspace →
Common questions
Does a pass certify the website is secure?
No. It confirms that selected headers were detected in this response. Their effectiveness and the rest of the application require a broader review.
Does this tool make changes to my website?
No. It reads public information and shows what was observed. Review the next step before changing site or DNS configuration.