SSL certificates7 min read
SSL certificates are moving to 47 days: what changes in 2026, 2027 and 2029
By the RenewalRemind team
Under CA/Browser Forum ballot SC-081v3, the maximum lifetime of a public SSL/TLS certificate fell from 398 days to 200 days on 15 March 2026, drops to 100 days on 15 March 2027 and to 47 days on 15 March 2029. Manual yearly renewals stop working: every site needs automated renewal plus independent monitoring of the certificate actually being served.
Key takeaways
- 200 days since 15 March 2026, 100 days from 15 March 2027, 47 days from 15 March 2029.
- Domain validation can be reused for less time too — down to 10 days by 2029.
- Buying a "1-year certificate" now means reissuing it at least twice a year, and up to 8 times a year by 2029.
- Automate issuance (ACME) and independently check the expiry date of the certificate each site is really serving.
For years, an SSL/TLS certificate could last up to 398 days, so most site owners renewed once a year and forgot about it. That is ending. In April 2025 the CA/Browser Forum — the group of certificate authorities and browser makers (Apple, Google, Microsoft, Mozilla and others) that sets the rules for public certificates — approved ballot SC-081v3, which shortens the maximum lifetime of a certificate in three steps until it reaches 47 days in 2029.
The timeline
Each limit applies to certificates issued on or after the date. Certificates issued before a deadline keep their original expiry date.
| Issued on or after | Maximum validity | Domain validation reuse | Renewals per year (at least) |
|---|---|---|---|
| Before 15 March 2026 | 398 days | 398 days | 1 |
| 15 March 2026 | 200 days | 200 days | 2 |
| 15 March 2027 | 100 days | 100 days | 4 |
| 15 March 2029 | 47 days | 10 days | 8 |
Domain validation reuse is how long a certificate authority may rely on an earlier check that you control the domain. By 2029 that check has to be repeated almost every time a certificate is issued, which in practice means it must be automated too.
Why browsers want shorter certificates
- Less damage from a leaked key. If a private key is stolen, a short-lived certificate stops being useful much sooner.
- Revocation doesn't work well. Browsers check revoked certificates inconsistently; letting certificates expire quickly is a more reliable way to retire them.
- Fresher ownership checks. Domains change hands. Re-validating often means a certificate reflects who controls a domain today, not a year ago.
- Forcing automation. Teams that renew automatically can also swap algorithms or certificate authorities quickly when they need to.
What it means for your websites
If you use Let's Encrypt or your host's free SSL
Let's Encrypt certificates already last 90 days and renew automatically through an ACME client such as Certbot, or through your hosting control panel. The 2026 and 2027 limits change nothing for you. The 2029 limit will mean renewals roughly every month — fine when automation works, but the window to notice a broken renewal shrinks from weeks to days.
If you buy certificates and install them by hand
This is where it hurts. A "1-year certificate" is now sold as a subscription, and you reissue and reinstall the certificate at least twice a year — four times a year from March 2027 and about eight times a year from 2029. Every manual install is a chance to forget a server, a load balancer or the CDN in front of the site.
If you look after many client sites
Multiply the renewals by the number of sites. A freelancer with 30 client sites on manual certificates would go from 30 installs a year to around 240 in 2029. Tracking that in a calendar or spreadsheet stops being realistic.
How to prepare: a 5-step checklist
- List every certificate. Include every hostname (www, shop, mail, API subdomains) and every place a certificate lives: web servers, load balancers, CDNs, mail servers.
- Automate issuance wherever you can. Use ACME (Certbot, acme.sh, your host's built-in SSL, or your certificate authority's ACME endpoint for paid certificates).
- Automate installation and reload. A renewed certificate on disk does nothing until the web server reloads. Add a deploy hook that reloads Nginx or Apache after each renewal.
- Monitor what visitors actually get. Check the certificate each site serves from outside, and alert well before it expires — 14, 7 and 1 day out is a sensible pattern. See how to check an SSL certificate's expiry date.
- Budget for it. If you charge clients for SSL, move from a once-a-year fee to a managed service that covers the extra reissues.
The bottom line
Shorter certificates are coming whether you are ready or not: 200 days now, 100 days from March 2027 and 47 days from March 2029. Automate renewal, automate the server reload, and keep an independent check on every live certificate, so a failed renewal shows up as an alert to you rather than a security warning to your visitors.
Frequently asked questions
When do 47-day SSL certificates start?
The 47-day maximum applies to certificates issued on or after 15 March 2029. Before that, the limit is 200 days (from 15 March 2026) and 100 days (from 15 March 2027).
Do existing certificates stop working when the rules change?
No. A certificate stays valid until its own expiry date. The new limits only apply to certificates issued after each deadline.
Does this affect Let's Encrypt certificates?
Let's Encrypt certificates already last 90 days, which is under the 2026 and 2027 limits. The 2029 limit of 47 days will apply to them as well.
Can I still buy a multi-year SSL certificate?
Certificate authorities still sell multi-year subscriptions, but each certificate they issue under it can only be valid for the current maximum, so you reissue and reinstall it several times during the subscription.