Check explainer · v1
Security headers: the four response headers beyond HSTS and CSP
Last reviewed
HSTS, CSP and framing get the headlines. Four quieter headers limit MIME sniffing, referrer leaks, browser features and cross-origin window access.
How this check works
One response-header grade covers four defence-in-depth headers. The page warns when any of x-content-type-options, referrer-policy, permissions-policy or cross-origin-opener-policy is missing, and the finding names each missing header. All four present passes; when the response headers are unavailable altogether the result is na (insufficient_signal). The rule never fails a page. HSTS, Content Security Policy and framing have their own explainers — the related links below open them.
What does a failure look like?
A CDN that strips x-content-type-options from every response; an application that ships CSP but no referrer-policy; a permissions-policy defined only on the marketing host while the app host omits it; a cross-origin-opener-policy missing after a proxy rewrite — each warns with the missing name.
How to fix it, step by step
- Send x-content-type-options: nosniff and a referrer-policy on every response, including CDN and app hosts.
- Send a permissions-policy limited to the features you actually use, and cross-origin-opener-policy: same-origin where cross-origin window access is not required.
- Re-run the audit and confirm all four header names appear on the representative response.
What does a pass or fail look like?
Good
One response carries x-content-type-options, referrer-policy, permissions-policy and cross-origin-opener-policy — the grade passes.
Fail
The origin sends HSTS and CSP but omits x-content-type-options and referrer-policy — two of the four names are reported missing.
Frequently asked questions
Does one missing header make the site exploitable?
No. These four are defence-in-depth: a missing header removes a limit the browser could have enforced, but the audit does not claim that alone makes a page attackable. Fix the names together and keep HSTS, CSP and framing in place.
Does this page generate a policy for me?
No. It explains what each header does and reports which names are missing; it is not a policy generator. The right values still depend on your hosts, CDN and the browser features the page uses.
Why do these warn while HSTS, CSP and framing fail?
HSTS, CSP and framing are graded as hard security checks. These four are defence-in-depth recommendations, so a missing name is a warning rather than a failed page.
This rule is one of the checks the page scan runs. Run the free page scan
Free preview; no account needed.