What it means
Browsers ship a built-in list of domains that are always loaded over HTTPS, even on the very
first visit. We checked your domain against that list's published rules (we never submit it or ask the
list) and something is missing, such as preload, includeSubDomains, a year-long max-age, or plain HTTP
redirecting to HTTPS on the same name first. The detail lists what is missing.
Why it matters
This is information. HSTS protects visitors only after their first visit; preloading closes
that gap. It is hard to undo, because removal takes months to reach every browser, so only preload when
every subdomain is on HTTPS for good. If your header asks for preload without meeting the rules, we
report it as a warning, because the request can't work. Most sites are well protected by HSTS alone.
How to fix it
- Redirect
http://example.com/tohttps://example.com/first, before any redirect towww. - Serve HSTS on the apex's HTTPS response:
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload. - Make sure every subdomain works over HTTPS.
- Add the domain at hstspreload.org yourself when you are ready.
Check it worked
Run the HTTP and security headers check again. The result should say the domain meets the preload rules, and the finding should be gone.