Website Monitoring Dashboard for Publishers and Multi-Site Owners

TLS Certificates Are Getting Shorter Lives: What Site Owners Need to Change

Security

October 30, 2026

An expired certificate is one of the most avoidable outages on the web. Visitors hit a full-page browser warning, and a lot of them leave. That risk went up this year for anyone who still renews certificates by hand, because the maximum lifetime of public TLS certificates is being cut in stages, and the first cut is already in effect.

What changed

The CA/Browser Forum is the industry body of certificate authorities and browser makers that sets the baseline rules for publicly trusted TLS certificates. In 2025 it approved a ballot, SC-081, that brings the maximum certificate validity period down step by step:

  • From March 15, 2026 (already in effect): 200 days.
  • From March 15, 2027: 100 days.
  • From March 15, 2029: 47 days.

The same ballot also shortens how long a certificate authority can reuse earlier domain validation.

Before this change, the maximum was 398 days, which is why a lot of teams renewed once a year.

Why browsers want shorter certificates

Shorter lifetimes limit how long a compromised or mis-issued certificate stays useful to anyone. They also push the industry toward automation, which cuts down on human error.

What this means in practice

A certificate that lasts 47 days has to be renewed about every month and a half, and in practice even sooner, since tools renew ahead of expiry. Renewing by hand at that pace invites mistakes. If your process today is a calendar reminder and a support ticket, it's time to automate.

How to automate

The usual approach is the ACME protocol, standardized by the IETF as RFC 8555. Let's Encrypt made it popular, and many certificate authorities support it now. ACME clients request, validate, and install certificates on their own.

Practical steps:

  1. Inventory every certificate. Include load balancers, CDNs, mail servers, and internal tools that serve public names.
  2. Use managed certificates where you can. Many hosting platforms and CDNs issue and renew certificates automatically.
  3. Install an ACME client on any servers you manage directly.
  4. Test renewals in staging, not just issuance.

What Let's Encrypt is changing

Let's Encrypt, the free certificate authority behind a large share of the web's certificates, already issues 90 day certificates, well under the new 200 day ceiling. It has published its own schedule for going further, announced in December 2025:

  • May 13, 2026: an opt in profile called tlsserver began issuing 45 day certificates for early adopters and testing.
  • February 10, 2027: the default profile moves to 64 day certificates, with a 10 day authorization reuse period.
  • February 16, 2028: the default profile moves to 45 day certificates, with authorization reuse cut to 7 hours.

Each change applies at the next renewal after the date, so nothing breaks on the day itself. What breaks is automation built on hidden assumptions. Let's Encrypt warns that renewing on a fixed 60 day schedule will no longer work with 45 day certificates. It recommends renewing about two thirds of the way through a certificate's life.

Renewal timing: use ARI where you can

ACME Renewal Information, usually shortened to ARI, lets the certificate authority tell your ACME client when to renew. Instead of a hard coded interval, the client asks for a suggested renewal window and follows it. This helps in two situations: when lifetimes change, and when a CA needs many certificates replaced early, for instance after a mis issuance. Let's Encrypt recommends ARI, and support is spreading across popular clients. Check your client's documentation for how to turn it on.

The reminder emails are gone

Many small teams relied on Let's Encrypt's expiration reminder emails as a safety net. Let's Encrypt ended that service on June 4, 2025, and deleted the email addresses tied to ACME accounts. It cited privacy, cost and the fact that most subscribers now automate renewals. Its own advice is to use a separate monitoring service. If your only warning was an email that no longer comes, you currently have no warning.

Why the authorization reuse change matters

The reuse change gets less attention than the lifetime change, but it can catch teams out. Domain validation proves you control a name. Today a validation can be reused for a while, so a renewal may not need a fresh DNS or HTTP challenge. As reuse periods shrink, almost every renewal will need a successful challenge. Anything that blocks validation, such as a changed DNS provider, an expired API token for DNS updates, a redirect rule or a firewall change, will surface quickly instead of months later.

Private and internal certificates

These rules apply to publicly trusted certificates, the ones browsers accept without extra setup. Certificates issued by your own private certificate authority for internal services aren't bound by the CA/Browser Forum schedule. Still, many organizations use the change as a reason to automate those too, since the same tools and monitoring work for both.

Monitor even if you automate

Automation fails quietly. A DNS change can break validation. A firewall rule can block the challenge. A renewed certificate can get issued and then never loaded by the server.

That's why it helps to monitor what visitors actually see: the certificate served on each hostname, its expiry date, and whether the chain is valid. A good alert goes off with enough lead time to fix a broken renewal, for instance when fewer than 14 days remain, instead of on the day it expires.

A simple renewal drill

Once a quarter, pick one hostname and force a renewal in a controlled window. Confirm the new certificate was issued, that the server or CDN actually loaded it, and that your monitoring saw the new expiry date. The drill takes minutes and catches the quiet failures, like a renewed certificate sitting on disk while the web server keeps serving the old one.

A checklist for your dashboard

  • Expiry date for each public hostname.
  • Issuer and chain validity.
  • Hostname match, including www and apex domains.
  • An alert threshold that leaves time to act.

A certificate failure shows up as a failed check, the same way a tile going offline starts: confirm the URL, then look at the host. The certificate date is the part you can see before that check fails.

Sources

Back to Blog