What this check inspects
Shipwork reads the Strict-Transport-Security header and its directives, checks the domain against the HSTS preload status service, looks for an alt-svc header advertising HTTP/3, and queries a public DNS-over-HTTPS resolver for a DS record to determine whether DNSSEC is enabled.
What a failure means
No HSTS is a warning: a first visit can be downgraded to http. HSTS without preload or without includeSubDomains is informational, since there is still a gap. HTTP/3 not advertised and DNSSEC not enabled are informational. None of these are page-level errors, but each is a real protection left off.
How to fix it
- Enable HSTS with a long max-age, then add includeSubDomains once every subdomain is https.
- Submit the domain to the HSTS preload list once HSTS is stable.
- Enable DNSSEC at your registrar and at your DNS provider, and publish the DS record.
- Check whether your CDN or host supports HTTP/3 and turn it on where available.
A typical failure, worked through
The setupA store enables HSTS but not includeSubDomains, and a shop subdomain that only serves http is added six months later.
What the check reportsThe check reports HSTS present without includeSubDomains, and no preload. The main host is protected, but the subdomain remains a downgrade path.
The pointHSTS without includeSubDomains protects the host and nothing below it. Decide subdomain coverage deliberately rather than by omission.