How do you cancel a digital certificate that has been stolen?

A certificate can be valid for a year, yet worthless from the moment its secret key leaks. Cancelling it is harder than it sounds.

You cannot take it back from every computer that has seen it, so the internet uses published lists of cancelled certificates instead. A digital certificate is like a passport for a website, valid until its expiry date. If the secret key behind it leaks, the passport is still stamped 'valid' until someone says otherwise. Cancelling a certificate early is called revoking it. A certificate is if, for example, the certificate authority improperly issued it or its is thought to have been compromised.

The classic tool is the certificate revocation list, or CRL: a list of certificates that have been by the issuing authority before their scheduled expiration date and should no longer be trusted. A CRL has a lifetime during which it is valid, often 24 hours or less, so browsers fetch fresh ones. A newer tool, , lets a browser ask about one certificate at a time. It has a catch: the browser has to contact a third party, which could track what websites the client is accessing.

What cancelling trust looks like
  1. Step 1: A key leaks or an authority errs

  2. Step 2: The certificate is

    Before its expiry date

  3. Step 3: Revocation is published

    CRL, CRLSet or a status check

  4. Step 4: Browsers refuse the certificate

    Once they have the update

A recent real case shows the machinery at work. Google reported that on Saturday 17 October 2026 its Chrome team received a report that the private keys of eight certificates belonging to the company eMudhra had been compromised. Google said the keys had been made with weak randomness, so anyone could forge trusted certificates for any website, for clients that still trusted them. Under two hours later, Chrome pushed a list update, called a CRLSet, blocking them, without any browser update or restart.

Those are Google's reported facts, and the story was still developing as of October 2026. What lasts is the lesson: trust has to be cancellable, and cancelling it quickly is hard.

Quiz me

0/3

  1. 1.Why is a certificate not simply cancelled by its expiry date when a private key leaks?
  2. 2.Why did Google turn off OCSP checks by default in Chrome in 2012?
  3. 3.Why is a compromised subordinate certificate authority more dangerous than a single stolen website key?

Recap

Issuing trust is easy; the hard part is taking it back everywhere at once.

💡 A trick to remember it · A hotel key card can be switched off at the desk: the door only needs to ask the desk, or get the fresh list, before it opens.

Surprising fact · Chrome blocked the compromised eMudhra authorities without any browser update.

Sources (6)

No source, no claim. Every fact in this lesson (16 claims) cites at least one of these.

  1. [1]Certificate revocation list · Wikipedia
  2. [2]Online Certificate Status Protocol · Wikipedia
  3. [3]Let's Encrypt · Wikipedia
  4. [4]Certificate Transparency · Wikipedia
  5. [5]Protecting Chrome and Android Users from Compromised eMudhra Intermediate CA Certificates · Google
  6. [6]Chrome's Response to Recent ccTLD Registry Hijacks · Google
More lessons in 💻 Tech (3) See all tech lessons →

One more light on your map.

Get one lesson like this every day, about the things you love. Free, in two or five minutes.

Get the share card for this lesson ↗