Mozilla disclosed that the private keys of eight eMudhra intermediate certificates were compromised. Firefox blocked them within three hours, and eMudhra and Sectigo revoked all 16 copies. Which certificates are affected, why it matters even if you never used eMudhra, and what to check.
GoDaddy is revoking 404,607 TLS certificates because the policy lines inside them don't match its own published rulebook, and it has missed the five-day deadline. What went wrong, which certificates are affected, and what to do before yours is revoked.
If your certificate's start date is more than 48 hours before it was actually issued, industry rules call that backdated, and your CA has 5 days to revoke it once it finds out. Nothing is wrong on your end. Here's what backdating means, a real 2026 example, and what TLS Radar checks for it.
Revocation doesn't change your certificate file, so you can't tell by looking at it. Here's how revocation checking actually works, why a one-off check is only a snapshot, and what it means when even the check itself is broken.
An annual WebTrust audit found four sampled certificates with no evidence that multi-perspective domain validation was performed. The full investigation found 2,700, and SSL.com revoked them all within a day. What MPIC is, why you could not have seen this one coming, the second SSL.com incident you can check for yourself, and what TLS Radar's new revocation checking does about it.
In the two weeks ending August 27, 2026, more than 30 public CAs logged 69 compliance incidents in Mozilla's tracker - delayed revocations, country-field and clientAuth misissuance, and the process failures that precede distrust. Every incident sourced to its Bugzilla bug, grouped by what it means for the certificates your business depends on.
One CA revoked 1.7 million certificates in 24 hours on April 3, 2026, following a compliance-driven mandatory revocation event. Five categories of mass revocation triggers, the timeline between revocation and customer impact, and why internal monitoring misses all of them.
On March 19, 2026, Let's Encrypt simulated a 3 million cert mass revocation. Two weeks later, another CA revoked 1.7 million real certificates in 24 hours. Both events told the same story: your CA can revoke your cert for reasons you don't control, and most renewal automation won't respond in time.
A mid-sized public CA's internal compliance documentation fell out of sync with its issuance system, forcing two separate mass revocations in July 2026. What happened, why it isn't a HARICA-specific problem, and how to check whether you're exposed to the next one.
Two reasons Chrome and Brave throw NET::ERR_CERT_AUTHORITY_INVALID: distrusted legacy roots (SSL.com 2016, DigiCert G1, Entrust) - the live, current cause - and CA-side compliance revocations, illustrated by a mid-sized CA's forced revocation of 63,525 certificates in July 2026. CA-agnostic diagnostics and fix steps.
Subscribe via RSS.