Guides · Security
How to check website security headers
Published 18 November 2026 · Updated 18 November 2026
To check website security headers, enter your home page in a headers checker, or paste the output of curl -sI into a paste analyzer. You should see HTTPS, HSTS, Content-Security-Policy, clickjacking protection, X-Content-Type-Options and cookie flags, graded from A to F. Fix the failures first, then re-run the check. A passive audit, from $15, reviews the rest of the site.
How do I check website security headers?
Open the free security headers check, enter a public page, usually your home page, and press Check my headers. The checker loads that page once, reads the headers and cookies, looks up public SPF and DMARC, and returns an A to F grade. Start with the failures: each row says what was found and how to fix it.
- Run the live check on your home page, then on the login or checkout page if you have one, because those pages should never be weaker than the home page.
- If the site is on staging or not public, copy the response headers from
curl -sIor your browser's developer tools and paste them into the paste headers analyzer. Nothing you paste leaves your browser. - Copy the suggested header for your server, deploy it, and run the check again. For Content-Security-Policy, start in Report-Only mode so you do not break the site; the CSP guide explains that rollout.
Which security headers should I look for?
Check for HTTPS and HSTS, a Content-Security-Policy, clickjacking protection with frame-ancestors or X-Frame-Options, X-Content-Type-Options set to nosniff, a clear Referrer-Policy, and secure cookie flags. These are the headers that stop common browser attacks such as clickjacking, MIME sniffing and some forms of script injection. A missing header is a failure; a weak value is usually a warning.
Plain-English notes for each header are in security headers explained. To confirm HSTS on its own, including preload and the HTTP to HTTPS redirect, use the HSTS checker. To stop other sites framing your pages, see What is X-Frame-Options?.
What should I do after I get a grade?
Fix failing headers first, deploy, and run the free check again until the failures are gone. Warnings can wait if a change might break a payment page; test those on staging, and use Report-Only for CSP. If you need the rest of the site reviewed, a passive audit starts at $15 and arrives as a PDF within 48 hours.
See security audit pricing, or read what a passive audit checks. The audit only runs after you prove you control the domain, and it never asks for a main password.
Frequently asked questions
How do I check website security headers?
Enter your home page in the free security headers check, or paste curl -sI output into the paste analyzer. You get an A to F grade for HTTPS, HSTS, CSP, clickjacking protection, cookie flags and related headers, with a fix for each failure.
Which tool should I use if my site is not public yet?
Use the paste headers analyzer. It grades the same headers in your browser and does not upload what you paste, so it works for staging and pre-launch sites.
What does a website security audit cost?
A passive security audit of a site you own starts at $15, with a PDF in 48 hours of payment and ownership verification, or a full refund. It covers more than headers: TLS, up to 20 pages, exposed files, software versions and email authentication.