·

Counterfeit TLS Certificates: How DNS Hijacks Break Web Trust

A recent report from Ars Technica breaks down a critical incident where attackers managed to generate valid digital security certificates for high-profile domains without breaking into the companies’ actual servers. The attackers compromised three country-code domain registries (.gh, .sl, and .as) and modified the authoritative Domain Name System (DNS) records. Because certificate authorities rely on automated checks to confirm that an applicant controls a domain before handing out a certificate, poisoning these registry records allowed the attackers to pass validation easily. This granted them unauthorized certificates for “several Google domains” alongside “several leading global brands and widely used online services.”

To understand why this matters, think of a TLS certificate as an authentic digital passport for a website. It proves the site is who it claims to be and encrypts the connection between the user and the server. As the report explains, “Possession of unauthorized certificates allows attackers to cryptographically impersonate the affected infrastructure.” When attackers hold a legitimate certificate, they can sit between a user and a real service, intercepting sensitive logins or decrypting private data, all while the visitor’s browser displays a trusted padlock icon with zero security warnings.

Even though Google acted quickly to block rogue certificates inside Chrome and revoke its own keys, client-side fixes have clear boundaries. The traditional revocation system that tells browsers a certificate is no longer trustworthy is slow and inconsistent across the internet. Google noted this exact limitation, warning that “Due to the complexity of DNS hijacks, we cannot guarantee that our analysis identified every affected domain, nor do Chrome interventions reliably protect non-Chrome users.” Anyone connecting through other web browsers, mobile apps, or backend API scripts could still be fooled by an undiscovered, fraudulent certificate.

This attack highlights why security teams cannot focus entirely on securing endpoint servers while ignoring the external trust chain. Defending against registry tampering requires layers of proactive monitoring. Organizations must track Certificate Transparency (CT) logs, which act like public ledgers recording every certificate issued worldwide, so rogue creations get spotted immediately. Additionally, teams should enforce Certification Authority Authorization (CAA) DNS records, which explicitly tell the internet which certificate authorities are allowed to issue certificates for a specific domain name.

Projects

Articles

, , , , , ,