Skip to content
AdminKit

How do you avoid an expired TLS certificate outage?

To avoid an expired TLS certificate outage, automate renewal with an ACME client, renew at about two thirds of the certificate's lifetime, reload every service that uses it, and check the certificate each host really serves. Lifetimes are shrinking toward 47 days. AdminKit's free SSL/TLS check shows the days left on any host.

By AdminKit team, Netbase JSC · Updated

Key takeaways

  • Most certificate outages are not caused by a missing renewal tool. They come from renewal that fails without anyone noticing, a new certificate that was never loaded, or a certificate on a system nobody listed.
  • Lifetimes are getting shorter. The CA/Browser Forum Baseline Requirements cap new certificates at 200 days from 15 March 2026, 100 days from 15 March 2027 and 47 days from 15 March 2029.
  • Automate with ACME, renew at about two thirds of the lifetime, and reload every service after renewal.
  • Check the certificate each host really serves, from outside, on a schedule that does not depend on the renewal client.
  • AdminKit’s free SSL/TLS check shows the expiry date and days left for any public hostname, with no account.

Why do TLS certificates still expire in production?

Free, automated certificates have been the norm for years, but expired certificates still take sites offline. The usual causes are:

  • Renewal failed and nobody saw it. The ACME client runs on a schedule, but domain validation fails because DNS moved, port 80 was closed or an API token for DNS changes expired. The client logs an error on a server nobody reads.
  • Renewal worked but the service was not reloaded. The new certificate file is on disk, while the web server, proxy or mail server keeps serving the old one from memory.
  • The certificate lives somewhere else. A load balancer, CDN, mail server, VPN gateway or appliance holds its own copy, uploaded by hand once and never automated.
  • The reminder email stopped. Let’s Encrypt ended its expiration notification emails on 4 June 2025, and recommends a third-party monitoring service for anyone who still wants warnings.

Each of these has a fix. None of them is fixed by buying a longer certificate, because longer certificates are going away.

How short are certificate lifetimes getting?

The maximum validity of a publicly trusted TLS certificate is set by the CA/Browser Forum. Ballot SC-081v3, voted on by CA/Browser Forum members in April 2025, added a schedule to §6.3.2 of the Baseline Requirements:

Certificate issuedMaximum validity
Before 15 March 2026398 days
15 March 2026 to 14 March 2027200 days
15 March 2027 to 14 March 2029100 days
From 15 March 202947 days

Every publicly trusted CA follows these limits. Let’s Encrypt already issues 90-day certificates and has published its own schedule in Decreasing Certificate Lifetimes to 45 Days:

DateLet’s Encrypt change
13 May 2026Opt-in tlsserver ACME profile issues 45-day certificates
10 February 2027Default classic profile moves to 64-day certificates
16 February 2028Default classic profile moves to 45-day certificates

Validation is getting shorter too. The same ballot cuts how long a CA may reuse a completed domain validation to 10 days by 2029, and Let’s Encrypt plans to cut its own authorization reuse period from 30 days to 7 hours by 2028. In practice your domain validation, whether an HTTP-01 file on port 80 or a DNS-01 TXT record, has to succeed at almost every renewal, not just at first issuance. Anything that blocks validation, such as a firewall change, a CDN rule in front of port 80, a moved DNS zone or an expired DNS API credential, breaks the next renewal.

At 45 or 47 days, a certificate renewed by hand once a quarter will expire before the next manual renewal. Let’s Encrypt’s announcement says manual renewal “is not recommended”.

How do you automate renewal properly?

Use an ACME client. ACME (RFC 8555) is the protocol a client uses to prove control of a domain and get a certificate without a human in the loop. Most CAs that issue domain-validated certificates support it, and many web servers, proxies and hosting panels include a client.

Then get three details right:

  1. Renew on time, not on a fixed date. Let’s Encrypt’s integration guide recommends checking ACME Renewal Information (ARI, RFC 9773) at least twice a day and renewing when it says to. As a backstop, renew when a third of the lifetime is left: 30 days before expiry for a 90-day certificate. The 45-day announcement warns that a hard-coded 60-day renewal interval “will no longer be sufficient”.

  2. Test renewal before you need it. The Certbot user guide describes a dry run, which by default uses the Let’s Encrypt staging server and proves validation still works without issuing a real certificate:

    certbot renew --dry-run
  3. Reload what uses the certificate. Certbot runs a --deploy-hook command only after a successful renewal. That is where a reload of the web server or mail server belongs:

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

    The service name is an example. Use the reload command for whatever terminates TLS on that host. Other ACME clients have an equivalent hook.

Certbot’s guide also notes that most installations set up a scheduled task that runs certbot renew on their own, and that renew only acts on certificates near expiry, so it is safe to run often. Check that the task exists on each server rather than assuming it does.

How do you know renewal actually worked?

Automation removes the routine work. Monitoring tells you when the automation breaks. Let’s Encrypt’s 45-day announcement recommends monitoring that alerts “if certificates aren’t renewed when expected”.

Good monitoring has three properties:

  • It checks from the outside. It connects to the hostname the way a visitor would and reads the certificate that is really served, not the file on disk. That catches the “renewed but not reloaded” case.
  • It is independent of the renewal client. If the scheduler that runs renewal stops, the monitor should still run.
  • Its thresholds match the lifetime. With renewal at one third of the lifetime left, a certificate that drops below that has missed its renewal window.
