Free tool·Headers & SSL

Is your site sending the right security headers?

HSTS, CSP, anti-clickjacking, SSL/TLS certificate: a grade from A+ to F and what to fix, in seconds.

A single visit to the homepage, just like a browser. Nothing is attacked.

What the test checks

Six configuration checks

  • HTTPS and TLS certificate

    Automatic redirect to https://, certificate validity and expiration date, protocol version (TLS 1.2 or 1.3).

    Learn more →
  • HSTS

    Forces the browser to always use HTTPS, even if the user types http://.

    Learn more →
  • Content-Security-Policy

    Lists the allowed script sources: the browser's best defense against XSS.

    Learn more →
  • Anti-clickjacking

    X-Frame-Options or frame-ancestors prevent your site from being displayed inside a booby-trapped page.

    Learn more →
  • X-Content-Type-Options, Referrer-Policy, Permissions-Policy

    Prevent disguised content from running, page URLs from leaking, and abusive access to the camera or microphone.

    Learn more →
  • Disclosure and cookies

    Server version publicly advertised, cookies missing the Secure, HttpOnly and SameSite attributes.

    Learn more →

FAQ

Everything about security headers

What is an HTTP security header?

An instruction the server sends to the browser with every page to turn on protections: force HTTPS (HSTS), restrict scripts (CSP), forbid embedding in another page (X-Frame-Options), and so on. They're configured on the web server, the hosting provider or the CDN.

Is the test safe for my site?

Yes. The tool visits the homepage once, just like a browser, and reads the response headers and the certificate. It sends no attack and doesn't read the page content.

How is the grade calculated?

Each check deducts points based on severity: something to fix (missing HSTS or CSP, invalid certificate) weighs more than something to improve. A+ means a complete configuration.

Does a good grade mean my site is secure?

No. Headers are a baseline, browser-side protection. Vulnerabilities in the application itself (access control, injection, business logic) only show up when you test it, with a pentest.

My site is behind Cloudflare or a CDN. Is that a problem?

No: the tool reads the headers as they reach the visitor. If the CDN adds any, they're taken into account.