Free tool·Headers & SSL
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
Automatic redirect to https://, certificate validity and expiration date, protocol version (TLS 1.2 or 1.3).
Learn more →Forces the browser to always use HTTPS, even if the user types http://.
Learn more →Lists the allowed script sources: the browser's best defense against XSS.
Learn more →X-Frame-Options or frame-ancestors prevent your site from being displayed inside a booby-trapped page.
Learn more →Prevent disguised content from running, page URLs from leaking, and abusive access to the camera or microphone.
Learn more →Server version publicly advertised, cookies missing the Secure, HttpOnly and SameSite attributes.
Learn more →FAQ
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.
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.
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.
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.
No: the tool reads the headers as they reach the visitor. If the CDN adds any, they're taken into account.