HSTS preload list
The header asks to be shipped in the browsers’ own HTTPS-only list. The list wants max-age of at least a year and includeSubDomains before it will accept a domain.
Even with HSTS, the very first visit to a site starts over plain HTTP, because the browser has not yet seen the header. The preload list closes that gap: it is a list of domains built into Chrome, Firefox, Safari and Edge, which they open only over HTTPS from the first request. A domain gets on it by sending the preload token in its HSTS header and submitting itself at hstspreload.org.
How SiteScan checks it
This row appears only when the HSTS header contains preload. The scanner then checks the list's terms that can be read from the header: max-age of at least one year (31,536,000 seconds) and includeSubDomains. If both are there, the row shows “Present”; if not, “Terms not met” in amber — the list would reject the domain, yet the header suggests otherwise. SiteScan does not query the list itself, so submitting is still up to you.
Before you preload
Preloading is optional and hard to undo: removal takes months to reach browsers. Every subdomain, including internal ones, must work over HTTPS. The full header looks like this:
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
The HTTP address must also redirect to HTTPS on the same host.
See this check on your own site
Run a free scan: the report shows this row for your domain along with the other checks of the site audit.
More in “Security headers”
What SiteScan checks
TLS certificate
- TLS certificate expiry
- Outdated TLS versions (TLS 1.0/1.1)
- TLS certificate chain
- TLS certificate issuer
- Certificate signature algorithm
Domain registration
- Domain registration expiry
- Registered domain name
- Domain registrar
- Domain registration date
- Domain last updated date
- Domain status codes (EPP)
- Domain transfer lock
- Registrar abuse contact
- RDAP and WHOIS data source
Indexing
- robots.txt file
- CSS and JS blocked in robots.txt
- XML sitemap
- Sitemap index file
- Off-domain URLs in the sitemap
- Sitemap lastmod dates
- Broken URLs in the sitemap
- RSS and Atom feed
Addresses & redirects
Security headers
- HTTP security headers and grade
- Strict-Transport-Security (HSTS) header
- Content-Security-Policy (CSP) header
- X-Content-Type-Options: nosniff
- X-Frame-Options and clickjacking
- Referrer-Policy header
- Permissions-Policy header
- HSTS preload list
- CORS and cross-origin reads
- HTTP TRACE method
Delivery & reputation
- Cache-Control header for HTML
- ETag and Last-Modified revalidation
- HTTP/3 and QUIC support
- Server version disclosure in headers
- DNS blocklist (DNSBL) check
Internal links
Exposure
- Exposed sensitive files (.env, .git, backups)
- Directory listing enabled
- Public JavaScript source maps
- Exposed WordPress endpoints
Well-known files
- security.txt file
- llms.txt for AI assistants
- llms-full.txt file
- ads.txt authorized sellers file
- humans.txt file
- Well-known change-password URL
DNS & email
- MX records (mail servers)
- SPF record
- DMARC record and policy
- DNSSEC signing
- CAA record
- Nameserver redundancy
- IPv6 support (AAAA record)
- MTA-STS policy
- TLS-RPT reporting record
- BIMI record (brand logo in email)
- Wildcard DNS record
- Dangling CNAME and subdomain takeover
Privacy & consent
- Analytics and tracking scripts
- Cookie consent banner
- Privacy policy link
- Terms of service link
- Imprint (Impressum)
- Accessibility statement
Core Web Vitals
- Lighthouse performance score
- Largest Contentful Paint (LCP)
- Cumulative Layout Shift (CLS)
- Interaction to Next Paint (INP)
- CrUX field data vs lab data