DKDKCISSP
DNS Trust · Unauthorized TLS Certificates

Three country-code registries hijacked: how legitimate HTTPS certificates became an attacker asset

Google reported that attackers compromised third-party country-code domain registries for .gh, .sl and .as, modified authoritative DNS and obtained unauthorized HTTPS certificates for Google and other organizations' domains. Google's own systems were not breached.

Affected ccTLDs
3
Google systems breached
No
Unauthorized certificates
Confirmed
Chrome mitigation
CRLSets + revocation

Background

The domain name system connects human-readable names to internet infrastructure. Certificate authorities rely on domain-control validation when issuing HTTPS certificates. If an attacker can manipulate authoritative DNS, a certificate can be technically valid yet issued without the legitimate domain owner's authorization.

Google's Chrome Secure Web and Networking Team reported hijacks involving the country-code top-level domains .gh (Ghana), .sl (Sierra Leone) and .as (American Samoa). These involved third-party registries, not an intrusion into Google's systems or proven misconduct by certificate authorities.

The trust boundary attackers crossed

ccTLD registry.gh / .sl / .asDNS manipulationAttacker-controlledrecordsHTTPScertificatesUnauthorized issuanceCT log discoveryOther affected domainsBrowserprotectionBlock and revoke certs
Fig. 1 — Google-confirmed trust chain. The exact intrusion method at the registry operators is not publicly established.

What actually happened

Google said attackers compromised third-party ccTLD registries associated with .gh, .sl and .as, changed authoritative DNS records and obtained unauthorized HTTPS certificates covering several Google domains and domains of other organizations.

Chrome responded by blocking unauthorized certificates for Google properties through CRLSets and coordinating with issuing certificate authorities to revoke them. Certificate Transparency log analysis exposed additional potentially affected organizations; Chrome proactively blocked related certificates and Google contacted organizations where possible.

Google said its own systems were not compromised and that it had no reason to believe the issuing certificate authorities had acted improperly. The public report did not identify the attackers, disclose how registry systems were penetrated, or prove that all unauthorized certificates had been discovered.

A valid certificate can still be unauthorizedA certificate authority may correctly validate attacker-controlled DNS records while the underlying DNS authority has been hijacked. HTTPS alone does not establish legitimate ownership after upstream compromise.

Root cause

Confirmed
  • Attackers compromised third-party ccTLD registries and modified authoritative DNS records, according to Google.
  • Unauthorized certificate issuance followed the loss of DNS control.
Reasonable hypothesis — not confirmed
  • Google did not disclose the initial access method or exact controls that failed at the affected registry operators.
  • The public report does not prove successful traffic interception or phishing using each certificate.

Timeline

Third-party operators of .gh, .sl and .as were compromised, according to Google. Exact intrusion paths were not disclosed.
Attackers changed authoritative DNS, enabling domain-control validation.
Certificates were issued for domains the attackers did not legitimately control.
Chrome blocked certificates via CRLSets; issuing CAs revoked affected certificates; CT analysis identified additional cases.
Fig. 2 — Publicly documented sequence; precise initial compromise times remain undisclosed in Google's report.

Detection

How it was discovered

Google's Chrome team became aware of the registry hijacks and used Certificate Transparency analysis to identify further unauthorized certificates.

What to monitor for in your own environment

Unexpected certificate issuance for any owned or regional domain

Certificate Transparency monitoring

Unauthorized DNS record or nameserver changes

Authoritative DNS change audit

Certificates issued by an unapproved CA

CT and certificate inventory

Containment, eradication & recovery

Containment

  • Chrome blocked unauthorized certificates for Google properties via CRLSets and later blocked additional identified certificates.

Eradication

  • Google worked with issuing certificate authorities to revoke unauthorized certificates. Registry-side technical eradication was not disclosed.

Recovery

  • Google notified affected organizations where possible and advised domain owners to monitor CT, maintain restrictive CAA policies and verify their domain inventory.
  • Google cautioned that browser-side intervention alone cannot guarantee every affected certificate was identified or protect all clients.

Security control analysis

Failed
Third-party registry integrity

Attackers modified authoritative DNS through compromised registry operators.

Held
Certificate Transparency visibility

CT logs helped Google discover additional suspicious issuance.

Held
Chrome certificate blocking and revocation coordination

Google reported CRLSet blocking and work with CAs to revoke affected certificates.

Unknown
Complete cross-client protection

Google warned its browser-specific protections were not comprehensive across all clients.

