SSL Certificate Risk Calculator
Calculate your expiry risk score and get an actionable remediation plan. Results update instantly as you adjust inputs.
Certificate Details
Configuration
Risk Factors
Recommended Actions
Why Certificate Expiry Is a Risk You Can Quantify
Every SSL/TLS certificate has a hard deadline baked into it, and the moment it passes, browsers stop trusting your site — no grace period, no warning banner for visitors, just a full-page security error. Expiry outages are unusual among production incidents in that they are 100% predictable: the date is known months in advance. They still happen constantly, because the renewal depends on a chain of small things going right — a payment method on file at the CA, a DNS record that still resolves, a cron job that survived the last server migration, a person who still works at the company reading the reminder email.
This calculator turns those failure modes into a single 0–100 score. It is deliberately weighted so that time remaining dominates: a perfectly automated setup with 3 days left is still an emergency, while a manual process with 300 days of runway is merely a task. The remaining points capture how wide the blast radius would be (wildcard and multi-domain certificates take many services down at once) and whether anything would warn you before the deadline.
The stakes keep rising as maximum certificate lifetimes shrink. Public certificates were capped at 398 days in 2020, and the CA/Browser Forum has approved a phased reduction to roughly 47-day certificates by 2029. In that world a renewal happens for every domain every few weeks — which is exactly why the two configuration checkboxes in this calculator (auto-renewal and monitoring) are worth 30 risk points between them.
How to Read Your Score
The Ways Certificates Actually Expire in Production
Certbot timers stop firing after OS upgrades, and ACME DNS-01 challenges break when nameservers change. Verify with `systemctl list-timers certbot*` and do a dry run: `certbot renew --dry-run`.
A renewed file on disk does nothing until the web server reloads it. Add a deploy hook — for certbot: `--deploy-hook "systemctl reload nginx"` — and verify what is actually served: `openssl s_client -connect example.com:443 | openssl x509 -noout -enddate`.
The main site renews fine while api.example.com, the mail server, or an internal admin panel quietly lapses. Inventory every TLS endpoint (Certificate Transparency logs help you find forgotten ones) and monitor each hostname separately.
CA reminder emails routinely go to a former employee’s inbox or an unmonitored alias. Point CA accounts and monitoring alerts at a shared address like ssl-alerts@yourcompany.com, never at an individual.
Paid certificates fail to auto-renew when the stored card lapses. Check billing details during quarterly reviews, or remove the failure mode entirely by switching eligible hosts to free ACME certificates.
Frequently Asked Questions
Stop Calculating — Start Monitoring
CertNotify checks your certificates every day and sends alerts 30, 14, and 7 days before expiry, so the risk score never gets a chance to climb.