47-day SSL certificates: what changes and how to prepare
Public SSL/TLS certificate lifetimes are shrinking from 398 days to 47 days by March 2029. Check when your certificate expires, then see the timeline and how to automate renewals.
Try: google.com · github.com · cloudflare.com
The SC-081 timeline at a glance
In April 2025 the CA/Browser Forum passed Ballot SC-081v3, with the browser makers Apple, Google, Microsoft and Mozilla voting yes. It replaces the old 398-day maximum with a step-down schedule for publicly trusted TLS certificates and for how long domain validation can be reused:
| Certificate issued | Maximum validity | Domain validation reuse |
|---|---|---|
| Before March 15, 2026 | 398 days | 398 days |
| March 15, 2026 – March 14, 2027 | 200 days | 200 days |
| March 15, 2027 – March 14, 2029 | 100 days | 100 days |
| From March 15, 2029 | 47 days | 10 days |
The 200-day step is already in force. Each limit is judged by the issuance date, so certificates issued before a cutoff keep their original expiry.
What 47-day certificates mean for site owners
- Many more renewals. One renewal a year becomes about two at 200 days, about four at 100 days and roughly eight at 47 days per certificate.
- Domain validation on almost every renewal. With 10-day reuse, proof of domain control must be repeated nearly every time, so email-based or hand-edited DNS validation will not keep up.
- Expired certificates become the main risk. A renewal job that silently fails now has weeks, not months, before visitors see “Your connection is not private”.
- Every endpoint counts. Load balancers, CDNs, mail servers, APIs and appliances that use public certificates all follow the same limits.
Automate with ACME
ACME is the open protocol (RFC 8555) used by Let's Encrypt and most commercial CAs to issue and renew certificates automatically. Common clients include certbot, acme.sh, simple-acme (formerly win-acme) for Windows/IIS and web servers with built-in ACME such as Caddy; many hosting panels, CDNs and cloud load balancers renew for you.
- Inventory every public certificate and where it is installed. Our bulk SSL checker lists expiry dates for up to 20 domains at once.
- Pick a challenge type. HTTP-01 works when the server is reachable on port 80; DNS-01 needs API access to your DNS but also covers wildcards and internal hosts.
- Renew early. Schedule renewal at about two-thirds of the lifetime (around day 67 of a 100-day certificate) so there is time to retry.
- Automate deployment with reload hooks so the new certificate is actually served, not just downloaded.
- Monitor what is live. Check the certificate each endpoint really presents and alert well before expiry.
Free SSLWatchLive account: monitor 1 site with email expiry alerts. No credit card. Paid plans from $5/month.
Check a certificate now with the SSL expiration checker or the SSL chain checker.
Frequently asked questions
When do SSL certificates become valid for only 47 days?
Publicly trusted TLS (SSL) certificates issued on or after March 15, 2029 can be valid for at most 47 days. The limit drops in steps: 200 days from March 15, 2026 and 100 days from March 15, 2027.
What is the maximum SSL certificate validity right now?
Certificates issued from March 15, 2026 to March 14, 2027 can be valid for at most 200 days. Certificates issued from March 15, 2027 are limited to 100 days.
Will my current certificate stop working on the cutoff date?
No. Each limit applies to the date a certificate is issued. A certificate already issued stays valid until its own expiry date; only its replacement gets the shorter lifetime.
What does the 10-day domain validation reuse mean?
A certificate authority may reuse an earlier proof that you control a domain for a limited time. That reuse period shrinks with the validity schedule (200, then 100 days) and falls to 10 days from March 15, 2029, so almost every renewal will need a fresh, automated domain validation.
Does the 47-day rule apply to internal or private certificates?
No. Ballot SC-081 changes the CA/Browser Forum Baseline Requirements, which cover publicly trusted TLS server certificates. Certificates from your own private CA are governed by your own policy.
How do I prepare for 47-day certificates?
Automate issuance and installation with an ACME client, renew at about two-thirds of the certificate lifetime, make sure domain validation (HTTP-01 or DNS-01) runs without manual steps, and monitor every certificate so a failed renewal is caught before it expires.