Free tool / No sign-up
Security headers checker: test HSTS, CSP and more.
Paste any website address. Each header graded, with the fix.
We request the page once, follow up to five redirects and read one of its own files. Only security headers come back. Nothing is stored. Up to 20 checks per 10 minutes.
Security headers added at server level and tested against your editor, forms and checkout, on a site I build or look after. Free review and a fixed quote.
See the serviceAbout this tool
Security headers checker: what it does.
Enter any website and this free security headers checker reads the HTTP security headers its home page sends. It follows redirects to the final address, then checks Strict-Transport-Security (HSTS), Content-Security-Policy, X-Content-Type-Options, X-Frame-Options and frame-ancestors, Referrer-Policy and Permissions-Policy. It also shows the cross-origin headers and any old headers you can remove. Each result says what the header does, what the site sends, and how to fix it on Apache, Nginx, Cloudflare or WordPress. It's free and needs no sign-up.
How it works
How to check security headers with this tool.
Security headers are lines the server sends with a page, before the page itself. They tell the browser which protections to switch on: always use HTTPS, only run scripts from trusted places, don't let other sites put the page in a frame. Visitors never see them, so a site can look fine and still send none.
The checker asks for the address you enter once, the way a browser would. If the site redirects, for example from http to https or from example.com to www.example.com, it follows each step and reports the final address. The headers shown are the ones on that final page, because that's the page your visitors get. It also reads one of the site's own scripts or stylesheets, to see if the headers reach files as well as pages.
Each header gets a plain result: pass, warning or fail. You see the exact value the site sent, so you can check the result yourself. The score adds up the points next to each result. Nothing is hidden behind a letter grade.
What it checks
The HTTP security headers it tests, and what each one does.
Six headers are scored. The rest are shown with a short note, because they suit some sites and break others:
| Header | What it does |
|---|---|
| Strict-Transport-Security (HSTS) | Tells the browser to use only HTTPS for the site, for a set time. Stops someone on the same network from forcing a visitor onto plain http. |
| Content-Security-Policy (CSP) | Lists where scripts, styles, images and frames may load from. A good policy stops injected scripts from running, which is the main defence against cross-site scripting. |
| X-Frame-Options or CSP frame-ancestors | Says whether other sites may show the page inside a frame. Blocking that stops clickjacking, where a hidden frame tricks a visitor into clicking. |
| X-Content-Type-Options | The only value is nosniff. The browser then trusts the declared file type, and won't run a file as a script or stylesheet unless it really is one. |
| Referrer-Policy | Controls how much of the page address is passed on when a visitor clicks a link to another site. It keeps private paths and search terms out of other sites' logs. |
| Permissions-Policy | Switches off browser features the site doesn't use, such as the camera, microphone and location, for the page and anything framed in it. |
| Cross-Origin-Opener-Policy, -Embedder-Policy and -Resource-Policy | Shown, not scored. They isolate the page from other sites' windows and files. Strict values can break payment, login and video embeds, so they need testing first. |
HSTS checker
HSTS checker: is the site forcing HTTPS?
An HTTPS certificate isn't enough on its own. A visitor who types the address without https, or follows an old link, still makes one plain http request first. HSTS closes that gap. After a browser sees the header once over HTTPS, it uses HTTPS for that site until max-age runs out. Browsers ignore the header on plain http, as the HSTS standard (RFC 6797) requires, so the checker reads it from the HTTPS response.
The checker passes HSTS when max-age is at least 15,552,000 seconds, which is six months. That's the same line Mozilla's HTTP Observatory uses. A shorter max-age gets a warning: it works, but each visitor is unprotected again sooner. A max-age of 0 switches HSTS off. If a site sends the header twice, browsers use only the first, so the checker grades the first and tells you about the second.
It also tells you if the site is ready for the HSTS preload list, which browsers ship built in. hstspreload.org asks for a max-age of at least 31,536,000 seconds (one year), includeSubDomains and preload, sent on the base domain, with plain http redirected to https. Add includeSubDomains only when every subdomain works on HTTPS, including ones only staff use. Leaving the list can take months, so preload is a long-term commitment.
Content Security Policy
Content security policy checker: what makes a CSP strong.
A CSP only protects against injected scripts if it controls scripts. The checker looks for script-src, or default-src when script-src is missing. It passes the policy when scripts are limited to named sources, nonces or hashes. It warns when the policy allows 'unsafe-inline' without a nonce or hash, allows 'unsafe-eval', or allows any host with * or https:. MDN says 'unsafe-inline' "defeats much of the purpose of having a CSP".
Many sites send a CSP that does something else. Shopify stores, for example, send a policy with upgrade-insecure-requests and frame-ancestors but no script rules. That still helps, so it gets a warning rather than a fail. A Content-Security-Policy-Report-Only header doesn't enforce anything; it only reports. The checker shows it, but it can't pass the CSP check on its own. It's the right way to test a new policy for a week before you enforce it.
Scoring
How the score works.
The score is out of 100. A pass earns the full points, a warning earns half, a fail earns none. Headers that aren't scored never change it.
| Check | Points, and what it takes to pass |
|---|---|
| HSTS | 25. Served over HTTPS with max-age of six months or more. Under six months is a warning. |
| Content-Security-Policy | 25. An enforced policy that controls scripts without 'unsafe-inline', 'unsafe-eval' or a wildcard. A policy without script rules is a warning. |
| Framing (frame-ancestors or X-Frame-Options) | 20. frame-ancestors with 'none', 'self' or named sites, or X-Frame-Options DENY or SAMEORIGIN. frame-ancestors * is a warning. |
| X-Content-Type-Options | 10. The value nosniff. |
| Referrer-Policy | 10. no-referrer, same-origin, strict-origin or strict-origin-when-cross-origin. Missing is a warning, because browsers already default to strict-origin-when-cross-origin. |
| Permissions-Policy | 10. At least one feature listed. A policy that lists only interest-cohort, from Google's retired FLoC test, is a warning. |
WordPress and Shopify
Which headers matter most for a WordPress or Shopify site.
For a typical WordPress business site, start with the three that rarely break anything: HSTS, X-Content-Type-Options nosniff, and X-Frame-Options SAMEORIGIN. Use SAMEORIGIN rather than DENY. The Elementor editor and the Customizer show your own site inside a frame, and DENY blocks that. WordPress core only sends X-Frame-Options on the login and admin screens, through its send_frame_options_header function, so the front end needs it added. Then add Referrer-Policy strict-origin-when-cross-origin and a Permissions-Policy that turns off the camera, microphone and location.
Leave Content-Security-Policy until last on WordPress. Themes, page builders, analytics and chat tools all add inline scripts and outside sources, so a strict policy breaks pages if you guess. Start with Content-Security-Policy-Report-Only, watch what it reports, then enforce it.
On Shopify, Shopify sets the headers for hosted stores, and Liquid themes can't send HTTP headers. Three stores checked on 15 November 2026 all sent HSTS with max-age=7889238 (about 91 days), X-Content-Type-Options nosniff and a CSP without script rules. Two blocked framing; one allowed it from any site. A Shopify score mostly reflects Shopify's defaults. Headless Hydrogen stores can set their own CSP in server code, as Shopify's Hydrogen documentation shows.
How to add them
How to add security headers on Apache, Nginx, Cloudflare and WordPress.
Each result in the checker gives a ready snippet for the header it found missing. This is where each one goes:
| Where your site runs | How to add the headers |
|---|---|
| Apache or LiteSpeed (most cPanel hosts) | Add Header always set lines to the .htaccess file in the site's root folder, inside <IfModule mod_headers.c>. Apache's documentation says always also covers redirects and error pages; without it, some responses go out without the header. |
| Nginx | Add add_header lines with the always flag in the server block. Nginx only adds headers to 200, 3xx and a few other codes without always. A location block that has its own add_header loses every header set above it, unless you use add_header_inherit merge (Nginx 1.29.3 and later). |
| Cloudflare | Turn on HSTS under SSL/TLS, Edge Certificates; the same panel has a No-Sniff switch for nosniff. Add the others with Rules, Create rule, Response Header Transform Rule, using Set static. Skip the Add security headers managed transform: it still adds X-XSS-Protection 1; mode=block and Expect-CT, which are both deprecated. |
| WordPress, without server access | Add the headers in PHP on the send_headers hook, in a small plugin or a child theme. Full-page caches that serve saved HTML without starting WordPress skip that hook, so check the result here after clearing the cache. Server or Cloudflare rules are more reliable. |
Old headers
Deprecated headers you can remove.
The checker lists these when it finds them. They don't change the score, but some can do harm:
| Header | Status and advice |
|---|---|
| X-XSS-Protection | Deprecated. MDN warns it "can create XSS vulnerabilities" in otherwise safe sites. Remove it, or set it to 0 as OWASP advises. Use a Content-Security-Policy instead. |
| Expect-CT | Deprecated. Chromium dropped it from version 107, because it now checks Certificate Transparency by default. Safe to remove. |
| Public-Key-Pins (HPKP) | Deprecated by all major browsers. A wrong pin can lock visitors out, so remove it. |
| Feature-Policy | Replaced by Permissions-Policy, which uses a different syntax. Move the rules across. |
| X-Frame-Options ALLOW-FROM | Obsolete. Browsers ignore the whole header, so framing is allowed. Use CSP frame-ancestors with the sites you trust. |
Limits
What a security headers test can't tell you.
Headers are one layer. A perfect score doesn't mean a site is secure: it says nothing about outdated plugins, weak passwords or server bugs. The checker reads the home page, or the exact address you enter, so a header added only on some pages won't show for others. It doesn't check the HSTS preload list itself, cookies or CORS.
Some sites show a bot check to automated visits. The headers then belong to the check page, not the site, and the result says so. Each check makes a few requests to the site you enter and returns only the security headers. Nothing is stored, and each visitor can run 20 checks every 10 minutes.
What's new
Changes to the checker.
November 2026: first version, grading six security headers with fixes for Apache, Nginx, Cloudflare and WordPress, and listing cross-origin and deprecated headers.
Next step
Want the headers set up for you?
Adding headers is a few lines, but a wrong CSP or an early HSTS preload can take a site down. I build and look after WordPress, WooCommerce and Shopify sites, and setting up and testing security headers is part of the work. If your site is on WordPress, I'll add them at server level, test the editor, checkout and forms, and send you the before and after results from this checker.
Questions
Security Headers Checker FAQs
How do I check a website's security headers?+
Enter the address above. The security headers checker follows any redirects, reads the headers on the final page and grades each one. To check security headers by hand, open your browser's developer tools, reload the page, select the first request on the Network tab and read the response headers, or run curl -I followed by the address.
What is an HSTS checker?+
An HSTS checker reads a site's Strict-Transport-Security header and says whether browsers will be told to use HTTPS only, and for how long. This checker passes a max-age of six months or more, warns below that, and tells you if the header meets the preload list rules: one year, includeSubDomains and preload.
Which security headers should every website have?+
Start with Strict-Transport-Security, X-Content-Type-Options nosniff, X-Frame-Options SAMEORIGIN (or CSP frame-ancestors), and Referrer-Policy strict-origin-when-cross-origin. Add Permissions-Policy for features you don't use. Content-Security-Policy gives the most protection but needs testing in report-only mode first.
Is X-Frame-Options still needed if I have a CSP?+
Not if your CSP has a frame-ancestors directive and is sent as a header. Browsers follow frame-ancestors and ignore X-Frame-Options when both are present. Keeping X-Frame-Options does no harm, and it covers very old browsers. frame-ancestors doesn't work in a CSP meta tag.
Should I still use X-XSS-Protection?+
No. Browsers removed the filter it controlled, and MDN warns the header can create XSS vulnerabilities. Remove it or set it to 0, and use Content-Security-Policy instead. The checker lists it under old headers.
Is the security headers checker free?+
Yes. It's free with no sign-up. Each visitor can run 20 checks every 10 minutes. Each check reads the page once, follows up to five redirects and reads one of the site's own files, and nothing is stored.
Done-for-you website work
Want your headers set up and tested?
Send me the site address and what you need. I’ll reply with a clear next step within 24 hours.
Free review and a fixed quote.
bealinawaz@gmail.com