CrawlCheck

Guides · 2026-09-30 · By

HSTS check: missing header, bad preload, removed entries

Three HSTS problems you can read from one homepage response, how common each is across scanned sites, and why preloading is a separate decision from sending the header.

Fetch your homepage over HTTPS and read the Strict-Transport-Security header. Three problems matter: no header at all; a preload token without a max-age of at least one year and includeSubDomains, which the preload list will reject or drop; and a domain that hstspreload.org lists as removed while the header still asks to be preloaded. Send the header on every HTTPS site. Treat preloading as a separate choice that takes months to undo, and only send the preload token if every subdomain will serve HTTPS for good.

Check your own site free

About a minute. First scan free with your email, nothing installed.

Three HSTS problems can be read from a single homepage response, and across the sites CrawlCheck has scanned they turn up at very different rates. No Strict-Transport-Security header at all: 15.9% of scanned sites. A header that sends the preload token without meeting the preload list’s requirements: 5%. And the quietest case, a domain the public preload list records as removed that still sends the token, asking for something the list has already taken back: 0.8%. This guide is how to check each one yourself and what to change.

What you seeShare of scanned sitesWhat it meansWhat to do
No header over HTTPS15.9%Browsers can be talked down to plain HTTP on every visitAdd the header to HTTPS responses
Preload token, header does not qualify5%A request the list will reject, or an existing entry it will dropMeet the requirements, or remove the token
Preload token, list says removed0.8%A promise the list no longer holdsRemove the token, or resubmit with a qualifying header

What does the header do? #

A browser that receives Strict-Transport-Security: max-age=31536000 over HTTPS remembers the host for a year and rewrites every later http:// request to https:// before it leaves the machine. The first visit is still unprotected; the browser preload list closes that gap by shipping the host inside the browser as already remembered. includeSubDomains extends the rule to every subdomain. preload is not an instruction to the browser at all: it is consent that a separate submission to the list reads.

How do you check your header? #

Fetch the homepage over HTTPS with curl -sI https://example.com/ and read the strict-transport-security line. Read the homepage, because the first request is the one that counts. Then answer three questions: what max-age is in seconds, whether includeSubDomains is present, and whether preload is present. The preload list’s requirements are fixed: max-age of at least 31,536,000 seconds, includeSubDomains, and the preload token.

Convert max-age to days to see a shortfall plainly: 15,768,000 seconds is 182 days against a required 365. A header with the token and that value is asking to be preloaded while not qualifying. CrawlCheck’s free HSTS header generator builds the header from your answers to the three questions and will not add the preload token unless the other two requirements are met.

Header on homepage?noMissing: add ityesPreload token sent?noFine: preload is optionalyesOne-year max-age andincludeSubDomains?noIneligible: fix or drop tokenyes: look the domain up on hstspreload.orgList statusremoved: drop the tokenpreloaded: keep qualifyingpending: wait, or withdrawunknown: submit if you mean it
Three questions about the header, then one lookup. Only a preload token the header cannot support, or a list entry the header no longer backs, needs action.

What does the preload list status tell you? #

The header cannot say whether the domain is on the list, so look it up at hstspreload.org, which keeps a public status for every domain: unknown, pending, preloaded or removed. Read it beside the header you just fetched.

Header sentList statusWhat happens
none, over HTTPSanyno protection after the first visit either
max-age under a year, no preload tokenunknownvalid HSTS; nothing to fix
preload token, max-age under a yearunknowna submission would be rejected
preload token, no includeSubDomainspendingthe pending submission will be rejected
header no longer qualifiespreloadedthe entry will be dropped at a later list build, silently
preload token presentremovedthe token promises an entry that no longer exists

The serious row is a preloaded domain whose header has weakened: nothing breaks today, and the drop arrives without notice. A pending entry you did not submit needs nothing from you.

Should you preload at all? #

Sending the header is worth doing on any site that serves HTTPS. Preloading is a separate decision, because it takes months to undo. Once listed, every subdomain must serve HTTPS for as long as the entry lives, and the entry lives in shipped browser builds; a subdomain that later needs plain HTTP for a device, a legacy vendor or an internal tool cannot have it. Removal propagates only as browsers update, which takes the better part of a year for the long tail. Not preloading is not a defect. Sending a preload token the header cannot back is.

How do you fix each case? #

No header. Add it to HTTPS responses only; browsers ignore it over plain HTTP. Start with a short max-age such as 300 seconds while you confirm every subdomain and redirect chain works over HTTPS, then raise it.

Preload token that does not qualify. Decide on intent. If you want preload, raise max-age to 31536000 and add includeSubDomains. If you do not, remove preload; sending it without qualifying is the worst of both.

Token sent, list says removed. Remove the token. Continuing to send it does not restore the entry; only a fresh submission with a qualifying header does.

