Skip to main content

Free Security Headers Checker

Inspect the headers returned by a public URL. See published policy values, missing headers, and configuration findings, then decide which changes fit your application.

Free to use — no signup required. Public demo limit: up to 2 requests per five minutes per IP, shared with the playground.

How to Review Security Headers

Headers belong to a particular HTTP response. Test the paths and environments that matter to your application.

  1. 1

    Enter a public URL

    Choose HTTP or HTTPS and include the path you want to inspect. The checker does not send your browser cookies or sign in to the target.

  2. 2

    Check the final response

    The default check follows redirects. Read the final URL and status before interpreting the returned headers; an error page can have different policies.

  3. 3

    Review values and recommendations

    Check existing policy values as well as missing headers. Presence alone does not show that a policy protects the application as intended.

  4. 4

    Retest a controlled change

    Review recommendations with the application owner, test compatibility, deploy through your usual process, and repeat the check for relevant paths.

What the Main Headers Do

Content-Security-Policy (CSP) can restrict resource sources and other browser behavior. Strict-Transport-Security (HSTS) tells browsers to use HTTPS for future requests within its scope. X-Content-Type-Options: nosniff limits MIME-type guessing, while framing policies help control which pages can embed your content.

Referrer-Policy and Permissions-Policy control different browser disclosures and capabilities. Use OWASP’s Secure Headers guidance when choosing values for your application, rather than copying another site’s policies unchanged.

A Missing Header Needs Context

A diagnostic score summarizes the checker’s rules, not the security of the entire website. For example, a restrictive CSP needs a resource inventory and testing, and HSTS settings require a working HTTPS deployment across the affected hosts.

The response lists present header values and missing-header descriptions. Review the headers API reference for optional redirect and error-page probes. The checker observes a server response and does not execute the page in a browser.

Test More Than the Homepage

A CDN, application server, and error handler can produce different headers. Check representative public paths and inspect redirects with the HTTP checker. Authenticated responses need separate testing in an authorized environment.

The checker cannot prove that a CSP is effective against every attack, inspect signed-in state, or establish compliance. Keep a record of the tested URL, final response, and intended policy when comparing deployments.

Frequently Asked Questions

No. It summarizes the headers observed by this check. Application vulnerabilities, authenticated behavior, and the effectiveness of policies need separate testing.

Need More Than a Free Check?

Get programmatic access to 100+ domain intelligence endpoints. Automate monitoring, integrate with CI/CD, and build custom workflows.

Free tier includes 200 requests/month

Free Security Headers Checker — Inspect HTTP Policies | EdgeDNS