Website Monitoring
What Happens When an SSL Certificate Expires (and How to Never Miss One)
7 min read · Updated 2026-11-10
Every HTTPS site serves a certificate that proves the site is who it claims to be. Every certificate has an end date. When that date passes, browsers stop trusting the site, and most visitors leave.
Certificates are also getting shorter. Public certificates could last up to 398 days until March 2026. They're now capped at 200 days, and the limit falls to 100 days in 2027 and 47 days in 2029. Renewals that once happened once a year now happen every few months, so there are more chances for one to go wrong.
What visitors see
An expired certificate doesn't take the site offline. The server still answers. But the browser shows a full-page warning before it loads anything:
- Chrome and Edge: "Your connection is not private", with the code
NET::ERR_CERT_DATE_INVALID - Firefox: "Warning: Potential Security Risk Ahead", with the code
SEC_ERROR_EXPIRED_CERTIFICATE - Safari: "This Connection Is Not Private"
Visitors can sometimes click through, but most won't, and sites that use HSTS don't offer the option at all. Apps and scripts that call an API over HTTPS simply fail with a certificate error. Mail servers that check certificates may stop delivering to you.
The certificate isn't less secure after it expires. The encryption would still work. The browser refuses it because it can no longer confirm the certificate is still valid.
Why certificates still expire with auto-renewal
Most certificates now renew automatically, through Let's Encrypt, a hosting provider or a CDN. Expiries still happen, usually for one of these reasons:
- The renewal can't prove control of the domain. The certificate authority checks with a file on the website or a record in DNS. A DNS change, a firewall rule, a redirect or a moved site can break that check.
- A CAA record blocks the authority. If your DNS has a CAA record that doesn't list the authority you're renewing with, it must refuse. See CAA Records.
- The new certificate isn't in use. The renewal succeeded, but the web server, load balancer or CDN still serves the old one because it was never reloaded or the new file was put in the wrong place.
- One server was missed. A site behind several servers, or a subdomain on separate hosting, has its own certificate with its own date.
- Billing lapsed. A paid certificate or the hosting plan that manages it wasn't renewed.
- Nobody saw the warning. Reminder emails go to someone who left, or to an address on the domain that's having the problem. Let's Encrypt stopped sending expiry reminder emails in 2025, so sites that relied on them now get no warning at all.
How to check when a certificate expires
In a browser, click the icon next to the address and open the certificate details. The "Valid to" or "Expires" date is the one that matters.
A certificate lookup on who.is shows the expiry date, who issued it, the names it covers and whether browsers trust the chain, without opening the site.
From a terminal:
echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null | openssl x509 -noout -enddate
Check each hostname you serve separately, such as example.com, www.example.com and api.example.com. They may have different certificates.
Getting warned in time
A good warning setup checks the certificate your site actually serves, not just the one your provider says it issued. That's the only way to catch a renewal that worked but was never put in use.
Warnings should start early enough to fix a broken renewal without a rush, and repeat as the date gets closer. With certificates that last 100 days or less, a single reminder a month out isn't enough.
who.is Website Monitoring reads the certificate your site serves and emails you 30, 14, 7 and 1 days before it expires. It also alerts you if the certificate is replaced unexpectedly or a different authority issues it, which can be a sign that someone else got a certificate for your domain. It's free for one domain.
If your certificate has already expired
- Find out whether a renewed certificate exists. If it does, the fix is usually to install it or reload the server.
- If not, renew by hand. With Let's Encrypt, run your ACME client's renew command and read the error it gives. It usually names the check that failed.
- Clear the cause, whether that's a DNS record, a firewall rule or a CAA record, so the next automatic renewal works.
- Check from outside with a certificate lookup once it's fixed. Browsers may hold on to the old result until they're restarted.
Key takeaways
- An expired certificate keeps the site running but makes browsers show a full-page warning, and API clients fail outright.
- Public certificates are capped at 200 days since March 2026, falling to 100 days in 2027 and 47 days in 2029.
- Automatic renewal still fails when the domain check breaks, a CAA record blocks the authority, or the new certificate is never put in use.
- Monitor the certificate your site actually serves, for every hostname, with warnings that start weeks ahead.
Get warned before your certificate expires
Free certificate monitoring with alerts 30, 14, 7 and 1 days before expiry, plus uptime and DNS checks.
Frequently asked questions
What happens when an SSL certificate expires?▾
Browsers show a security warning instead of your site, apps and scripts that use HTTPS fail, and some mail servers stop delivering. The site itself keeps running.
How long do SSL certificates last?▾
Since 15 March 2026, publicly trusted certificates can last at most 200 days. The limit falls to 100 days in March 2027 and 47 days in March 2029. Let's Encrypt certificates last 90 days by default, falling to 64 days in February 2027 and 45 days in February 2028.
How do I check when my SSL certificate expires?▾
Open the certificate details from the browser's address bar, or run a certificate lookup, which shows the expiry date, issuer and chain status.
Can I get an alert before my certificate expires?▾
Yes. who.is Website Monitoring emails you 30, 14, 7 and 1 days before expiry, free for one domain.