Certificate lifetimeNormal renewal point (one third left)Alert if days left fall below
90 days30 days leftabout 20 days, so there is time to fix validation
64 daysabout 21 days leftabout 14 days
45 to 47 daysabout 15 days leftabout 10 days

The alert values are a suggested margin, not a standard. Choose ones that leave your team enough time to fix a broken validation by hand.

AdminKit’s SSL/TLS check is useful here as an on-demand check: it completes a real TLS handshake on port 443, shows the certificate subject, issuer and covered hostnames, and counts down the days to expiry. It raises a medium finding at 15 to 30 days left, a high finding at 14 days or fewer and a critical finding once expired. It is not a scheduled monitor. Run it after every renewal, migration or proxy change to confirm what visitors now see. How to read a TLS/SSL certificate check result explains every field.

Where do forgotten certificates hide?

An outage is often on the one host not covered by automation. Build an inventory that includes:

  • Every public hostname, including www and apex names, API hosts, status pages and old marketing domains that still redirect.
  • Load balancers, CDNs and reverse proxies that terminate TLS with their own uploaded copy.
  • Mail servers. SMTP with STARTTLS, IMAP and submission ports use certificates too. Does your mail server enforce STARTTLS? explains how mail servers use TLS between each other.
  • VPN gateways, firewalls and appliances with a web admin interface or client portal.
  • Internal services that call each other over TLS, even when the CA is private.

Certificate Transparency logs help find public certificates you did not know about, because CAs log the certificates they issue so that major browsers will accept them. Certificate Transparency logs explained shows how to search them for your domain.

What happens when a certificate expires anyway?

Browsers show a full-page warning, and API clients refuse the connection. For sites that send HSTS, it is worse: Let’s Encrypt’s integration guide notes that browsers do not allow a click-through on an expired-certificate warning for hostnames with an active HSTS header. HSTS and HSTS preload explained covers why.

If it happens:

  1. Renew or reissue the certificate with your ACME client, or from your CA if it is not automated.
  2. Reload or restart every service that serves it, and upload it to any load balancer or CDN that keeps its own copy.
  3. Confirm from outside with the SSL/TLS check that the new expiry date is served, and check the chain with checking TLS certificate chain completeness.
  4. Find out why automation missed it, and add that host to your inventory and monitoring.

Checklist: avoid the next certificate outage

StepDone when
InventoryEvery hostname and device that terminates TLS is listed with its renewal method
AutomationEach certificate renews through ACME, with ARI or renewal at one third of lifetime left
Dry runA renewal dry run passes on every server after DNS, firewall or hosting changes
ReloadA deploy hook or equivalent reloads each service after renewal
MonitoringAn external check alerts before the renewal window is missed
VerificationThe served certificate is checked after every renewal or infrastructure change

Check a hostname’s certificate now: it is free, needs no account, and shows the expiry date, days left and the hostnames the certificate covers. For the certificate format itself, see the X.509 certificate glossary entry. This guide is part of AdminKit’s security basics cluster.

This guide is general information, not a security audit of your specific network — see our disclaimer for what AdminKit's guidance does and does not commit to.

Frequently asked questions

How long is a TLS certificate valid today?

Under the CA/Browser Forum Baseline Requirements, a publicly trusted TLS certificate issued on or after 15 March 2026 may be valid for at most 200 days. The limit drops to 100 days on 15 March 2027 and to 47 days on 15 March 2029. Let's Encrypt issues 90-day certificates by default today and plans to move its default to 64 days in February 2027 and 45 days in February 2028.

When should a certificate be renewed?

Let's Encrypt recommends asking its ACME Renewal Information (ARI) endpoint when to renew, and as a backstop renewing when a third of the certificate's lifetime is left. For a 90-day certificate that is 30 days before expiry. A fixed schedule, such as every 60 days, will not work once certificates last 45 days.

Will my certificate authority email me before the certificate expires?

Do not rely on it. Let's Encrypt stopped sending expiration notification emails on 4 June 2025 and recommends using a separate monitoring service instead. Other CAs have their own policies. Monitoring that checks the certificate your server really serves catches more problems than a reminder email, including a renewal that worked but was never loaded.

My certificate renewed, so why does the site still show the old one?

The server process that terminates TLS is still using the certificate it loaded at start-up. Web servers, proxies and mail servers usually need a reload after a new certificate file is written. Certbot's --deploy-hook option runs a command after each successful renewal, which is the usual place to reload the service.

Can visitors click through an expired certificate warning?

Often they cannot. Let's Encrypt's integration guide notes that browsers do not allow a click-through on a name-mismatch or expired-certificate warning for hostnames with an active HSTS header. For those sites an expired certificate means the site is unreachable in a browser until it is replaced.

Does AdminKit monitor my certificates for me?

No. AdminKit's SSL/TLS check is an on-demand check: it completes a real TLS handshake on port 443 when you submit a hostname and shows the expiry date and days left, with a warning at 30 days and a high finding at 14. Use it to verify a renewal or spot-check a host, and keep a scheduled monitor for continuous coverage.

Want AdminKit to watch this for you?

Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.

Huy Nguyen (David), Founder and CEO of Netbase JSC

Talk to an expert

Huy Nguyen (David), Founder & CEO, Netbase JSC

Ask whether this fix applies to your setup, or get a second pair of eyes on your DNS and mail records.