Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Short-lived certificates expire in days or weeks instead of a year, replacing unreliable revocation with a validity window too narrow for a stolen key to be worth much.

What Are Short-Lived Certificates?
A short-lived certificate is one whose validity period is measured in days or weeks rather than the 398 days the public web has allowed since 2020. The idea is blunt and effective: if a certificate is only valid for a week, a stolen private key is worth very little, and the industry no longer has to rely on revocation machinery that has never worked properly.
This is no longer a niche practice. In April 2025 the CA/Browser Forum adopted ballot SC-081, which steps the maximum lifetime of publicly trusted TLS certificates down to 47 days by 2029.
When a private key is compromised, the certificate is supposed to be revoked and clients are supposed to notice. In practice:
Shortening the validity window sidesteps all of this. Expiry is enforced by every client, offline, with no network call and no failure mode to exploit.
| From | Maximum certificate lifetime | Maximum reuse of domain validation |
|---|---|---|
| Today | 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 |
The second column is the one most teams overlook. Reducing domain validation reuse to ten days means the validation itself—the DNS record or HTTP token proving you control the name—must also be automated, not just the certificate request.
At 47 days, manual certificate handling stops being viable. A certificate issued by raising a ticket, generating a CSR by hand, and emailing a file would need that process eight times a year per name. The practical requirements are:
Certificate outages are not theoretical. On 6 December 2018 an expired certificate inside Ericsson software took down O2’s data network for most of a day, affecting around 32 million UK customers and several million more internationally. Microsoft Teams was unavailable for hours in February 2020 for the same reason. As lifetimes shorten, the number of opportunities for that mistake multiplies, which is why the renewal path deserves the same resilience testing as the service it protects—particularly for organisations in scope of the NIS Regulations or operational resilience rules.
Inside a service mesh the trend runs further. SPIFFE-based issuers such as SPIRE, and the mesh integrations built on them, hand out identity certificates valid for an hour or less, rotated automatically with no human in the loop. Let’s Encrypt added a six-day profile for public certificates in 2025 on the same logic. When rotation is fully automated, a compromised key stops being an incident and becomes a non-event.
Our Infrastructure and Architecture Review Services include certificate lifecycle readiness, so you learn which systems break at 47 days before the deadline rather than after it.
Because revocation does not reliably reach clients. If a private key is stolen, the only dependable limit on the damage is the certificate’s expiry date, which every client enforces without a network call. Shorter lifetimes also force automation, and automated issuance tends to produce better key hygiene, accurate inventories, and fewer forgotten certificates than annual manual renewals.
Only the ones that cannot renew automatically. Web servers, load balancers, and cloud services behind ACME clients will not notice the change. The risks sit with appliances that require a manual upload, mobile apps with pinned leaf certificates, partner integrations that whitelist a specific certificate, and embedded devices. Identify those now and plan a different approach for each.
The CA/Browser Forum rules govern publicly trusted certificates, so a private CA can still issue longer-lived ones. In practice most organisations align internal policy with the public timetable because the automation is the same, and because a private CA with long lifetimes becomes the weakest link in an otherwise well-rotated estate.
Build an inventory. Pull your public certificates from Certificate Transparency logs, scan your internal ranges for TLS services, and record the owner, issuer, expiry, and renewal method for each. Anything without an automated renewal path goes on a remediation list. Only once that list is short does switching the rest to ACME become a straightforward piece of engineering.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.