Interpret the four checks in a security header report
Admin ·
Give the checker enough context to identify the final transport. Read the evidence rows alongside the grade so that an unavailable or custom setting stays visible.
Work through four configured fields
For an HTTPS response, use Strict-Transport-Security: max-age=86400, X-Content-Type-Options: nosniff, X-Frame-Options: DENY and Referrer-Policy: no-referrer. Each field satisfies its respective check and the grade is A. A zero max-age removes the HSTS point.
IETF RFC 6797 — HTTP Strict Transport SecurityW3C Referrer Policy
Interpret framing and referrer results
An enforced frame-ancestors rule limited to self or none earns the framing point. When no such directive is present in enforced policies, one DENY or SAMEORIGIN X-Frame-Options field qualifies. A custom ancestor list is marked for review. The referrer check accepts no-referrer, same-origin, strict-origin or strict-origin-when-cross-origin as the last recognized token.
Use a finding to locate the right configuration
Check whether the saved final response was an HTML page, an error page or a static asset. Different response paths can have different header settings. A finding from one captured path should be retested on the specific route whose behavior matters.
After changing configuration, compare a new saved capture with the old one and inspect the exact field values. A higher header score does not test application logic, access control or the content of a page.
Common questions
Does a report-only CSP satisfy the framing check?
Only an enforced Content-Security-Policy contributes a frame-ancestors rule here. Report-only policies describe observations.
Will omitting a referrer header always expose a full URL?
A browser may apply its own default. This check records whether the captured response explicitly declares one of its four qualifying policies.
Sources
Put it into practice.
Related guides
- Read a saved HTTP response header dump
- Read recorded redirect hops
- Compare recorded response headers
- Test a CSP in Report-Only and Enforce Modes
- Check Recorded Browser Feature Allowlists
- Check a Saved Frame Ancestor Chain
- Compare Referrer Disclosure Across Origins
- Trace HSTS Preload and Saved Header Evidence
- Check Version Details in Saved Server Headers