Security headers checker

Check the headers that tell browsers how to protect your visitors, and whether files like .env or .git answer to anyone who asks.

Free, no account. Up to 25 checks a day per visitor.

What it checks

  • HTTP Strict Transport SecurityTells returning browsers to never try http first, closing the window where a connection can be hijacked.
  • Content Security PolicyA policy stops an injected script from running even if an attacker gets one onto the page.
  • Clickjacking protectionWithout it another site can load yours invisibly in a frame and trick visitors into clicking.
  • MIME sniffing disabledStops browsers guessing a file's type, which turns an uploaded "image" into an executable script.
  • Referrer policyDecides how much of the current URL is sent to sites you link to. Tokens and IDs in URLs leak without one.
  • Cookie flagsA session cookie without Secure and HttpOnly can be stolen by a script or over an open network.
  • Server version disclosureA version number in a header tells an attacker exactly which published exploits to try.
  • Exposed sensitive filesA readable `.env`, `.git` folder or database dump is the whole site's secrets in one request.
  • Directory listingA folder that lists its files shows every upload and backup to anybody who looks.

Questions

Is this a hacking tool?

No. We only read what the site shows every visitor. Nothing is submitted and no weakness is exploited.

Which header matters most?

An exposed .env or database backup is the most urgent — it is the site's passwords in one file. After that, a Content-Security-Policy.

Will adding headers break my site?

A strict Content-Security-Policy can, so start it in report-only mode. The others are safe to add as the report suggests.

We only read what a public visitor could. Nothing is submitted to your site and no vulnerability is exploited — findings are what your site shows, not what we tried.

More free tools

Or run all fifty checks at once