Free HTTP security headers checker
See which browser protections your website sends and what you can improve.
Example report
example.com- 1 Medium
- 2 Low
- 11 passed
HSTS is not enabledexample.comMedium
https://example.com/ answered without a Strict-Transport-Security header.
Next step
Add
Strict-Transport-Security: max-age=31536000; includeSubDomainsto HTTPS responses once every subdomain serves HTTPS.No Content Security Policyexample.comLow
https://example.com/ answered without a Content-Security-Policy header.
Next step
Start with a report-only policy (
Content-Security-Policy-Report-Only) to see what your pages load, then enforce a policy such asdefault-src 'self'plus the sources you need.Software version disclosed in headersexample.comLow
The Server header names nginx 1.18.0.
Next step
Turn off version banners:
server_tokens off;in nginx,ServerTokens ProdandServerSignature Offin Apache,expose_php = Offin php.ini, and remove X-Powered-By where your framework adds it.
example.com
- X-Content-Type-Options
- Clickjacking protection
- Referrer-Policy
- Permissions-Policy
www.example.com
- HTTP Strict Transport Security
- Content Security Policy
- X-Content-Type-Options
- Clickjacking protection
- Referrer-Policy
- Permissions-Policy
- Server information disclosure
Response headers
example.com
strict-transport-securityKeeps browsers on HTTPS- Not set
content-security-policyLimits where scripts and other content may load from- Not set
x-content-type-optionsStops content-type guessingnosniffx-frame-optionsOlder control over framingSAMEORIGINreferrer-policyHow much of the address is sent onstrict-origin-when-cross-originpermissions-policyWhich browser features the page may usecamera=(), microphone=(), geolocation=()serverNames the server softwarenginx/1.18.0x-powered-byNames the framework- Not set
All response headers (200 from https://example.com/)
server: nginx/1.18.0
content-type: text/html; charset=utf-8
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
referrer-policy: strict-origin-when-cross-origin
permissions-policy: camera=(), microphone=(), geolocation=()
cache-control: max-age=600www.example.com
strict-transport-securityKeeps browsers on HTTPSmax-age=31536000; includeSubDomainscontent-security-policyLimits where scripts and other content may load fromdefault-src 'self'; frame-ancestors 'none'x-content-type-optionsStops content-type guessingnosniffx-frame-optionsOlder control over framing- Not set
referrer-policyHow much of the address is sent onstrict-origin-when-cross-originpermissions-policyWhich browser features the page may usecamera=(), microphone=(), geolocation=()serverNames the server softwarecdnx-powered-byNames the framework- Not set
All response headers (200 from https://www.example.com/)
server: cdn
content-type: text/html; charset=utf-8
strict-transport-security: max-age=31536000; includeSubDomains
content-security-policy: default-src 'self'; frame-ancestors 'none'
x-content-type-options: nosniff
referrer-policy: strict-origin-when-cross-origin
permissions-policy: camera=(), microphone=(), geolocation=()What the headers check looks at
Transport
Strict-Transport-Security, so browsers keep to HTTPS.
Scripts and content
An enforced Content-Security-Policy that blocks inline scripts.
Framing
frame-ancestors or X-Frame-Options, so other sites cannot frame your pages.
Browser behaviour
nosniff, Referrer-Policy, Permissions-Policy and version disclosure.
Headers are judged on the final response after redirects, for the domain and its www name separately.
Understand the issue and your next step
Each finding explains what we found, why it matters and what you can change. Start with the issues that need attention, then open the evidence when you want the detail.
- Enter your domain
- Review the findings
- Follow the fix guides
No Content Security PolicyLow
The page does not set a Content-Security-Policy header.
Content-Security-Policy: not presentA Content Security Policy limits where scripts and other content may load from. It greatly reduces the damage if a cross-site scripting bug is ever introduced.
Start with a report-only policy (Content-Security-Policy-Report-Only) to see what your pages load, then enforce a policy such as default-src 'self' plus the sources you need.
Common header issues you can put right
HSTS is not enabledMedium
Your site may use HTTPS without telling browsers to keep using it on future visits. Check your HTTPS setup before enabling HSTS.
No Content Security PolicyLow
A CSP tells browsers which sources your pages can load. Start by understanding what your site needs, then test a policy before enforcing it.
Software version disclosed in headersLow
A version number in Server or X-Powered-By tells anyone which release to look up weaknesses for. Remove it at the web server or framework.
HSTS max-age is shortLow
The Strict-Transport-Security max-age is under six months.
Content Security Policy allows inline scriptsLow
The Content Security Policy permits 'unsafe-inline' scripts without a nonce or hash.
X-Content-Type-Options is not setLow
Responses do not include
X-Content-Type-Options: nosniff.Pages can be framed by other sitesLow
Neither X-Frame-Options nor a CSP frame-ancestors directive is set.
No Referrer-PolicyInformation
Responses do not set a Referrer-Policy header.
No Permissions-PolicyInformation
Responses do not set a Permissions-Policy header.
Keep watch after you've fixed it
Ironfang Security rechecks a verified domain every week or every day and tells you what changed: new findings, fixes and certificates nearing expiry.
Free during the preview. Domain verification required.
- NewIssue detected
- FixedConfirmed by recheck
- ReopenedDetected again
How the check works
- The home page over HTTPS for the domain and its
www.name, or only the name entered if it is a subdomain, following up to three redirects that stay on those names. Headers are judged on the final response. - Transport and scripts:
Strict-Transport-Securitywith amax-ageof at least 180 days, and an enforcedContent-Security-Policythat does not let inline scripts run. - Framing: a CSP
frame-ancestorsdirective, orX-Frame-Optionsset toDENYorSAMEORIGIN. - Browser behaviour:
X-Content-Type-Options: nosniff, aReferrer-Policy, and aPermissions-Policy(the olderFeature-Policyalso counts). - Disclosure: a version number in
Server,X-Powered-By,X-AspNet-Version,X-AspNetMvc-VersionorX-Generatoron any response the check received.
Reading a result
Security headers are instructions a server attaches to its responses, and browsers act on them: they switch to HTTPS before connecting, refuse scripts from sources a policy does not allow, and decline to show a page inside another site. A missing header is not a vulnerability in itself. It is a defence the browser would apply and currently does not.
The result counts each check on each host as passed or needing attention. There is no grade or score: the seven checks do not carry equal weight, and a letter for headers says nothing about the rest of the site. Every finding this page can raise is hardening, each with the severity shown beside it.
Where the domain and its www. name are served by different systems, their headers often differ, so each host is listed on its own with the full set of headers it returned.
What it does not do
- It reads the home page only. Other paths, an application behind a login and API responses can send different headers, and often do.
- Headers are checked for presence and a few key values, not audited in depth. A
Content-Security-Policypasses here as long as it is enforced and blocks inline scripts, however many sources it allows. - Cookies, the HTTP to HTTPS redirect and security.txt are not part of this result. The cookie security, HSTS and security.txt checkers show them.
- It is an automated, low-impact external check: a few ordinary requests from one address, no login and no attack traffic. It is not a penetration test, and a clean result does not mean the site is secure.
What happens to the domain you enter
The check runs from Ironfang Security's published scanner address with the same low-impact limits as a scan. Nothing you enter is stored or logged. A result is reused for five minutes, and a certificate log search for an hour, so a repeat check is quick and the domain is not checked again.
Guides
A few things worth knowing
- Which security headers should a website send?
- Most sites should send Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options: nosniff, a framing control (CSP frame-ancestors or X-Frame-Options), Referrer-Policy and Permissions-Policy. The right values depend on what the site loads and who embeds it.
- Do security headers need to be on every page?
- Mostly, yes. A browser applies HSTS to the whole host once it has seen it, but a Content Security Policy, a framing control and nosniff apply only to the response they arrive on. Set them once at the web server, CDN or framework rather than page by page.
- Why does this checker not give a grade?
- Ironfang's scanner has no score to give. Each check passes or raises a finding with its own severity, and the page shows those counts. A letter grade would add the headers up as if they weighed the same, and they do not.