Controls that would have prevented or limited this

Fix
Continuous CT monitoring for all owned domains

Alerts owners to unexpected issuance including regional and parked domains.

Closes: Third-party registry integrityCIS Control 1 — Inventory and Control of Enterprise Assets
Fix
Restrictive CAA records with account binding where supported

Constrains issuance options and improves detection of unauthorized certificate requests.

CIS Control 12 — Network Infrastructure Management
Fix
Independently verify registry and DNS change integrity

Detects unauthorized changes upstream of certificate issuance.

Closes: Third-party registry integrityCIS Control 12 — Network Infrastructure Management

Blast radius

Confirmed by Google

  • Three affected country-code namespaces: .gh, .sl and .as.
  • Unauthorized HTTPS certificates for Google domains and other organizations.
  • DNS record changes at compromised third-party registries.

Not established

  • Compromise of Google's own infrastructure.
  • Wrongdoing by the certificate authorities.
  • Exact attacker identity, registry intrusion mechanism or total affected domains.
  • Confirmed interception of any particular user's traffic.
Fig. 3 — Potential for impersonation is not evidence of proven traffic interception.

Distinct affected trust layers

Country-code namespaces3Google internal systems breachedNoTotal rogue certificatesNot fully known
Fig. 4 — Category widths are illustrative; they are not numerical comparisons.

What they got right

Chrome rapidly blocked known unauthorized certificates for Google properties.

Google coordinated revocation with issuing CAs and used CT logs to discover additional impacted domains.

The disclosure clearly distinguished third-party registry compromise from compromise of Google's systems.

Why this keeps happening

Domain validation trusts authoritative DNS; registry compromise can undermine the authority on which issuance depends.

Large organizations may have regional or parked domains outside their primary monitoring inventory.

Browser-specific protections do not automatically protect every browser, client or non-browser application.

Lessons for your own environment

  1. DNS is a security boundary

    If upstream DNS authority is compromised, downstream HTTPS validation can be abused.

  2. Monitor certificates you did not request

    CT monitoring exposes unauthorized issuance even when internal systems were not breached.

  3. A browser fix is not universal

    Different clients and applications may not receive identical emergency protections.

CISO & board lessons

  • Maintain a complete portfolio of regional, parked and delegated domains—not only primary corporate domains.
  • Require CT alerting, restrictive CAA and accountable ownership for external DNS changes.
  • Include registry and certificate-issuance dependencies in third-party concentration-risk reviews.

Action plan

First 24 hours

  • Review CT logs for unauthorized certificates across all affected and owned namespaces.
  • Check DNS and registry audit records and coordinate certificate revocation where required.

First 7 days

  • Validate CAA policies and ownership of regional and parked domains.
  • Assess non-browser clients that may not benefit from Chrome-specific blocking.

First 30 days

  • Automate CT monitoring and certificate inventory reconciliation.
  • Exercise DNS/registry incident response with external providers.

Could this happen in your organization?

  • Can we list every country-code domain owned by the organization?
  • Would we detect a certificate issued by an unexpected CA?
  • Are our non-browser applications protected when browser vendors block a rogue certificate?

If this happened to you: what to ask, and what to say

Knowing the lesson isn’t the same as knowing what to do with it Monday morning. A security lead, a CISO, and a customer-facing team each need something different from this incident.

  • Do we monitor CT for all regional domains?
    Include parked and delegated namespaces, not just the primary domain.
  • Was Google itself hacked?
    Google explicitly said its own systems were not compromised.
    The attackers compromised third-party domain registries and obtained unauthorized certificates. The case illustrates an upstream trust dependency rather than a breach of Google's own systems.
  • Does HTTPS always mean a site is legitimate?
    No; the domain-control validation chain can be abused after DNS hijacking.

References & confidence

  • ConfirmedGoogle Chrome Secure Web and Networking Team — Chrome's Response to Recent ccTLD Registry Hijacks (6 October 2026). https://blog.google/security/chromes-response-to-recent-cctld-registry-hijacks/ — Primary disclosure for registry compromise, DNS changes, certificates and Chrome response.
  • Analytical inferenceDKCISSP editorial analysis — domain monitoring and incident response recommendations — Recommendations are not assertions about undisclosed registry controls or attacker actions.
This case study is built entirely from public reporting on this incident — see References & confidence above for what's confirmed, reported, or still unconfirmed. Nothing here is an estimate or an illustrative placeholder.