Security Header Audit
Check CSP, HSTS, framing, MIME, referrer, and permissions headers.
Read the guideRun the tool
JVR Software’s server processes the public target you enter. The diagnostic is rate-limited. Use a system you own or are authorised to check.
More information
Back to the toolWhat it is and when to use it
Security Header Audit checks six response headers commonly used to control browser behaviour on a site you operate. It can help you review a deployment, put a missing header on a maintenance list, or compare a public page with your own documented configuration. It is a presence check with displayed values.
How it works
The report checks Content-Security-Policy for resource rules, Strict-Transport-Security for HTTPS enforcement, X-Content-Type-Options for MIME sniffing, X-Frame-Options for framing, Referrer-Policy for referring URL detail, and Permissions-Policy for browser feature access. Browsers can also enforce a CSP frame-ancestors rule.
How to use it
- Enter the authorised HTTPS URL that visitors actually use.
- Run the check and read the values as well as MISSING markers.
- Compare the result with your approved settings and confirm changes on a representative set of pages before rolling them out.
Worked example
A page missing X-Frame-Options may already have a restrictive CSP frame-ancestors directive. Read the CSP value, then test whether an intended embed still works. A missing slot in this report does not automatically mean a browser has no framing protection.
Reading the result
MISSING means the named header was absent in the recorded response. A present value can still be too broad, configured for the wrong host or incompatible with an application. Security needs differ between a public marketing page and a page designed to be embedded.
Review directives alongside the pages people actually use. A policy that suits a simple landing page may block a payment or embedded media screen. Check representative page types and browser errors in staging before enforcing stricter values across the whole site.
Common mistakes and limits
This page does not discover vulnerabilities or certify that a site is safe. It observes one public response from one location. Evaluate policy directives in context, and test legitimate scripts, embeds and sign-in flows after changing browser policies.
