Free tool

Check your website's security headers

Enter your domain: we read your homepage like a browser and check the HTTPS redirect, HSTS and the HTTP security headers that stop common attacks. For anything missing, the exact line to add.

No sign-up. Your domain is neither stored nor published.

What this security headers check looks at

HTTP security headers are instructions your server sends the browser with every page. The check first confirms that the unencrypted version of your site (http://) redirects to HTTPS. It then reads the Strict-Transport-Security (HSTS) header, which tells the browser never to come back unencrypted, and its duration. Finally, it checks the basic protections: X-Content-Type-Options, which stops the browser from guessing a file's type, protection against your site being shown inside a booby-trapped frame (X-Frame-Options or frame-ancestors), and the referrer policy. Only one page is read: your homepage, once.

How to read the result

"Broken now": your site isn't served over HTTPS, or doesn't send visitors to the encrypted version. A missing or very short HSTS header, or missing headers, are "To plan": they're extra protections, not a proven flaw. "Not applicable": your homepage is served by another domain (a website builder, for example), whose settings aren't up to you. "Could not be checked": the site didn't answer, or an anti-bot page blocked the check, so this HSTS test couldn't run.

The most common mistakes

  • A site available over HTTPS, but also over http:// with no redirect.
  • An HSTS header added with a duration of a few minutes, for testing, and never extended.
  • Headers added on a single page only, or lost when moving to a new host.
  • A content security policy (CSP) copied from an example, which breaks part of the site and ends up removed.

The fix, step by step

Headers are added in the server configuration (Apache, Nginx), in your hosting control panel, or with a plugin for your CMS. Turn on the HTTPS redirect first. Then add HSTS with a short duration, make sure everything works, and extend it to one year. Add X-Content-Type-Options: nosniff, frame protection and a referrer policy: these three lines rarely break anything. Leave the content security policy for last, starting in report-only mode.

Frequently asked questions

Do these headers make my site secure?

They close known doors, nothing more. They don't replace updates, strong passwords or backups.

Why do you only check the homepage?

To stay an ordinary visit: without authorization, our probe only reads the homepage. Headers are usually the same across the whole site.

Can HSTS make my site unreachable?

Only if HTTPS stops working: browsers will then refuse the unencrypted version. Start with a short duration, and keep certificate renewal automatic.