Your SSL certificate expired — what now?
2 min read
What visitors see when a certificate expires, how to check remaining days, the emergency fix, and how automation plus monitoring prevents it from ever happening again.
What happens at expiry
Certificates are deliberately short-lived (currently up to ~13 months, heading to 47 days by 2029). The moment one expires, browsers show a full-page warning, API clients drop the connection with certificate has expired, and integrations start failing quietly. To visitors it reads as "this site is unmaintained".
An intermediate in the chain can expire too — the classic case where your own certificate looks fresh yet the site is rejected. SSLx lists every link with its dates, so you can see exactly which one lapsed.
Diagnosis and the emergency fix
An SSLx query shows a countdown badge — days left, or days since expiry. The immediate fix is to renew/reissue and install; with Let's Encrypt, certbot renew plus a service reload usually suffices.
The permanent fix: automation plus monitoring
A manually renewed certificate is a certificate waiting to be forgotten. The robust setup has two layers: automated renewal (a scheduled certbot/acme.sh job) and independent monitoring that checks the expiry date from outside, so you hear about it when automation breaks. Add SSLx to your periodic checklist; certificates under 30 days show amber, expired ones red.
Test your own site
SSLx performs every diagnosis in this guide in ten seconds: chain verification, hostname matching, expiry and HSTS — free, no signup.
Test with SSLxFrequently asked questions
Does an expired certificate hurt SEO?
It stops visitors at a warning page; the resulting bounce and unreachable content hurt rankings indirectly, and Google uses HTTPS as a ranking signal.
Why do certificate lifetimes keep getting shorter?
To shrink the damage window of stolen or mis-issued certificates and to force automation. Short lifetimes make auto-renewal the norm.