Info

Not eligible for the HSTS preload list

The short version

Meet the preload requirements if you want browsers to use HTTPS before the first visit.

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

  1. Redirect http://example.com/ to https://example.com/ first, before any redirect to www.
  2. Serve HSTS on the apex's HTTPS response: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload.
  3. Make sure every subdomain works over HTTPS.
  4. 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.