Hackers Got Real HTTPS Certificates for Google Domains — How? Cybersecurity Today

Attackers obtained unauthorized HTTPS certificates covering Google domains after hijacking infrastructure behind three country-code domain namespaces. Google says its own systems were not compromised. Instead, attackers compromised infrastructure associated with .gh, .sl and .as, changed authoritative DNS records, and used that apparent domain control to obtain trusted certificates. In today's Cybersecurity Today, we explain how attackers can manipulate the trust systems behind HTTPS without breaking encryption, why a browser padlock does not tell the entire security story, and what organizations should do to monitor certificate issuance and protect DNS infrastructure. The key lesson is simple: HTTPS still matters. But trust is a chain — and attackers may target the infrastructure underneath the security control everyone is watching. Stay informed. Stay skeptical. And stay secure. #Cybersecurity, #Google, #HTTPS, #DNS, #CyberSecurityNews, #InfoSec, #WebSecurity, #TLS, 00:00 – Introduction: How Did Hackers Get Real HTTPS Certificates? 00:30 – The Global Impact of the DNS Attacks 01:30 – How Attackers Manipulated Domain Control 02:30 – HTTPS Encryption vs. Website Trust 03:00 – Certificate Transparency and Suspicious Certificates 04:00 – The Security Checkpoint Analogy 04:30 – How Google and Chrome Responded 05:00 – Three Practical Lessons for Defenders 05:30 – Certificate Transparency and CAA Records 06:30 – Why DNS Security Matters 07:00 – Understanding the HTTPS Padlock 08:00 – Could a Valid Certificate Still Be Dangerous? 08:30 – DNS, Identity Security, and the Bigger Picture 09:00 – Final Takeaways and What's Next RIB2ZYUOUL4TAJRD