Insight
Certificate lifetimes are shrinking: what 200, 100 and 47 days mean for your team
10 Nov 2026
In April 2025 the CA/Browser Forum approved Ballot SC-081v3, which reduces the maximum lifetime of publicly trusted TLS certificates in three steps. The domain-validation reuse period shrinks on a similar schedule, so organisations must prove control of their domains far more often.
| From | Maximum TLS certificate lifetime |
|---|---|
| 15 March 2026 | 200 days |
| 15 March 2027 | 100 days |
| 15 March 2029 | 47 days |
Why it matters
A team that renews each certificate once a year today will, at 47 days, renew roughly eight times a year. Spreadsheets, calendar reminders and manual requests do not scale to that pace, and a single missed renewal becomes an outage.
What to do now
- Discover every certificate, including those on cloud services, appliances and forgotten servers.
- Assign owners so every certificate has a person or team responsible.
- Automate renewal and deployment with ACME or your CA's APIs wherever you can, and with an approval workflow where you cannot.
- Monitor expiry and failures so a failed renewal is noticed days, not minutes, before it matters.
Private and internal PKI is not directly covered by the schedule, but many teams align internal policy to the same cadence so that everything is managed one way.