How far ahead should you alert on SSL certificate expiry?
Choosing lead times for certificate expiry alerts: why 30 days is too late for some setups and 14 is enough for others, and how to avoid alert fatigue with auto-renewal.
· 6 min read · By the Spot Downtime team
An expired certificate takes a site down as completely as a crashed server, and with a worse message: a full-page browser warning that most visitors will not click through. Almost every team that has had one says the same thing afterwards: we had a reminder, it just came too late or went to the wrong person.
So the question is not whether to alert on expiry, but how many days ahead, how many times, and who gets it. The answer depends on how your certificates are issued.
Start from your renewal process
An expiry alert is a safety net under your renewal process. Size it to that process.
- Fully automated (Let's Encrypt, a managed platform certificate). Certificates last 90 days and clients normally renew about 30 days before expiry. The alert should fire only if renewal has clearly failed. If it fires every cycle, it is noise. A threshold of 14 days or less leaves the automation its full retry window first, and still leaves two weeks to fix things. See why Let's Encrypt renewals fail for the usual causes.
- Semi-automated. Someone approves a request, or a script runs when a person triggers it. Alert earlier, around 30 days, since a human step can wait on holidays, approvals or a lost ticket.
- Fully manual (purchased certificates, devices, vendors). Use 45 days or more for the first warning. Buying, validating and installing a certificate can take days, and organization validation can take longer.
Rule of thumb
Use more than one alert
A single reminder is easy to miss and easy to snooze. A short ladder works better, with each step more urgent than the last:
- Early (14 to 30 days). Goes to a channel or ticket queue. Plenty of time, nothing is on fire.
- Middle (7 days). Something should already have happened. If this fires, renewal is stuck. Notify the owner directly.
- Final (1 to 2 days). Treat as an incident. Page the on-call person, because the next step is an outage. See alert escalation policies for routing it.
This is also how Spot Downtime works. Every HTTPS website and API monitor reads the certificate expiry on each check and warns at 14, 7 and 1 day before it lapses, once each per certificate. Nothing fires earlier than 14 days, so automatic renewals stay quiet, and a renewed certificate resets the warnings. Details are on the SSL monitoring page.
Alert on what visitors actually receive
A certificate in your issuing system proves little. What matters is the certificate the server presents, from the outside. Several things make those differ:
- Renewal succeeded but the web server was never reloaded, so it keeps serving the old certificate from memory.
- Several servers behind a load balancer, with one that missed the update.
- A CDN or proxy terminating TLS with a different certificate than the origin.
- A missing intermediate that works in your browser but fails elsewhere.
You can check what a host presents from the command line:
echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null \
| openssl x509 -noout -enddate -subject
# notAfter=Jan 30 12:00:00 2027 GMTTo see how many days remain, compare that date with today. An external monitor that does this on a schedule, for every hostname, is the version that does not depend on someone remembering.
Do not forget the less obvious certificates
- Every hostname.
api.,staging.,mail.and old marketing subdomains expire on their own schedules. Wildcard certificates cover names but not different servers that must each be updated. - Non-HTTPS services. SMTP, IMAP, LDAP and database endpoints can use TLS too. A TCP port check will show they are reachable, but not that the certificate is valid. Check what you can from outside and keep a calendar entry for the rest.
- Client and internal certificates. Mutual TLS, internal CAs and device certificates are usually not visible to a public monitor. Track them separately.
- The domain itself. A perfectly renewed certificate is useless if the domain registration lapses. Alert on both expiries.
Make sure the alert reaches someone
- Send expiry alerts to a shared channel or group address, not one person's inbox. People change roles and go on leave.
- Include the hostname, the expiry date and a link to the renewal runbook in the alert itself.
- Test the path once. Send a test alert and confirm it arrives on every channel the final warning is supposed to use.
- Write down who owns each certificate. An expiring certificate nobody owns is the classic cause of an avoidable outage.
When it has already expired
If the alert came too late, the fix is to issue and install a new certificate, reload the server and verify from outside. The browser messages and their fixes are in SSL certificate expired and ERR_CERT_DATE_INVALID.
SSL checkerSee the certificate a host presents, its expiry date and whether the chain is complete.Get new guides by email
Practical posts on monitoring, outages, error fixes and on-call, when they're published. No spam.
Keep reading
- SSL · MonitoringCertificate Transparency monitoring: find certificates issued for your domainCertificate Transparency logs are public. Learn how to search them for your domains, spot unexpected certificates, and lock down issuance with CAA records.November 10, 2026 · 6 min read
- SSL · TroubleshootingCertificate pinning and rotation: how to renew without breaking your appsPinned certificates turn a routine renewal into an outage for mobile apps and API clients. How to pin the public key, plan backup pins and rotate safely.November 9, 2026 · 7 min read