The HSTS preload list is a list of domains shipped inside browsers that are treated as HTTPS-only from the very first request. Unlike the plain Strict-Transport-Security header, which a browser can only learn after one secure visit, a preloaded domain is protected from the start.
Why it matters
The ordinary header leaves a gap on first contact and after the stored policy expires. Preloading closes it. The list is maintained at hstspreload.org and used by major browsers. To qualify, you serve a valid certificate, redirect HTTP to HTTPS on the same host, serve HTTPS on all subdomains, and send an HSTS header on the root domain with a max-age of at least one year plus includeSubDomains and preload.
Example
Header that meets the submission rules:
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
Then submit the domain at hstspreload.org. Removal is possible but slow, because it only takes effect when browsers ship new versions.
Common mistakes
- Submitting before auditing every subdomain, including forgotten internal and staging hosts.
- Treating the submission as a setting you can undo this week.
- Adding
preloadto the header and assuming the domain is on the list. You still have to submit it.
Related
- HSTS
- SSL stripping
- Guide: HSTS preload guide
- Tool: HSTS checker
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.