Why certificates still expire in production
An expired certificate is one of the few outages you can see coming months ahead. The expiry date is written inside the certificate. Yet expired certificates still take down websites, APIs, mail servers and VPNs, because the date is known but the work to act on it is not done in time.
The pressure is growing. Public TLS certificates now last at most 200 days, and that falls to 100 days in March 2027 and 47 days in March 2029, as we explain in certificate lifetimes are falling to 200, 100 and 47 days. More renewals mean more chances to miss one.
The five ways it goes wrong
Nobody knew the certificate existed
A contractor set up a service years ago, or a vendor installed an appliance with its own certificate. It never made it onto any list, so nobody was watching it. This is the most common cause, and the only fix is to find certificates rather than wait to be told about them.
The owner left
The certificate is on a list, but the name next to it belongs to someone who changed teams or left. Reminders go to an inbox nobody reads. A certificate needs an owner that is a team or a role, not one person.
The reminder went away
Some teams relied on their CA’s reminder emails. Let’s Encrypt, for example, stopped sending expiry emails on 4 June 2025 and recommends separate monitoring instead. If your only warning came from someone else’s system, you have no warning.
Renewal worked, but the new certificate never arrived
The renewal succeeded, but the service still presents the old certificate. Maybe the web server was never reloaded, the file was written to the wrong path, or one node in a cluster was missed. Seen from outside, this looks exactly like no renewal at all.
The chain changed
The server certificate is fine, but an intermediate or root it depends on changed. When the DST Root CA X3 root expired in September 2021, Let’s Encrypt wrote that most sites were unaffected, but some older clients and configurations failed until their software was updated. Chain problems often hit only some clients, which makes them slow to diagnose.
A checklist that prevents most outages
- Keep one inventory. Every certificate you depend on, public and internal, with where it is installed, which CA issued it and when it expires. Build it from discovery, not memory.
- Give every certificate a team owner. Use a team name or a shared queue, so ownership survives people moving on.
- Automate renewal. Use ACME where your CA supports it. Renew at about two thirds of the lifetime, so a failure leaves a third of the lifetime to fix it.
- Automate the install and reload. A renewal is not done until the service has loaded the new certificate.
- Monitor what is served, not what is on disk. Connect to each endpoint the way a client does, with the right hostname, and read the certificate it presents. Alert on that.
- Alert early and in more than one place. Alert when a served certificate passes two thirds of its lifetime, then again closer to expiry. Send alerts to a team channel and a ticket queue, not one inbox.
- Check the full chain. Make sure each endpoint sends the right intermediates, and test with the oldest clients you still support.
- Write a short runbook. Who can issue a certificate in an emergency, from which CA, and how to install it on each kind of system.
When it happens anyway
If a certificate has expired, the quickest safe fix is usually to issue a new one from the same CA for the same names and install it. Then look for the cause, using the five patterns above. Ask whether the certificate was on your inventory, whether anyone got an alert and whether the renewal ran. Fix that cause, not only the certificate, and check whether other certificates share it.
Where clm.mt fits
We build clm.mt, a certificate lifecycle service, so read this with that in mind. It keeps an inventory with owners and expiry views, renews through ACME and other CAs, deploys the new certificate and then checks what each endpoint serves. Alerts go to email, Slack, Microsoft Teams, Jira or a webhook. Network and Certificate Transparency discovery is in preview.
The integrations page lists which deployment targets are supported after tests on real software and which are in preview. The docs explain setup and pricing lists the plans. The checklist above works with any tool, including scripts you already have.
Sources
- Let’s Encrypt, Ending Support for Expiration Notification Emails, 22 January 2025.
- Let’s Encrypt, Resources for Certificate Chaining Help, 1 October 2021.
- CA/Browser Forum, Ballot SC-081v3, April 2025.