Guide
SSL certificate expiry and the move to shorter certificates
Certificates are getting shorter every year. Manual renewal stops being practical, and a missed renewal takes a site offline for every visitor.
Short answer
Since March 15, 2026, newly issued public TLS certificates can be valid for at most 200 days, dropping to 100 days in 2027 and 47 days in 2029, so certificates should renew automatically and you should monitor expiry dates on every domain you run.
Key takeaways
- The CA/Browser Forum's schedule caps public certificate lifetimes at 200 days from March 15, 2026, 100 days from March 15, 2027 and 47 days from March 15, 2029.
- Certificates already issued keep the lifetime they were issued with; the cap applies to new ones.
- Automated renewal with ACME is the practical answer; manual yearly renewals no longer fit.
- Most outages come from automation that silently stopped, so check expiry dates independently.
- An expired certificate blocks visitors with a full-page browser warning, which is worse than slow pages or a broken image.
For years a TLS certificate was something you bought once a year, installed and forgot until a reminder email arrived. That rhythm is ending. The industry body that sets the rules for publicly trusted certificates has scheduled a series of cuts that take the maximum lifetime from just over a year down to 47 days. If any of your sites still renew by hand, the schedule below is the reason to change that.
How long can a TLS certificate last now?
Public TLS certificates issued on or after March 15, 2026 can be valid for at most 200 days.
The CA/Browser Forum, where certificate authorities and browser makers agree on the rules, passed ballot SC-081 in 2025. It sets three steps:
| Issued on or after | Maximum validity |
|---|---|
| March 15, 2026 | 200 days |
| March 15, 2027 | 100 days |
| March 15, 2029 | 47 days |
The same ballot also shortens how long a certificate authority may reuse an earlier domain validation, so a new certificate needs fresh proof that you control the domain more often. The stated aim is to limit how long a wrong or compromised certificate stays trusted.
What does this change for site owners?
Renewals become frequent enough that doing them by hand stops being realistic, so every certificate needs automated renewal.
At 47 days, a certificate needs replacing roughly every month and a half, and in practice sooner, since you want to renew before the last day. For one site, a calendar reminder might cope. For ten or a hundred domains, it won't. Most hosting platforms and CDNs already issue and renew certificates automatically, using the ACME protocol that Let's Encrypt made common. The change mainly hurts setups where someone uploads a certificate file by hand: older shared hosting, custom load balancers, appliances and some email or FTP servers.
Why do automated renewals still fail?
Automation fails quietly when a validation step breaks, so a renewal job can stop working months before anyone notices.
Common causes:
- DNS moved to a new provider and the DNS challenge credentials were never updated.
- A firewall or redirect rule blocks the
/.well-known/acme-challenge/path used for HTTP validation. - The domain now points to a different server, which has no renewal job.
- A CAA DNS record allows only a certificate authority you no longer use.
- The renewal succeeded but the web server was never reloaded, so it keeps serving the old certificate.
Each of these gives you a working site today and an expired one later. That gap is why independent checks matter.
How do you check a certificate's expiry date?
Read it from the live site, either in the browser's certificate viewer or with a command-line check, and record it per domain.
In a browser, click the icon next to the address and open the certificate details. From a terminal:
echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null | openssl x509 -noout -enddate
The notAfter line is the expiry date. Check every hostname you serve, including www and any subdomains, since they can have separate certificates.
The Robotto checker tests the TLS handshake on the https versions of your domain and shows the error when a certificate is expired, self-signed or issued for another name. It doesn't read certificate expiry dates yet; warnings before expiry are planned for scheduled monitoring.
Who is most likely to be caught out?
Sites with hand-installed certificates, paid multi-year certificate plans and servers outside the main hosting platform are most at risk.
Some vendors sell certificate "plans" of two or more years. Under the new rules, those plans are delivered as a series of shorter certificates that must each be installed. If the installation step is manual, every reissue is a chance to miss one. Ask your certificate vendor and host three questions: does renewal happen without anyone logging in, how will they tell you if it fails, and which hostnames does it cover. If the answer to the first is no, plan the move to automation now, while the cap is still 200 days and you have room to test.
Wildcard certificates deserve a note too. They usually need DNS validation, which depends on API credentials for your DNS provider. When those credentials expire or the DNS moves, wildcard renewals are the first to break.
How is this different from domain expiry?
Certificate expiry breaks HTTPS for a working domain, while domain expiry takes the whole name away, and both need tracking.
They fail differently. An expired certificate shows a browser warning but you still own the domain and can fix it in minutes. An expired domain stops resolving and can eventually be lost. The dates are unrelated, so track both. Our guide on tracking domain expiry covers the registry side.
A checklist for shorter certificates
- List every hostname that serves HTTPS, including mail, API and staging hosts.
- Confirm each one renews automatically, and note which tool or provider does it.
- Make sure the ACME challenge path is reachable or the DNS credentials are current.
- Check that the server reloads after renewal.
- Record expiry dates and check them weekly from outside your network.
- Remove certificates for hostnames you no longer use.
Questions
Does the 200-day limit apply to certificates I already have?
No. The limit applies to certificates issued on or after March 15, 2026. A certificate issued earlier keeps its original expiry date, but its replacement will be shorter.
Does this affect free certificates from Let's Encrypt?
Let's Encrypt certificates already last 90 days, which is under the 200- and 100-day caps. Let's Encrypt has announced its own plan to shorten them further, so automated renewal stays necessary.
What happens when a certificate expires?
Browsers show a full-page security warning and most visitors leave. APIs, apps and webhooks that call your site fail outright, because most HTTP clients refuse an expired certificate.
Do private or internal certificates have the same limit?
No. The CA/Browser Forum rules cover publicly trusted TLS certificates. Certificates from your own private certificate authority follow your own policy.