TLS Certificates Now Last 200 Days at Most: Who Tracks Your Renewals?
If you bought a one-year SSL certificate in September last year, it is about to expire. The replacement will not last a year. Since 15 March 2026, the maximum lifetime of publicly trusted TLS certificates has been 200 days, down from 398. That was the first step of CA/Browser Forum ballot SC-081, adopted in April 2025, and more steps follow.
The schedule: 200, 100, 47
| Date | Maximum certificate lifetime | 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 |
These limits apply only to certificates from publicly trusted authorities. Certificates issued by your own internal CA are not affected. Certificates issued before March 2026 also keep working until their natural expiry, so nothing breaks overnight.
What changes on your calendar
Renewals per year, for a single certificate:
- 398-day certificate: about 1
- 200-day: 2
- 100-day: about 4
- 47-day: about 8
A company with a website, a mail gateway, a VPN portal, a remote desktop gateway, a customer portal and a few subdomains is looking at more than 50 renewals a year by 2029. One renewal a year can be done by hand. One every few weeks cannot; somebody will forget.
What an expired certificate actually breaks
The server does not crash. Visitors get a full-page browser warning, and most turn back. The more painful failures are elsewhere:
- Accounting, e-invoicing or warehouse software calling a certificate-protected API starts failing without a clear error.
- The SSL VPN or remote desktop gateway throws warnings and the home-working team cannot connect.
- TLS between mail servers fails, and some counterparties reject the mail.
- A mobile app fails certificate validation and nobody knows why.
These tend to surface on a Friday evening or the day before a public holiday. The cause is usually mundane: the person who bought the certificate left, and the reminders go to their old mailbox.
Manual tracking or automation?
| Method | Enough when | Weak spot |
|---|---|---|
| Calendar reminder / spreadsheet | Under 5 certificates, 2 renewals a year | Depends on one person, records go stale |
| Provider’s warning emails | One provider only | Nobody knows whose inbox gets them |
| ACME auto-renewal | Web servers, reverse proxies | Appliances and legacy software may not support it |
| Expiry checks in remote monitoring | Many certificates, mixed devices | Needs one-time setup |
ACME automates requesting, validating and installing a certificate. Let’s Encrypt already issues 90-day certificates, so teams using it are well placed for shorter lifetimes. The hard part is anything that does not speak ACME, such as firewalls, load balancers and older mail gateways. Those need either the provider’s management tool or a reverse proxy placed in front.
What to do in the next two months
- Build an inventory. For every externally reachable domain and subdomain: who bought the certificate, from which provider, when it expires, which device it sits on.
- Name a real owner. Notifications should go to a shared address (a bt@ style mailbox) that at least two people can see, not to an individual.
- Hook expiry dates into monitoring. Alerts at 30, 14 and 7 days. Certificate checks come built into remote monitoring tools.
- Separate what can be automated. Websites and reverse proxies move to ACME; plan the appliances separately.
- Reflect it in the budget. A multi-domain or wildcard certificate often creates less work than many single ones. As renewals multiply, staff time becomes a real cost line.
Frequently asked questions
Is my existing 398-day certificate invalid right now? No. Certificates issued before March 2026 stay valid until their expiry date. The new limit applies when you renew.
Can I still ask for a longer lifetime? No. However long a package the provider sells, a single certificate cannot exceed the cap. Even with a multi-year plan you will reissue and install the certificate at intervals.
Does this apply to internal servers? Certificates from your own internal CA are outside these rules. Any certificate from an authority that browsers trust is in scope.
Sources? The schedule follows CA/Browser Forum ballot SC-081 and summaries published by DigiCert and GlobalSign.
If you do not know how many certificates your company has or who tracks them, an inventory is half a day of work. For help, get in touch.
Related Posts
What Happens When the One Person Who Knows Your IT Leaves?
In most offices one person knows the router password, who owns the domain name and where the backup goes. Here is what access, records and ownership the company should hold before that person walks out, step by step.
Read more: What Happens When the One Person Who Knows Your IT Leaves?
Scan-to-Email May Stop Working in December 2026: What to Check
Microsoft will disable Basic authentication for SMTP AUTH by default in Exchange Online at the end of December 2026. Here is how to find the printers, scanners and old apps that depend on it, and what to replace it with.
Read more: Scan-to-Email May Stop Working in December 2026: What to Check
New Hire Starts Monday: What IT Needs Ready Before Day One
If a new hire spends the first morning waiting for a laptop, an email address and a password, the process is missing a step. Accounts, licences, devices and MFA, in the order they should happen.
Read more: New Hire Starts Monday: What IT Needs Ready Before Day One