Chrome blocked bad certs after .gh / .sl / .as registry hijacks
On October 6, 2026 Google explained Chrome's response to .gh, .sl, and .as ccTLD registry hijacks: attackers changed DNS and got unauthorized HTTPS certs; Chrome blocked them via CRLSets. Chrome users need no action.