The HSTS preload list is built into browsers: a domain on it is HTTPS-only from the very first visit. Since January 2025 hstspreload.org itself says preloading is not recommended — browsers now try HTTPS first on their own — and getting off the list takes months. Here is what it asks, and what it costs.
| Run by | The Chrome team, at hstspreload.org |
| Used by | Chrome, and lists based on it in Firefox, Safari and Edge |
| Header needed | max-age of at least a year, includeSubDomains and preload |
| Removal | Takes 6–12 weeks to reach most Chrome users |
| Recommended by hstspreload.org | No, since January 2025 |
Check HSTS preloading on your site
Enter a domain: we fetch its homepage and read every security header, this one first.
What it does
Ordinary HSTS starts working only after a browser has seen the header once, so the first visit to a site can still be downgraded. The preload list closes that gap: domains on it are compiled into the browser as HTTPS-only for the domain and every subdomain, before the first visit. Chrome maintains the list, and Firefox, Safari and Edge base their own lists on it.
hstspreload.org changed its advice in January 2025. Chrome and Safari now upgrade navigations to HTTPS on their own and fall back to HTTP only if HTTPS fails, so preloading adds protection only when an active attacker blocks that upgrade. In its words, the benefits of preloading are minimal compared with HSTS itself, and while HSTS is recommended, HSTS preloading is not.
What hstspreload.org requires
| Directive or value | What it does |
|---|---|
A valid certificate | The domain serves HTTPS with a certificate browsers accept. |
Redirect on the same host | If the domain listens on port 80, it redirects HTTP to HTTPS on the same host first. |
Every subdomain on HTTPS | Including www if it has a DNS record, and internal subdomains that are not public — preloading covers all of them. |
max-age=31536000 or more | On the base domain’s HTTPS responses; an extra redirect from HTTPS must carry the header too. |
includeSubDomains and preload | Both directives present in that header. |
What to send
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
That is the example hstspreload.org gives. Sending preload counts as asking to be listed, and you must keep meeting every requirement for as long as you stay on the list — a site that stops may be removed automatically.
Common mistakes
- Sending preload by default because a guide or plugin included it — hstspreload.org says many site owners have joined the list without realising.
- Preloading a domain with an internal or legacy subdomain that cannot serve HTTPS: it becomes unreachable in every browser that ships the list.
- Expecting removal to be quick: it takes 6–12 weeks to reach most Chrome users, and longer for other browsers.
What we recommend
Most sites should send HSTS without preload. Preload only a domain you are sure will serve HTTPS on every subdomain for years — typically a bank, a login domain or a brand new domain with nothing old on it.
Questions
How do I get off the HSTS preload list?
Remove preload from the header (keep a valid HSTS header and certificate), then use the removal form at hstspreload.org/removal. It takes 6–12 weeks to reach most Chrome users and may take longer for other browsers.
Is preloading still worth it?
Rarely. hstspreload.org no longer recommends it, because browsers now try HTTPS first by default; it helps only against an attacker actively blocking that upgrade.
Sources
Checked on 25 September 2026 against these official sources:
- HSTS Preload List Submission — hstspreload.org
- HSTS Preload List Removal — hstspreload.org
- Strict-Transport-Security header — developer.mozilla.org
- RFC 6797: HTTP Strict Transport Security (HSTS) — rfc-editor.org