HTTP Security Header Checker

Audit pasted response headers locally for common browser security protections

Response headers

Paste raw HTTP response headers, one Name: Value pair per line.

Privacy: headers are parsed only in your browser. No network requests are made.

Security header audit

7 issues (2 critical)

Strict-Transport-Security

HSTS is missing, so browsers are not instructed to keep future requests on HTTPS.

missing

Content-Security-Policy

CSP is missing, leaving script and resource loading without a browser-enforced allowlist.

missing

X-Frame-Options / CSP frame-ancestors

Add X-Frame-Options or a CSP frame-ancestors directive to reduce clickjacking risk.

missing

X-Content-Type-Options

Add X-Content-Type-Options: nosniff to prevent MIME type sniffing.

missing

Referrer-Policy

Set a referrer policy to control which URL details are sent with outbound requests.

missing

Permissions-Policy

Add Permissions-Policy to restrict features such as camera, microphone, and geolocation.

missing

Cross-Origin-Opener-Policy

Add COOP to isolate the browsing context from untrusted cross-origin windows.

missing

About this tool

HTTP security headers activate browser defenses that ordinary application code cannot replace. They can pin future requests to HTTPS, restrict script and resource loading, prevent unauthorized framing, disable MIME sniffing, limit referrer data and powerful browser features, and isolate pages from untrusted cross-origin windows.

This checker audits seven common controls from a raw response-header block: Strict-Transport-Security, Content-Security-Policy, X-Frame-Options or CSP frame-ancestors, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, and Cross-Origin-Opener-Policy. It distinguishes a missing header from a weak value, such as a short HSTS max-age, CSP unsafe-inline or unsafe-eval, an ineffective X-Content-Type-Options value, or a non-isolating COOP policy.

The tool does not fetch your site. Parsing and auditing happen entirely in the browser, so you can safely paste headers copied from developer tools, curl, a private staging environment, or an internal application. Treat the findings as a focused baseline and test policy changes against your application before deploying them broadly.

How to use

  1. Paste response headers

    Copy a raw HTTP response-header block from developer tools or curl and paste one Name: Value pair per line.

  2. Review the summary

    Read the live issue and critical counts, then inspect every present, missing, or weak finding.

  3. Fix and recheck

    Update your server configuration, copy the new response headers, and paste them again until the intended protections show as present.

Audited protections

HeaderProtection
Strict-Transport-SecurityHTTPS enforcement and downgrade resistance
Content-Security-PolicyResource allowlisting and script-injection mitigation
X-Frame-Options / frame-ancestorsClickjacking protection
X-Content-Type-OptionsMIME sniffing prevention
Referrer-PolicyOutbound referrer-data control
Permissions-PolicyBrowser capability restrictions
Cross-Origin-Opener-PolicyCross-origin window isolation

The checker audits pasted text locally and makes no network requests.

Frequently asked questions