Skip to content
search-engine-optimizedby Netsolution
  1. Home
  2. Technical and performance
  3. Security Headers Checker

Security Headers Checker

Check the protections your server sends — or fails to send — to every visitor.

Direct reading of the HTTP response headers returned by your server. Nothing is stored, and there is no usage limit.

What this tool is for

With every page served, your server sends headers the visitor never sees. Some give the browser security instructions: which script sources to accept, whether HTTPS is required, whether the page may be displayed in a frame on another site.

When those instructions are missing, the browser falls back on its defaults, which are deliberately permissive so as not to break the older web. Your site stays functional, but it is more exposed — to script injection, to clickjacking, to connection interception.

The link to search is indirect and brutal. A compromised site gets deindexed or flagged as dangerous in the results. Years of work disappear in a few days, and recovery takes weeks.

The first move: HSTS. One line in your configuration, no risk of breakage, and it removes the whole class of attacks that rely on an intercepted HTTP connection.

How to read the results

Strict-Transport-Security (HSTS) requires the browser to use only HTTPS for your domain, even if a link points at the old address. Its max-age value expresses how long that is remembered. Start short, lengthen later.

Content-Security-Policy (CSP) declares the authorised sources for scripts, styles and images. It is the most effective protection against code injection, and the most delicate to tune. Deploy it in report-only mode first.

X-Content-Type-Options has only one useful value: nosniff. It stops the browser guessing a file’s type and treating as a script something that is not one. No side effects.

Referrer-Policy controls what is passed to the site your visitor clicks through to. strict-origin-when-cross-origin is the right compromise: it preserves your partners’ statistics without disclosing your internal addresses.

X-Frame-Options prevents your pages being displayed in a frame on another site, a technique used to mislead users about what they are clicking.SAMEORIGIN suits most cases.

Common mistakes

Deploying a strict CSP straight away. It will block legitimate resources and break features, often with no visible error. Always go through report-only mode, which flags violations without blocking anything.

Setting a long HSTS without automated certificates. If the certificate expires, browsers will refuse the connection for the whole declared period, and the visitor can do nothing about it. Check automatic renewal with the SSL certificate checker before lengthening it.

Allowing unsafe-inline in the CSP. It is the easy way out when the policy breaks something, and it cancels most of the protection. Better to move inline scripts into files.

Configuring the headers and forgetting to check. A directive written in a configuration file is not a directive applied. Run the analysis again after deploying: that is the only way to know.

Checking only the home page. On a site with several server configurations or a separate subdomain, headers can differ from one section to the next. Check several pages.

Going further

Frequently asked questions

Do security headers affect search rankings?

Not directly, apart from moving to HTTPS, which has been a confirmed factor since 2014. Their effect is indirect but serious: a compromised site gets deindexed or flagged as dangerous in the results, which wipes out its traffic. These headers are insurance, not a ranking lever.

Where should I start if I have none?

In this order of return. HSTS first, which forces HTTPS and goes in as one line with no risk. Then X-Content-Type-Options, just as simple. Then Referrer-Policy. CSP comes last, because it is the only one that takes real tuning work.

Why is CSP so complicated?

Because it requires declaring every authorised source: scripts, styles, images, fonts, connections. On a site that has accumulated third-party tools over the years, that inventory is long. A badly tuned CSP breaks the page. The right method is to deploy it first in report-only mode, which flags without blocking.

Can HSTS make my site unreachable?

Yes, if your certificate expires during the declared period. Browsers that memorised the directive will refuse any connection over HTTP, with no way round it for the visitor. Start with a short duration, a few days, and lengthen it once automatic renewal is proven.

Is X-Frame-Options still needed?

It is officially superseded by the CSP frame-ancestors directive, but remains recognised everywhere. The best move is to declare both: the modern directive for recent browsers, the old header for everything else. The cost is nil.

Can I configure these on shared hosting?

Yes in almost every case, through an .htaccess file if the server runs Apache or LiteSpeed. A few lines cover the first three headers. On a WordPress site a security plugin can also handle it, at the price of a little less control.