CertiMonitor

Blog

Certificate lifetimes are dropping to 47 days

Jaime Guerrero · · 2 min read

Since March 15, 2026, a public TLS certificate can be valid for at most 200 days. Until then the limit was 398. It drops again to 100 days in March 2027 and to 47 days in March 2029.

The change comes from ballot SC-081v3 at the CA/Browser Forum, where certificate authorities and browser vendors agree on the rules every public certificate follows. It passed in April 2025 without a single vote against.

The schedule

FromMax certificate lifetimeDomain validation reuse
Before March 15, 2026398 days398 days
March 15, 2026200 days200 days
March 15, 2027100 days100 days
March 15, 202947 days10 days

The last column gets less attention than it deserves. Domain validation is the check where the CA confirms you control the domain, usually through a DNS record or a file on your server. Today a CA can reuse that check for months. From 2029 it has to repeat it every 10 days, so whatever your renewal relies on has to keep working every time it runs.

Why the browsers want this

A certificate is trusted for its whole lifetime, even if the key leaks or the domain changes hands. Revocation was supposed to handle those cases, but browsers don't check it reliably, so in practice a bad certificate stays trusted until it expires. Shorter lifetimes cap that window. They also make manual renewal impractical, which is the point: the browsers want everyone on automation.

What I'd do now

At 47 days you renew roughly eight times a year per certificate. If any of your certificates are still renewed by hand, start there.

  1. Move everything you can to ACME (how ACME issuance works). Let's Encrypt and ZeroSSL are free, most paid CAs have an ACME endpoint, and certbot, Caddy, Traefik, cert-manager and most load balancers and CDNs support it.

  2. Make validation work without a person. If your DNS challenge depends on someone adding a TXT record, use a DNS provider with an API instead, or HTTP validation.

  3. Check what the server actually serves. A common failure isn't a renewal that failed but one that worked while the web server kept serving the old certificate, because nothing reloaded it. You can check from your own machine:

    echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null \
      | openssl x509 -noout -enddate
    
  4. Look at intermediate certificates too. They expire, and occasionally before the certificate they signed.

  5. Adjust your alerts. A 30-day warning made sense when certificates lasted a year. With short lifetimes, what matters is a certificate that should have renewed by now and hasn't.

Where monitoring helps

Automation fixes the renewal. You still need to know when the automation stops working: an API token expires, someone changes DNS providers, a firewall rule blocks the validation request. When certificates lasted a year, a broken job had months to get noticed. Soon it will have days.

That's what I built CertiMonitor for. It connects to your hosts the way a browser does, reads the certificate actually being served, and tells you before it runs out. You can try it on any domain here:

Sources