Your site was working fine yesterday. Today, visitors see a scary browser warning: "Your connection is not private." Nothing changed on your end except the calendar — this is what an expired SSL certificate looks like, and it's one of the most common causes of sudden, unexplained downtime.
Check right now — takes 10 seconds
Use our free SSL Certificate Checker to see exactly when a site's certificate expires, who issued it, and how many days are left. No signup, no waiting.
Why certificates expire in the first place
SSL/TLS certificates aren't permanent by design — they're issued for a fixed period, usually 90 days (Let's Encrypt, the most common free option) or up to a year (paid certificate authorities). This limited lifespan is intentional; it forces regular re-verification and limits the damage if a certificate's private key is ever compromised.
What actually happens when one expires
Browsers don't just show a small warning icon — modern browsers block the page entirely behind a full-screen interstitial, and most visitors have no idea how to get past it (nor should they be encouraged to). Your site becomes functionally down, even though the server itself is running perfectly fine.
An expired certificate isn't a minor cosmetic issue. To every visitor's browser, it looks identical to a site being hacked.
The auto-renewal trap
Most people set up Let's Encrypt's auto-renewal (via Certbot) once and assume it's handled forever. It usually is — until a renewal silently fails: a firewall rule changes, a DNS record gets modified, disk space runs out, or a cron job quietly stops running after a server migration. Auto-renewal reduces the risk; it doesn't eliminate it.
How to actually stay ahead of it
- Don't rely on remembering — set a real reminder, or better, automated monitoring.
- Check a few days before, not the day of — gives you time to fix a failed renewal before visitors see anything.
- Verify auto-renewal actually ran — don't just assume the cron job fired; check the certificate's actual expiry date periodically.
This is exactly the kind of silent failure PingKeeper is built to catch — it checks your site every 60-300 seconds and alerts you the instant something breaks, including the moment a certificate issue starts causing connection failures. Free for up to three sites.
Stop finding out about outages from customers.
Free forever for up to 3 monitors — set one up in under a minute.
Start monitoring free