Every secure website uses an SSL/TLS certificate, the thing behind the padlock and "https". For years, certificates could last more than a year, and many businesses renewed them manually once a year with a calendar reminder.
That's ending. The CA/Browser Forum, the body of certificate authorities and browser makers that sets the rules, voted in 2025 to shorten maximum certificate lifetimes in stages, down to 47 days by 2029. The first step took effect in March 2026.
The timeline
| From | Maximum certificate validity | 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 |
"Domain validation reuse" is how long a certificate authority can rely on an earlier check that you control the domain before checking again.
Why the change
- Security: if a certificate's private key is stolen or a certificate is issued wrongly, a shorter lifetime limits how long it can be misused.
- Accurate information: domain ownership and company details change; shorter lifetimes mean certificates reflect reality more closely.
- Pushing automation: the industry wants renewals automated, which reduces human error and outages.
Who's affected
| Setup | Impact |
|---|---|
| Let's Encrypt with automatic renewal | Little; already 90-day certificates |
| Managed hosting, website builders, Shopify, Wix | Little; the platform renews automatically |
| Cloudflare or another CDN managing edge certificates | Little at the edge; check your origin certificate setup |
| Manually bought and installed certificates | High; manual renewal several times a year becomes impractical |
| Internal servers, appliances, mail servers, VPNs using public certificates | High; often forgotten |
| Organisation-validated (OV) or extended validation (EV) certificates | Higher effort: validation also needs repeating more often |
What to do now
1. List every certificate you have
Websites, subdomains, APIs, mail servers, VPNs, load balancers, staging sites. Note who issues each one, how it's renewed and when it expires.
2. Automate renewal everywhere
Use the ACME protocol (the standard Let's Encrypt and many commercial authorities support) with tools built into your server, host or CDN. Web servers like Caddy obtain and renew certificates automatically by default.
3. Monitor expiry
Automation can fail silently: a DNS change, a firewall rule or an expired API token can stop renewals. Set up monitoring that alerts you weeks before any certificate expires. Zelvorm Watch keeps checking your website for problems, and many uptime tools check certificates too.
4. Check your CDN and origin
If you use Cloudflare, the edge certificate is managed for you, but with SSL set to Full (strict), your origin server also needs a valid certificate. Read Cloudflare for small business websites.
5. Review OV/EV needs
If you buy organisation-validated certificates for business reasons, plan for more frequent validation, or consider whether domain-validated certificates meet your needs.
6. Document the process
Write down how certificates are issued, renewed and monitored, so it survives staff or agency changes. Include it in your website handover checklist.
Common failure points
- Renewal script runs, but the web server isn't reloaded to use the new certificate.
- DNS validation fails after moving DNS providers.
- Firewall or CDN rules block the validation request.
- The certificate is renewed on one server but not others behind a load balancer.
- A forgotten subdomain or mail server uses a manually installed certificate.
Related security basics
Short-lived certificates are one part of a secure site. Also check HTTP security headers, website security basics and domain name security. Many outages blamed on "the website being down" are actually expired certificates. See why websites go down.
How to check a certificate's expiry date
In a browser: click the padlock (or site settings icon) in the address bar, open the connection or certificate details and look at "Valid to" or "Expires on".
From a terminal, for any domain:
echo | openssl s_client -servername example.com -connect example.com:443 2>/dev/null | openssl x509 -noout -dates
The notAfter date is when it expires.
Across many domains: use monitoring that checks every hostname daily and alerts at, say, 21 and 7 days before expiry. With 47-day certificates, a two-week warning window is the minimum sensible margin.
What a healthy renewal setup looks like
| Element | Healthy setup |
|---|---|
| Issuance | ACME client, CDN or host issues certificates automatically |
| Renewal timing | Renews well before expiry (often around two-thirds of the way through the lifetime) |
| Deployment | New certificate is loaded automatically, with no manual restart |
| Validation | DNS or HTTP validation works through your CDN and firewall |
| Monitoring | Independent check alerts you if any certificate is close to expiry |
| Ownership | A named person or supplier is responsible, documented in writing |
The short version
Maximum SSL/TLS certificate lifetimes dropped to 200 days in March 2026 and will fall to 100 days in March 2027 and 47 days in March 2029. If your host, builder or CDN manages certificates, you're probably fine. If anyone renews certificates manually, inventory them now, automate renewal with ACME and monitor expiry so nothing lapses.
Want certificates and monitoring handled for you? Our maintenance and support team looks after it as part of every care plan.




