-
Notifications
You must be signed in to change notification settings - Fork 13
Open
Labels
Description
I see that https://govinfo.gov and https://www.govinfo.gov both use an HSTS header, and in general govinfo.gov is a relatively new domain that I would expect to have fewer legacy internal services at subdomains of govinfo.gov that might rely on plain HTTP.
Could govinfo.gov be preloaded into browsers as HTTPS-only, as the executive branch is doing with all new .gov domains and offering as an opt-in to other new .gov domains?
This would enforce HTTPS-only at all times, even if the user has never been to govinfo.gov at all, no matter what subdomain or URL they may visit within the zone.
Reactions are currently unavailable