HTTP and security headers

Grade a website's HTTPS redirects, HSTS, Content-Security-Policy, cookies and other security headers.

A domain or URL; only the site (scheme and host) is used.

A few free checks a day without an account. Sign in to use your credits.

Check many at once

Bulk checks aren't unlocked yet

Bulk checks unlock after your first credit purchase or plan. Single checks work as usual.

Sign up free

What the check tells you

A website answers far more than its pages. Every response carries headers that tell browsers how careful to be: whether to insist on HTTPS, which scripts to trust, whether other sites may frame the page, what to send to the next site a visitor clicks to. Most of them are invisible when everything goes well, which is exactly why they're so often missing. This check reads them the way a browser would and grades the result.

What we check

Entry points. People reach a site four ways: http:// and https://, each with and without www. These are the site's entry points. We follow each one hop by hop and show every redirect on the way. We check that plain HTTP ends on HTTPS on your own site, that no chain loops or drops back from HTTPS to HTTP, that all four end on the same final address, and that the chains are short. A www name with no address is noted, not failed.

Security headers. On the page the chains end on we read:

  • HSTS, which makes browsers use HTTPS for your site for a set time. We check that it is present, valid, lasts at least a year and covers subdomains.
  • Content-Security-Policy, the strongest defence against injected scripts. We flag policies that still allow inline scripts, eval or scripts from anywhere, and policies that only report.
  • Framing protection, through frame-ancestors or X-Frame-Options, against clickjacking.
  • X-Content-Type-Options: nosniff, Referrer-Policy, Permissions-Policy and Cross-Origin-Opener-Policy.
  • Version numbers in Server and X-Powered-By, which tell scanners what to try.

Cookies. For every cookie the page and its redirects set, we check the cookie flags: Secure on HTTPS, HttpOnly on session cookies, a SameSite value, and the rules for __Host- and __Secure- names. We never keep cookie values.

Protocols. Whether the server offers HTTP/2, found with one TLS handshake, and whether it advertises HTTP/3. Both are information only.

Preload readiness. Whether the domain meets the published rules of the HSTS preload list, so browsers could use HTTPS even on a first visit.

How the grade works

The grade starts at 100 and loses points for each problem, weighted by how much it exposes visitors. No HTTPS at all costs the most. A missing redirect to HTTPS, a redirect loop, a downgrade or missing HSTS cost a lot. A missing CSP, a weak CSP, framing and insecure cookies cost a fair amount. Small things such as a missing nosniff or a long redirect chain cost a little. Information findings, such as a missing Permissions-Policy or no HTTP/2, cost nothing. A is 90 and up; below 50 is F.

Reading the result

The first block shows each entry point: where it started, every hop with its status code, and the page it ended on. A green tick means the chain ended on a working page; a cross means it failed, with the reason in words. Next comes the header table, one row per header with a plain verdict and the exact value we received, followed by preload readiness, the cookie table and the protocol line.

If none of the four entry points answers, the check returns an error and you aren't charged. When nothing listens on port 80 or 443 at all we say so plainly, and the domain report skips its website section rather than failing it.

How we fetch

We fetch as DNSSuperBot, from our own servers, and only the pages this check needs. Each hop is fetched once and checked against our safety rules again before we connect, so a redirect can't send us to a private address. We go easy on every site: at most a couple of dozen requests per check and a shared limit per host across all our users. If a site shows us a bot challenge, we report that entry point as not checked rather than trying to get around it.

What to do next

Each finding links to a fix guide with the exact header or setting for common servers and CDNs. Once you've made changes, run the check again with "fresh" ticked to skip the cache. The redirect tracer shows any single address hop by hop, and the domain report puts this grade next to your DNS, email and SSL results.

Questions

Which pages do you check?
The home page of the site you enter, reached four ways: http and https, each with and without www. We follow every redirect ourselves, one hop at a time, and read the headers of the page each chain ends on. A path in the address you type is ignored, because security headers are usually set for the whole site.
Why is my grade low when the site works fine?
Most security headers change nothing visible. They tell browsers to refuse attacks that haven't happened yet: plain HTTP downgrades, injected scripts, framing by other sites. A site can work perfectly and still leave those doors open. Each finding says what it protects against and the exact header to add.
Do you submit my site to the HSTS preload list?
No. We compare your headers and redirects with the list's published rules and tell you what's missing. We never contact the list or any other third party about the site you check. Adding a domain is something only its owner should do, at hstspreload.org.
Do you see or store my cookies?
We record only cookie names and their flags, such as Secure, HttpOnly and SameSite. The value of each cookie is dropped the moment we read the header, and we never send cookies from one hop to the next.
How much does a check cost?
In the browser you get a few free checks a day without an account. Through the API or MCP a check costs 2 credits, and a cached answer costs the same. Answers are cached for 15 minutes. Checks that fail on our side are free.