HSTS Preload Checker
Look up a hostname in a dated Chromium HSTS preload snapshot. Compare exact and inherited entries, a saved submission response and saved HTTPS headers.
Trace HSTS Preload and Saved Header Evidence
HSTS Preload Checker: how to use it
- Enter the hostname or an HTTP(S) URL. Check the pin date before interpreting the result.
- Optionally paste the saved preload status JSON for the same hostname and HTTPS response status lines and headers for the observed hops.
- Choose Check preload evidence. Review the snapshot match, saved submission status and header findings, or download the JSON report.
Limits and notes
Uses a pinned Chromium source list and locally supplied evidence. The status JSON can contain up to 16,384 characters and the captured headers up to 50,000. A current submission decision also depends on live HTTPS, redirects, certificates and the submission service.
How your privacy works →HSTS Preload Checker: common questions
How can a hostname match without its own preload entry?
A parent entry can include its subdomains. The check shows the nearest matching snapshot name and whether it covers descendants.
Does the preload directive mean a site is already on the list?
The directive indicates that the captured header requests preloading. Snapshot inclusion and saved submission status are separate evidence.
Why can a saved response differ from the Chromium snapshot?
The submission service and Chromium source list represent different observations. Browser builds also ship snapshots on their own release schedules.