Skip to content
// free tool

Security headers checker

Security headers are short instructions your server sends with every page. They tell browsers how to protect your visitors: always use encryption, don't let other sites frame this page, don't run scripts from strangers. This tool fetches your home page once and tells you which headers are there, which are missing, and what each one means in plain English.
// sample result
odesstra ~ $ check yourbusiness.co.za
[http]:80 → :443 redirectpass
[headers]HSTS ok · CSP missing · X-Frame-Options missingwarn
[expose]X-Powered-By: PHP/8.1.2 · generator: WordPress 6.4warn
done in 6.2s · nothing attacked
// what it checks

The headers we look for

  • [HSTS](/glossary/hsts) (Strict-Transport-Security): tells browsers to only ever use HTTPS for your site. We check it's present and set for at least six months.
  • [Content Security Policy](/glossary/content-security-policy) (Content-Security-Policy): a list of where scripts, styles and images may come from. It limits the damage of cross-site scripting.
  • Clickjacking protection: either X-Frame-Options or the CSP frame-ancestors rule, so another site can't wrap yours in an invisible frame.
  • [X-Content-Type-Options](/glossary/x-content-type-options): set to nosniff, so browsers don't guess file types in risky ways.
  • [Referrer-Policy](/glossary/referrer-policy): how much of your page address is shared when visitors click away.
  • [Permissions-Policy](/glossary/permissions-policy): which browser features, like the camera or location, your site is allowed to use.

We also check the cookie flags (Secure, HttpOnly, SameSite) on any cookies your home page sets, whether http:// redirects to https://, and whether your headers reveal software versions.

// reading your results

What good looks like

A well-configured site sends something like this. The exact Content Security Policy depends on what your site loads, so treat it as an example, not something to copy blindly:

Example response headers
Strict-Transport-Security: max-age=31536000; includeSubDomains
Content-Security-Policy: default-src 'self'; frame-ancestors 'none'; object-src 'none'
X-Content-Type-Options: nosniff
Referrer-Policy: strict-origin-when-cross-origin
Permissions-Policy: camera=(), microphone=(), geolocation=()

A site that needs work typically shows only a server banner and nothing protective. Here's how one finding reads in each view:

// hacker view

[headers] HSTS ok · CSP missing · X-Frame-Options missing warn

// plain english

Another site could wrap yours inside a fake page. Two protective settings are missing. Adding them takes a developer about an hour.

// limits

What this check does not do

It makes one request for your home page (following up to five redirects) and one plain http:// request. It doesn't visit other pages, so headers that differ on your shop or login pages won't show here. It doesn't test whether your Content Security Policy actually blocks an attack, and it can't prove your site is free of problems. It is a quick, honest look at the front door.

// how to fix

Adding headers without breaking your site

  1. 01

    Start with the safe ones

    X-Content-Type-Options, Referrer-Policy, Permissions-Policy and clickjacking protection rarely break anything. Add them first, in your web server, hosting control panel, CDN or a security plugin.

  2. 02

    Add HSTS once HTTPS is solid

    Only turn on HSTS once every part of your site works over HTTPS. Start with a short max-age and increase it after a week or two.

  3. 03

    Roll out CSP in report-only mode

    Use Content-Security-Policy-Report-Only first, watch what it would block, adjust, then switch it on. This is the header most likely to need a developer.

Our guide to the six security headers every website should send explains each one in more detail.

// questions

Common questions

How do I check the security headers of a website?

Type the domain above. The checker makes one ordinary request to the home page and lists each security header it finds or misses, with what it means. Developers can also see headers in the browser's developer tools, under the Network tab.

Do security headers slow my site down?

No. They're a few hundred bytes of text sent with each page. Browsers read them instantly.

Can I add security headers on WordPress?

Yes. You can add them in your server configuration, your hosting panel, a CDN such as Cloudflare, or a reputable security plugin. Server or CDN level is usually the most reliable.

Why is my Content Security Policy marked as weak?

Usually because it allows 'unsafe-inline' scripts, which removes most of its protection against injected scripts. Moving inline scripts into files, or using nonces or hashes, fixes that.

Do I need both X-Frame-Options and frame-ancestors?

One is enough for modern browsers, and frame-ancestors in your CSP is the newer way. Sending both does no harm and covers older browsers.

Talk to a human