HTTP and browser security guides

Trace a hostname's inherited HSTS preload evidence

·

A hostname can inherit HSTS from a parent entry even when the hostname never appears as its own row in the preload list. Compare the snapshot, a saved submission response and the observed HTTPS headers before explaining which evidence accounts for an upgrade.

HSTS Preload Checker

Find why a .dev hostname matches

Choose Load example and Check preload evidence. The fixture uses the synthetic hostname shop.example.dev and a sample saved status response. The pinned Chromium list reports Inherited match because the nearest entry is dev with Includes subdomains set to Yes.

Clear the two optional evidence fields and check dev by itself. The match changes to Exact match. Check example.com to see No match in the same pin. The checker interprets only the dated source list for these results.

Pinned Chromium HSTS preload source listChromium's preload lookup

Compare the saved status and the two HTTPS hops

Load the example again. The saved JSON follows the submission status response shape and records Preloaded, with dev as the preload domain. The example values describe a fixture; for your own review, paste the response you saved for the exact hostname.

The first response is 301 and has only 86,400 seconds of max-age. The later 200 response records 31,536,000 seconds, includeSubDomains and preload. It meets the three header criteria. Current eligibility also depends on the certificate, redirects, HTTPS support and the submission service.

Compare the saved status and the two HTTPS hops
ObservationExpected evidence
Pinned list for shop.example.devInherited entry from dev
Saved JSONPreloaded under dev
Saved HTTP 301Header criteria incomplete
Saved HTTP 200Meets preload header criteria

Chromium HSTS Preload List SubmissionRFC 6797, Strict-Transport-Security

Record which evidence supports the conclusion

Open the JSON report and check provenance. It gives the Chromium source commit, UTC date and input data digest. The capture summary lists the status and HSTS facts for each saved response. Cookies, other raw headers, URL paths and query strings are left out of the report.

When a saved status is pending or unknown, use that wording in your notes. The runtime behavior of a specific browser also depends on its installed list and previously learned policies.

Pinned Chromium HSTS preload source listChromium HSTS Preload List Submission

Common questions

What should I check if the snapshot and saved response disagree?

Compare the source commit date and capture time. A submission service and an installed browser can reflect different points in the update cycle.

If the parent includes subdomains, does every child always match?

A more specific exact-only snapshot entry can stop inherited coverage for its own descendants. Review the nearest entry shown by the checker.

Can the saved 200 response prove preload eligibility?

It can show the observed preload header directives. A current eligibility decision also evaluates certificates, redirects, HTTPS availability and the submission service.

Sources

Put it into practice.

Related guides