Skip to content
AdminKit

HSTS preload list

What is HSTS preload list?

The HSTS preload list is a hardcoded browser list, maintained via hstspreload.org, that forces HTTPS from a domain's very first connection, closing a bootstrap gap in RFC 6797's HSTS header. Ordinary HSTS only protects a domain after a browser's first successful HTTPS visit. AdminKit's guide explains why preloading isn't recommended for every site.

By AdminKit team, Netbase JSC · Updated

The HSTS preload list is a hardcoded list baked directly into Chrome’s source code — and, via lists derived from it, into Firefox, Safari and other major browsers — that forces every connection to a listed domain onto HTTPS from the very first request a browser ever makes to it, with no prior visit required. It exists to close a gap in RFC 6797’s HTTP Strict Transport Security (HSTS) header, whose current document status is tracked at its IETF Datatracker entry: HSTS only takes effect after a browser has already seen the header once over a successful HTTPS connection, leaving a domain’s very first connection unprotected if it happens to start over plain HTTP. A site submits itself for preloading at hstspreload.org, but every current and future subdomain must support HTTPS indefinitely first, since both addition and removal from the list take months to propagate through browser release cycles. MDN’s Strict-Transport-Security reference adds that when the header’s preload directive is used, max-age must be at least 31536000 seconds (one year) and the includeSubDomains directive must be present.

The header itself, and how a browser stores and enforces it, is covered in AdminKit’s HSTS entry. HSTS preloading is one of several “lock in a security decision ahead of time” mechanisms AdminKit’s glossary covers, alongside certificate pinning and a Content-Security-Policy’s own allowlisting approach.

HSTS preload list is part of AdminKit’s machine protocols cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

What gap does the HSTS preload list close?

Ordinary HSTS (RFC 6797) only takes effect after a browser has already seen the header once over a successful HTTPS connection, leaving a domain's very first connection unprotected if it happens to start over plain HTTP. Preloading forces HTTPS from that very first request, with no prior visit required.

How does a site get added to the HSTS preload list?

A site submits itself for preloading at hstspreload.org, but every current and future subdomain must support HTTPS indefinitely first.

Can a site easily remove itself from the preload list?

Not quickly -- both addition and removal from the list take months to propagate through browser release cycles, since the list is baked directly into Chrome's source code and, via lists derived from it, into Firefox, Safari and other major browsers.

Where does the preload list actually live?

It's hardcoded directly into Chrome's source code, and other major browsers like Firefox and Safari ship lists derived from that same source rather than maintaining a fully independent one.