SSL certificates now last 200 days, and soon 47: what website owners need to do
TL;DR: The CA/Browser Forum, the body that sets rules for publicly trusted SSL/TLS certificates, voted to shorten the maximum certificate lifetime in stages. It fell from 398 days to 200 days in March 2026, goes to 100 days on 15 March 2027 and to 47 days on 15 March 2029. If your host or an ACME tool such as Certbot renews certificates automatically, you will barely notice. If you buy certificates and install them by hand, the number of renewals per year rises and a missed one means a "Your connection is not private" warning for every visitor. The fix is to inventory your certificates, move to automated renewal and monitor expiry dates.
What changed and when
Until early 2026, a publicly trusted certificate could be valid for up to 398 days, roughly 13 months. Ballot SC-081v3 of the CA/Browser Forum reduced that in three steps. The schedule below is by issuance date, and a certificate issued before a cutoff keeps its original lifetime until it is renewed or reissued.
| Effective date | Maximum certificate validity |
|---|---|
| Before 15 March 2026 | 398 days |
| 15 March 2026 | 200 days |
| 15 March 2027 | 100 days |
| 15 March 2029 | 47 days |
The proof of domain control that a certificate authority collects, called domain control validation, can also be reused for a shorter and shorter time. By 2029 it drops to about 10 days, which makes manual validation impractical.
Dates vary slightly in announcements, and some authorities began enforcing a shorter limit a little before the formal cutoff. Treat the table as the schedule and check your certificate authority's notices for its own dates.
Who is affected
The rules cover publicly trusted TLS certificates: domain validated, organisation validated, extended validation, wildcard and multi-domain certificates. They do not apply to private certificate authorities or self-signed certificates used internally.
In practice:
- Sites on hosting with automatic SSL (AutoSSL, Let's Encrypt integrations, managed platforms): your host renews the certificate, and little changes for you.
- Sites using Certbot or another ACME client: renewal already runs on a short cycle, typically every 60 to 90 days, so you are already used to this rhythm. Check that your renewal job actually works. See setting up automatic SSL renewal with Certbot.
- Sites using purchased certificates installed by hand: you are the most affected. A one-year certificate used to need one renewal a year. At 200 days it needs two, at 100 days about four, and at 47 days about eight.
- Certificates inside load balancers, CDNs, mail servers and appliances: easy to forget, because they are not on the website itself.
If you are unsure what the different certificate types mean, our guide to DV, OV and EV certificates explains them, and free vs paid SSL covers what a paid certificate adds.
What breaks if a certificate expires
When a certificate expires, browsers show a full-page warning and many visitors leave. APIs and apps that call your server fail with certificate errors. Payment callbacks and webhooks can stop working, and email clients may refuse to connect. Search engines also see the problem. Our guide to the connection is not private error shows how it looks and how to diagnose it.
Shorter lifetimes do not make certificates less secure to forget. They make forgetting more likely, which is the point of the change: it pushes everyone towards automation.
Step 1: list every certificate you own
You cannot manage what you have not listed. Write down, for each domain and subdomain:
- the domain names covered, including
www,mail,apiand any staging subdomains, - where the certificate is installed (web server, CDN, load balancer, mail server),
- the certificate authority and type,
- the expiry date,
- how it renews, and who is responsible.
To read a live certificate's dates from the command line:
echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null | openssl x509 -noout -dates -subject
Run this for each public hostname. You may find forgotten subdomains with certificates nobody renews.
Step 2: check how each one renews
Put each certificate in one of three groups:
- Fully automatic. Renewed by your host, CDN or an ACME client with no action from you.
- Semi-manual. You receive a reminder and must reissue and install the certificate.
- Manual and unmonitored. Nobody is sure who renews it. This is the dangerous group.
For group 2 and 3, decide whether to move to automation or accept the extra work at 200, 100 and 47 days. Over time, group 2 becomes impractical.
Step 3: automate renewal
Most public sites can use free certificates through the ACME protocol, which was designed for automatic issuing and renewal.
- Shared hosting: use the host's automatic SSL feature if it offers one, and confirm it renews on its own.
- VPS or dedicated server: install an ACME client such as Certbot, or the one built into your web server or panel, and make sure the renewal timer is active. Test renewal without issuing:
sudo certbot renew --dry-run
- Wildcard certificates: these usually need DNS-based validation, which requires an ACME client that can update your DNS records through an API.
- CDN or proxy in front of your site: make sure certificates at the edge and at the origin are both covered.
- Appliances and software that cannot use ACME: ask the vendor about support, or place a proxy that can in front of them.
If your certificate authority and tooling support ACME, you can keep a paid certificate and still automate its renewal. Check that your provider supports it before relying on it.
Step 4: monitor expiry
Automation fails silently, so watch it. Set alerts on the expiry date of each certificate, ideally with warnings at 30, 14 and 7 days. A good uptime monitor includes certificate expiry checks. Our guide to uptime monitoring that alerts you before customers notice shows how to set them up.
Also watch for the cause of most failed renewals: DNS changes that break validation, a firewall blocking the validation request, a redirect that sends the validation path to the wrong place, or an expired API key for DNS updates.
Paid certificates and the new rules
If you pay for a certificate, the term you buy and the certificate's actual lifetime are no longer the same. A provider may sell a one-year subscription, but each certificate inside it lasts no more than 200 days now and less later, so you reissue within the term at no extra charge. That means you must complete validation and install the new certificate each time, unless you use automation.
When you compare providers, ask whether they support automated issuance, how reissuing works and how they notify you before expiry. A cheap certificate with a painful manual process may cost more than a free automated one.
A simple plan before March 2027
- This month: inventory every certificate and its renewal method.
- Next month: move at least the public website certificates to automated renewal.
- By January 2027: automate or replace the awkward ones, such as mail servers and internal tools exposed to the internet.
- By February 2027: run a dry-run renewal on every system and confirm alerts reach a person.
- From March 2027: review again, because the next step is a 100-day limit.
FAQs
How long do SSL certificates last now?
Publicly trusted certificates issued after the March 2026 change can be valid for at most 200 days. Older certificates keep their original lifetime until they expire.
When does the 47-day limit start?
On 15 March 2029, according to the CA/Browser Forum schedule. A 100-day limit applies from 15 March 2027.
Do I have to renew by hand more often?
Only if you do not automate. With automated renewal, the change is invisible. By hand, you renew more often every year.
Does this affect free Let's Encrypt certificates?
Those already have short lifetimes and are designed to renew automatically. If your renewal works today, you are already in good shape.
What happens if I miss a renewal?
Browsers show a security warning, visitors leave and APIs and webhooks that depend on the certificate fail until you install a new one.
Can I still buy a one-year certificate?
You can buy a one-year subscription from many providers, but the actual certificate lifetime inside it is shorter, so you must reissue during the year.
Does this apply to self-signed or internal certificates?
No. The rules apply to publicly trusted certificates, not private authorities or self-signed ones.
How do I know when my certificate expires?
Open the certificate details in your browser, run the openssl command above, or use a monitoring service that alerts you before expiry.
Conclusion
Shorter certificate lifetimes are a nudge to stop treating SSL as an annual chore. Inventory what you have, find the manual renewals, automate them and add expiry alerts. Done well, you will not notice the 200-day, 100-day or 47-day limits, and your visitors will never see a warning page.
HostCloud's hosting plans include SSL so your sites stay secure without manual work. See the options at https://hostcloud.in.
Sources: