SSL certificates are shrinking to 47 days
In April 2025 the CA/Browser Forum, where certificate authorities and browser makers set the rules, passed ballot SC-081. It cuts the maximum lifetime of publicly trusted TLS certificates in steps.
| Issued from | Maximum lifetime | Domain validation reuse |
|---|---|---|
| before 15 March 2026 | 398 days | 398 days |
| 15 March 2026 | 200 days | 200 days |
| 15 March 2027 | 100 days | 100 days |
| 15 March 2029 | 47 days | 10 days |
What it means in practice
- Manual renewals stop being realistic. At 47 days you renew roughly 8 times a year per certificate.
- Automation fails quietly. A certbot timer that stopped, a DNS API token that expired, or a load balancer that never reloaded the new file keeps serving the old certificate until browsers refuse it.
- Nobody e-mails you any more. Let's Encrypt ended its expiry reminder e-mails in 2025, so you need your own check.
- Check what is served, not what is on disk. The renewed file on the server doesn't help if nginx, a CDN or a mail server still presents the old one.
A simple safety net
CertNudge connects to your hosts every 6 hours like a browser would and e-mails you when a certificate gets close to expiry, stops being trusted, or the domain registration itself is about to lapse. Free for 3 hosts.
No password: we e-mail you a sign-in link.
Source: CA/Browser Forum Baseline Requirements, ballot SC-081.