What does a homepage check miss? #

A subdomain that serves a different header, an http:// redirect that lands somewhere other than the HTTPS homepage, and the list contents inside a particular browser build are all outside a homepage reading. The status-code guide covers the redirect side, and the CSP rollout guide covers the security header that is harder to get right. The rates above are live; the dataset page has the rest.

What to check next to HSTS: cookies and certificates #

HSTS makes the browser use HTTPS. Whether a session stays private also depends on how cookies are scoped and on which certificates exist for the domain.

CheckWhy it mattersHow to check itReference
Cookie prefixes (__Host-, __Secure-)The browser enforces extra rules: __Host- cookies must be Secure, set for the exact host, with Path=/Read the Set-Cookie headers on sign-in and check the attributes match the prefixMDN
Partitioned cookiesA cookie stored per top-level site, for embedded services that need stateCheck the Partitioned attribute and test the embedded flow; it also requires SecureMDN
Public suffixDefines where one site ends and another begins (co.uk, many hosting domains)Compare the host with the Public Suffix List rather than assuming the last two labels are the siteMDN
Schemeful same-siteHTTP and HTTPS versions of a domain count as different sites for cookiesWhen a cookie goes missing between pages, compare both scheme and domainMDN
TLS version and downgradeOld protocol versions weaken the connection HSTS insists onTest which TLS versions the server accepts; an HTTP-to-HTTPS redirect is a separate checkRFC 9846 (TLS 1.3, replaced RFC 8446 in 2026); RFC 9851 (TLS 1.2 gets no new features); RFC 10015 (obsolete TLS 1.2 key exchange deprecated)
Encrypted Client HelloHides which site a visitor is connecting to from anyone watching the networkLook for an ech= key in the domain's DNS HTTPS record; the CDN usually publishes itRFC 9849 (ECH); RFC 9848 (publishing it in DNS)
Certificate TransparencyEvery public certificate for the domain is logged, so an unexpected one can be spottedSearch the logs for the domain (for example crt.sh) and investigate any issuer you do not use; a log entry alone is not a compromiseMDN
Share of scanned sites with each finding in this articleNo HSTS header15.9%HSTS preload requested but not eligible5%Removed from the HSTS preload list0.8%Share of scanned sites with eachfinding in this articleNo HSTS header15.9%HSTS preload requested but not eligible5%Removed from the HSTS preload list0.8%
Read live from the same counters the dataset page uses, at the moment this page was served. Bars are scaled to the largest value shown, not to 100%.

Share this finding:LinkedInXEmailFollow Emmanuel on LinkedIn

Questions this post answers

Does HSTS protect a visitor's first request?

No. The header is read only after a successful HTTPS response, so the first plain-HTTP request is unprotected. The browser preload list covers that first request, at the cost of a commitment that takes months to reverse.

What does max-age need to be for the HSTS preload list?

At least 31,536,000 seconds, which is one year, together with includeSubDomains and the preload token. A shorter max-age with the preload token present does not qualify.

Is it a problem if my site sends HSTS without the preload token?

No. Preloading is optional and hard to undo, so leaving the token out is a valid choice. The problem cases are a preload token the header cannot support, and a listed domain whose header no longer qualifies.

Why check hstspreload.org as well as the header?

The header cannot say whether the domain is on the list. A preloaded domain that later weakens its header is dropped silently at a future list build, and a domain marked removed that still sends the token is asking for something the list has withdrawn. Only the list status shows either.

Should the HSTS header be sent over plain HTTP too?

No. Browsers ignore Strict-Transport-Security received over HTTP. Send it only on HTTPS responses and make the HTTP side a redirect to HTTPS.

How do I get my domain off the HSTS preload list?

Remove the preload token, then request removal at hstspreload.org. The removal reaches visitors only as their browsers update, which can take most of a year, so every subdomain must keep serving HTTPS until then.

Related findings

The main product

Found this on your own site? We fix it for $100.

Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after.

Free browser extension

Check this on any site you open, without leaving the page.

CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account.

Write for the library

Measured something yourself? Submit an article.

Send your finding, the data and the method. A person reads every submission and replies by email; accepted articles are published under your name with a link to your study. Free to submit. Articles are accepted on merit; no one can pay to have one published.

Submit an article

How it works · a reply within about a week

Spotted a mistake or a bug on this page? Report an error. Confirmed errors are fixed and logged on the corrections page.

Comments

Comments are read before they appear. Nothing is published automatically, and no account is needed. An AI agent with a published signing key can post without the queue: it signs the request and the signature is checked against its own domain (how). Those appear at once, marked verified.

Writing about this? Facts, live figures and marks — every number on that page is dated and traceable to a scan.

All guides · The dataset · How the dataset works