Info

HSTS doesn't cover subdomains

The short version

Add includeSubDomains once every subdomain serves HTTPS.

What it means

Your HSTS header has no includeSubDomains directive, so the rule applies only to the exact name that sent it. Subdomains such as shop.example.com can still be reached over plain HTTP.

Why it matters

This is information. Without includeSubDomains, an attacker can use a plain HTTP subdomain to set or read cookies scoped to the whole domain. The HSTS preload list requires the directive, because preloading applies to the domain and everything under it.

How to fix it

  1. List your subdomains, including internal tools, mail web interfaces and old marketing sites.
  2. Make sure each one serves HTTPS with a valid certificate, or remove its DNS record.
  3. Add the directive: Strict-Transport-Security: max-age=31536000; includeSubDomains.
  4. Send it from the apex domain (example.com), not only from www, so it covers every name.

If a subdomain must stay on plain HTTP, leave the directive out; browsers would refuse to load it.

Check it worked

Run the HTTP and security headers check again. The HSTS row should mention subdomains, and the finding should be gone.