Attackers meanwhile hijacked three country domain namespaces and used that control to obtain fraudulent TLS certificates for several Google domains. RocketNews summarises an Ars Technica report on a Google announcement. DNS hijack TLS certificates also covered domains from several leading global brands, although Google did not name the other brands or its own domains. Owners’ own infrastructure stayed uncompromised, Google says.
The affected namespaces for example were gh for Ghana, sl for Sierra Leone, and as for American Samoa. They modified authoritative DNS records inside those namespaces. Control checks then passed, since certificate authorities saw DNS proof that looked valid. Automated checks cannot spot a lie when the layer above the domain tells it. Google has warned about hijacked browser extensions before, while the Chrome extension hijacking cases show how far that abuse can reach.
TLS certificates meanwhile act as digital identity cards for websites, and browsers trust them to prove a site matches its name. Fraudulent certificates let attackers impersonate real services over encrypted connections. Victims could face phishing pages, intercepted data, or malware downloads without a browser warning. Padlock trust rests on honest DNS and honest issuance.
Its team revoked the fraudulent DNS hijack TLS certificates through certificate authorities and blocked them in Chrome. Blocks as a result arrived through CRLSets, the emergency block mechanism for certificates. Certificate authorities complied with all requirements during issuance, Google says, and Google finds no fault with the issuers. The weakness sat in the hijacked namespaces, not in the certificate process itself.

Its analysts warn that the analysis may miss some affected domains, given the complexity of DNS hijacks. Browser interventions may not protect users of other browsers and apps reliably. Domain owners meanwhile should monitor Certificate Transparency logs across their full portfolio, including parked and regional domains. Owners with gh, sl, or as domains should review recent entries for unexpected certificates.
Google advises domain owners to set restrictive CAA records, which name the certificate authorities allowed to issue for a domain. CAA records alone cannot stop issuance during an active DNS hijack TLS certificates attack, however they narrow the field for attackers in normal times. Account bound CAA records add another layer by tying issuance to a specific account. Defence works best as layers, not as a single control. A Google security warning sparked a patch rush in an earlier incident, which shows how quickly Google moves when a flaw spreads.
Country domain operators for example run critical infrastructure, and a compromise at that layer affects every domain beneath it. Single registry failures can expose thousands of sites that did nothing wrong. Small registries may lack the security budgets of large global operators. Attackers hunt for the weakest link in a trust chain, and registries present a tempting target. Global brands and small site owners share the same risk when a namespace falls.

Certificate Transparency logs meanwhile give the internet a public audit trail for certificates, and owners should treat log alerts as early warnings. Cloudflare and Cert Spotter send alerts when a new certificate appears for a watched domain. Quick checks after an alert can catch the fraudulent DNS hijack before attackers exploit them. Chrome extension hijacking shows how silent abuse spreads, but log monitoring turns silence into signal.
History offers a stark parallel from 2011, when the DigiNotar breach let attackers mint fraudulent certificates for Google and hundreds of other domains. That breach, thus, ended the certificate authority involved. This DNS hijack TLS certificates case differs, since the weak point was registry control rather than a certificate authority. Trust systems fail at different layers, and defenders must watch every layer.
Ordinary Chrome users meanwhile need take no action for the blocked Google certificates, Google says. Chrome already blocks the known fraudulent certificates for Google properties. Domain owners carry the heavier duty, since they must audit logs and tighten CAA records. App store controls and YouTube channel protections show how Google keeps tightening platform trust after abuse. Attackers have redirected domains at the registrar layer before, and the domain redirect attacks reached 12 protocols through that route.
Trust on the web meanwhile rests on quiet machinery that most people never see, and a hijacked registry can shake that trust in days. The DNS hijack reminds owners that a domain name needs care long after purchase. Monitor the logs, set strict CAA records, and check regional domains with the same care as flagship domains. Padlocks should mean safety, and safety demands vigilance at every layer.
