Skip to content
This repository has been archived by the owner on Dec 17, 2021. It is now read-only.

Measure whether a domain is actually in the Chrome preload list #30

Closed
konklone opened this issue Jun 19, 2015 · 4 comments
Closed

Measure whether a domain is actually in the Chrome preload list #30

konklone opened this issue Jun 19, 2015 · 4 comments

Comments

@konklone
Copy link
Contributor

Get the Chrome preload list from source control somehow, and measure whether the domain is actually in there. This can help eliminate the gap between what we think is preload-ready and what actually made it.

@garrettr
Copy link
Contributor

@konklone Do you think it would be worth implementing this upstream in site-inspector?

@konklone
Copy link
Contributor Author

cc @benbalter to get his thoughts. My suspicion is no, since it's looking up the domain's status in an external source, rather than inspecting the domain's technical configuration.

@benbalter
Copy link
Contributor

Assuming we can write a script to wget the HSTS preload list and vendor it into the Gem, I'd gladly merge a pull request that adds a check as to whether the domain is on the list.

@konklone
Copy link
Contributor Author

@benbalter Cool, that's only upside for site-inspector. @garrettr contributed Python code to do exactly this in our scanner: https://github.com/18F/domain-scan/blob/master/scanners/inspect.py#L18-L41

One crucial aspect of it for batch scans is caching the HSTS list once, at the top of the scan, to avoid redownloading/reparsing it once for every domain.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants