← All posts

TLS Certs Now Expire in 200 Days. Is Your Renewal Working?

Remember when you'd buy an SSL certificate, install it, and forget about it for a year? Yeah, those days are over. Since March 15, 2026, a public TLS certificate can be valid for 200 days, max. Most certificate authorities now issue them for 199 days to leave themselves a little wiggle room.

And it doesn't stop there. The limit drops to 100 days in March 2027 and to just 47 days in March 2029. That's not a proposal or a rumor. It's an industry rule that every major browser and CA signed off on, and the first wave of 200-day certs already started expiring last month.

Here's my take: auto-renewal is great, and you should absolutely be using it. But it will fail at some point. When it does, you want to hear about it from a monitor, not from a visitor staring at a big red "Your connection is not private" screen.

The Timeline

Here's what the maximum certificate lifetime looks like over the next few years:

Before Mar 15, 2026 398 days Mar 15, 2026 (you are here) 200 days Mar 15, 2027 100 days Mar 15, 2029 47 days
Bar length is to scale. In 2029 you'll be renewing roughly every month instead of once a year.

It's not just the certificate itself, either. The time a CA can reuse your domain validation (the "yes, you really control this domain" check) shrinks too, down to just 10 days by 2029. So you can't validate once and coast. Your setup has to prove domain control over and over, automatically.

If you use Let's Encrypt, you're actually ahead of this curve, whether you like it or not. Their default certs drop from 90 days to 64 in February 2027 and to 45 days in February 2028. And heads up: they stopped sending expiration reminder emails back in June 2025. If you were counting on that email as your safety net, it's gone.

Why Shrink Them? Security, Mostly

The honest answer is that revocation doesn't really work. In theory, if a certificate's key gets stolen or a cert gets issued by mistake, the CA revokes it and browsers stop trusting it. In practice, browsers and devices check revocation inconsistently, lots of clients skip it entirely, and plenty of gadgets never check at all. A stolen or bad certificate tends to stay useful until the day it expires.

So the industry's fix is simple: make that day come sooner. If a cert only lives 47 days, a compromised one is only dangerous for 47 days, not 13 months. Shorter lifetimes also force everyone to automate, which means that when something goes wrong, swapping certificates is a non-event instead of a panicked all-hands weekend.

If that sounds theoretical, we just got a pretty wild real-world example.

The eMudhra Mess: When the CA Itself Is the Problem

In October 2026, eMudhra, an Indian certificate authority whose certificates protect businesses and government services (reportedly including India's income tax portal), had a very bad week.

It wasn't a hack in the movie sense. Nobody broke into their servers. Instead, a researcher noticed that eight of eMudhra's intermediate CA certificates, the ones that sit between a trusted root and the certificates websites actually use, had private keys that were laughably weak. A proper key for these certificates is a random number over 100 digits long. These keys were all smaller than 256. One of them was literally the number 4. Anyone with the public certificate could recover the private key in under a second.

And that's about as bad as it gets for a CA. With one of those keys, an attacker could sign a certificate for any domain, and browsers would trust it. That means impersonating sites, intercepting traffic, the whole nightmare.

The cause? A faulty script during a 2025 key ceremony generated a second batch of weak keys with labels similar to the real ones, and the weak ones got picked by mistake. Human error stacked on human error.

Here's how it played out:

  • Oct 17: The problem was reported to the browser vendors and eMudhra. Chrome and Firefox blocked the certificates the same day.
  • Oct 18: eMudhra revoked all eight intermediates.
  • Oct 19–20: Apple and Microsoft followed, and Mozilla pulled trust in the root that signed them.
  • Oct 22: eMudhra announced it was leaving the global TLS certificate business entirely. Around 30,000 customer certificates need to be replaced.

eMudhra says none of the weak intermediates were used to issue customer certificates and that no data was leaked. Credit where it's due, they moved quickly. But think about it from the point of view of a site owner using eMudhra certs. Your provider just exited the business, its root is distrusted, and you have to move to a new CA, probably on short notice.

Notice what saved the day, too. It wasn't revocation working the way it's supposed to. It was browsers pushing out emergency updates to stop trusting those certificates. Anything that doesn't get those updates, like old phones, embedded devices, and that IoT box in the corner, may keep trusting them for a long time.

That's the strongest argument for automation I can think of. If your certificates come from an ACME client and you've got monitoring in place, switching CAs is a config change and a renewal. If you've got a manually installed cert on a box nobody remembers, it's going to be a rough week.

How Auto-Renewal Actually Fails

Let's be real, "set up certbot and forget about it" works great until it doesn't. Here are the usual ways renewals quietly break:

  • The cert renewed, but the server never reloaded. The new certificate is sitting on disk while nginx happily serves the old one until it expires. This one is sneaky because every check on the server itself looks fine.
  • Validation stopped working. Someone added a firewall rule that blocks port 80, put a redirect in the wrong place, or moved DNS to a new provider and the DNS-01 API token didn't come along.
  • The scheduler died. You migrated servers, rebuilt a container, or switched from cron to systemd timers, and the renewal job just... didn't come with you.
  • Hardcoded intervals. A script that renews "every 60 days" is fine for 90-day certs and catastrophic for 45-day ones.
  • The CA changed under you. Rate limits, a distrusted CA, an API change. Like the eMudhra situation, sometimes the problem isn't on your end at all.

The common thread is that renewal failures are silent. Nothing pops up and tells you. Today, with a 200-day cert, a broken renewal might sit there unnoticed for months before it bites. With 47-day certs, you'll have a couple of weeks at best.

A couple of quick sanity checks you can run right now:

# What certificate is the server actually serving, and when does it expire?
echo | openssl s_client -connect www.example.com:443 -servername www.example.com 2>/dev/null \
  | openssl x509 -noout -enddate

# Does renewal actually work end to end?
sudo certbot renew --dry-run

And if you're on certbot with nginx, make sure there's a deploy hook so the server picks up the new cert:

sudo certbot renew --deploy-hook "systemctl reload nginx"

Let a Monitor Watch the Expiry Date

This is where uptime monitoring earns its keep. I wrote about why uptime monitoring matters a while back, and one feature I barely mentioned turns out to be the most important one here: the SSL expiry option on an HTTP check.

Most monitoring tools, free ones included, let you tick a box on a regular HTTP monitor that also checks the certificate. The monitor connects to your site the same way a visitor's browser does, looks at the certificate it's actually served, and alerts you when the expiry date gets close. That's exactly what you want, because it catches every failure mode in the list above, including the "renewed on disk but never reloaded" one that checks on the server itself miss.

A few tips to get the most out of it:

  • Set the alert threshold below your renewal point. If your client renews at about two-thirds of the way through a cert's life, there should always be plenty of days left. Something like 21 days for today's certs works well. Once you're on 45 or 47-day certs, around 10 days is a good alarm bell. If you get that alert, renewal already failed at least once.
  • Monitor every hostname. www and the bare domain often have separate certificates (or at least separate configs). Same goes for your API, mail server, and that admin subdomain.
  • Check from outside your network. Your monitor should see what your visitors see, through the same CDN or reverse proxy.
  • Keep TLS verification on. A check that verifies the full chain will also complain if your certificate chain breaks or your CA's certs stop being trusted, as long as its trust store stays up to date.

Shorter certificates are honestly a good thing for security. They make stolen keys less valuable, and they make situations like eMudhra's way less painful for the people caught in the middle. But they also turn "renew once a year" into "renew every month, forever," and anything that happens that often will break eventually. Automate the renewal, then put a monitor on top of it. Five minutes of setup today beats an expired certificate at 3 AM.