You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 17, 2021. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: