Skip to content
// glossary

What is HSTS preload?

also: HSTS preload list

// short answer

A list built into major browsers of domains that must only ever be loaded over HTTPS, even on a visitor's very first visit.

In plain English

Normal HSTS only works after a browser has visited your site once and seen the Strict-Transport-Security header. HSTS preload closes that first-visit gap: browsers such as Chrome, Firefox, Safari and Edge ship with a list of domains that must always use HTTPS, so they never try plain http:// at all.

To be accepted, a domain typically has to serve a valid certificate, redirect http:// to https://, and send an HSTS header on the HTTPS site with a max-age of at least one year, plus includeSubDomains and preload. You then submit the domain at hstspreload.org.

A header that meets the usual preload requirements
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

Why it matters to a small business

Preloading gives the strongest HTTPS guarantee, but it is hard to undo. Removal from the list can take months to reach every browser, and every subdomain must work over HTTPS, including old ones you may have forgotten, such as a mail or test subdomain. For most small businesses, ordinary HSTS is enough; preloading is a deliberate step, not a default.

What to do

  • First make sure your site and every subdomain work over HTTPS, and run the security headers checker to confirm HSTS is in place.
  • Run HSTS with includeSubDomains for a few weeks before adding preload.
  • Only submit to the preload list once you are sure you will keep HTTPS on every subdomain for good.

Does your site get HSTS preload right?

Find out in about 30 seconds with the free, passive check. Nothing is attacked and nothing is stored.

Talk to a human