1. Home
  2. Developer
  3. Security Headers Checker

Security Headers Checker

Check the HTTP security headers of a website and see how to improve them.

For every format and option in one place, use Network Diagnostics →

Server lookup · only the address you type is sent, nothing is stored
The address you type is sent to a server for the lookup and is not stored. The server makes one request to it and returns only the response headers.
Without https:// we use https. Redirects are followed and the final response is checked.

This check only looks at whether response headers are present and at some common values, for reference. The score is a simple weighting defined by this site, not a security certification or a penetration test. A high score does not mean the site is safe, and a low one does not mean it is vulnerable. The home page, pages after login and APIs can send different headers.

How to use

  1. Enter the address to check. Without https:// the lookup uses https, and redirects are followed so the final response is the one checked.
  2. Press Check security headers. A server sends one request to the address and reads the response headers.
  3. Look at the score and band (Good, Fair, Poor) at the top.
  4. In the table, see whether each header is “Present (good)”, “Present (weak)”, “Missing” or “Not applicable”, with the current value and the reason.
  5. Under Suggested improvements, copy the example value for each missing header into your server configuration.

Headers checked and the rules

Header Weight Counts as good when
Strict-Transport-Security (HSTS) 20 On an https response, max-age is at least six months (15,552,000 s)
Content-Security-Policy (CSP) 25 Script sources are restricted, with no unsafe-inline, unsafe-eval or wildcard
X-Content-Type-Options 10 The value is nosniff
X-Frame-Options 10 DENY or SAMEORIGIN (CSP frame-ancestors is accepted instead)
Referrer-Policy 10 no-referrer, same-origin, strict-origin or strict-origin-when-cross-origin
Permissions-Policy 10 Set to a non-empty value
Cross-Origin-Opener-Policy 5 same-origin or same-origin-allow-popups
Cross-Origin-Resource-Policy 5 same-origin or same-site
Cross-Origin-Embedder-Policy 5 require-corp or credentialless

A “good” header earns its full weight, a “weak” one half and a missing one zero. An address that answered over http leaves HSTS out of the calculation because HSTS has no meaning there. With no headers at all the score is 0, with every item good it is 100, and a site that sets only HSTS and nosniff scores 30. A score of 80 or more is shown as Good, 50 or more as Fair, and anything lower as Poor.

Typical reasons for “weak”:

  • CSP script-src (or default-src when there is no script-src) contains 'unsafe-inline' without a nonce or hash, contains 'unsafe-eval', or allows almost everything with *, https: or data:
  • CSP is set only as Report-Only, so nothing is blocked
  • HSTS max-age is 0 or shorter than six months
  • Referrer-Policy is unsafe-url or no-referrer-when-downgrade
  • X-Frame-Options uses a value modern browsers do not support, such as ALLOW-FROM

COOP, CORP and COEP carry a lower weight because applying them can block external resources or popups. If you want other sites to use your public images or fonts, CORP cross-origin may be intended.

Other information shown

  • Information leaks: a server header with a version such as nginx/1.25.3, or an x-powered-by header, is reported. It does not affect the score.
  • Obsolete headers: X-XSS-Protection set to 1 is flagged as no longer used.
  • Cookie attributes: missing Secure, HttpOnly and SameSite flags on the cookies this response sets. Cookie values are never shown.

The result is for reference

This check only looks at whether response headers exist and at some common values. The score is a simple weighting defined by this site, not a security certification or a penetration test. A high score does not make a site safe, and a low one does not make it vulnerable. The home page, pages after login and APIs can send different headers, and many headers are added by a CDN or proxy. The example values are only a starting point. Test CSP and COEP in particular in a staging environment first, because pasting them as is can break pages.

What is sent to the server and the limits

  • Only the address you type is sent to the server for the lookup, and neither the address nor the result is stored.
  • A response must arrive within 8 seconds, up to 5 redirects are followed, and visiting the same host 3 times stops the lookup.
  • Private addresses, internal networks and bare IP addresses are not checked, and only default ports (80, 443) are allowed.
  • Rate limits apply: 6 requests per minute per IP and 30 per minute per target host.
  • This is not a port scanner or a way to load someone else’s site. It sends a single request per address.

FAQ

Will a site without security headers get hacked?

No. Security headers are an extra layer that limits the damage of attacks such as XSS, clickjacking and https downgrade. A missing header does not mean the site is wide open, but having them reduces harm when another weakness exists.

Which headers should I set first?

On an https site, HSTS, nosniff and Referrer-Policy have few side effects and are easy to start with. CSP has the biggest effect but requires knowing every script and third-party service you use, so the usual approach is to start with Report-Only, review the violation reports, then switch to enforcing mode.

My hosting or CDN does not let me set them.

CDNs such as Cloudflare can add response headers through rules, and most web servers and hosts let you set headers in a config file or dashboard. On hosted store or blog platforms where headers cannot be changed, just use the result to see the provider defaults.

Can I relax at 100 points?

No. This check looks at a handful of headers. Real weaknesses such as input validation, authentication and outdated dependencies cannot be seen in headers. To see raw header values use the HTTP header viewer, for certificate details the SSL certificate viewer, and for a file that tells researchers where to report vulnerabilities the security.txt generator.

Why is HSTS “Not applicable” for my http address?

Browsers ignore an HSTS header sent over http, so it only matters on https responses. For an address that answered over http, it is left out of the score. First use the redirect checker to see whether http moves to https.

The address you type is sent to a server for the lookup and is never stored.

Can't find the tool you need?

Tell us what you want to do. We build the most requested tools first.