Published on
November 5, 2026
For years, 90-day TLS certificates have encouraged organisations to automate certificate renewal rather than rely on manual processes. Now, even that renewal window is getting shorter.
On October 7, 2026, Let’s Encrypt announced that it will move to 64-day certificate lifetimes by default from February 10, 2027. The change is another milestone in the industry's broader move towards shorter-lived public TLS certificates, with a further reduction to 45 days planned for February 2028.
For organisations that already have reliable certificate automation in place, this may be a relatively straightforward transition. For those still relying on manual renewals, fixed renewal schedules or fragmented certificate inventories, it is a warning sign.
The challenge is not simply renewing certificates more frequently. It is ensuring that every certificate is discovered, renewed, deployed and monitored reliably across the entire infrastructure.
And the industry timeline suggests that organisations have little reason to treat this as a one-off adjustment.
What is changing with Let’s Encrypt certificates?
Let’s Encrypt currently issues certificates with a default validity period of 90 days. From February 10, 2027, certificates issued or renewed under its default classic ACME profile will have a validity period of 64 days.
The transition will take place in stages:
Date | Change |
|---|---|
October 14, 2026 | 64-day certificates introduced in the staging environment for testing |
February 10, 2027 | 64-day certificates become the default in production |
February 16, 2028 | Default certificate lifetime reduced further to 45 days |
February 16, 2028 | Authorisation reuse period reduced to 7 hours |
The February 2027 change will also reduce the authorisation reuse period from 30 days to 10 days. This determines how long Let’s Encrypt can reuse previous domain-control validation information when issuing a new certificate.
Let’s Encrypt expects the last 90-day certificate issued under the old default to expire on May 11, 2027. Existing valid certificates will not be revoked as part of the transition.
Importantly, this is not an isolated decision by one certificate authority. It forms part of a wider transformation of the public Web PKI.
Why are TLS certificate lifetimes getting shorter?
Shorter certificate lifetimes are intended to improve the security and resilience of the Web PKI.
There are two main reasons behind this direction.
1. Reducing the exposure window
A certificate that has been mis-issued or whose private key has been compromised can be used to impersonate a legitimate website or service.
Reducing its validity period limits the amount of time that certificate can remain usable before it expires, even when revocation or replacement processes do not happen immediately.
Shorter lifetimes therefore help reduce the exposure window associated with compromised keys and mis-issued certificates.
2. Making certificate automation essential
Shorter lifetimes also encourage organisations to move away from manual certificate management.
When certificates remain valid for a year, manual renewal processes may appear manageable. With 90-day certificates, the pressure to automate becomes more apparent. At 64 days and eventually 45 days manual management becomes increasingly difficult to sustain at scale.
Automation is no longer simply a way to save administrators time. It becomes a fundamental requirement for maintaining service availability and operational security.
Let’s Encrypt is part of a broader industry transition
The move to 64-day certificates should be understood in the context of changes approved by the CA/Browser Forum.
Its updated TLS Baseline Requirements establish a progressive reduction in the maximum validity period for publicly trusted TLS subscriber certificates:
Effective date | Maximum certificate validity |
|---|---|
Before March 15, 2026 | 398 days |
March 15, 2026 | 200 days |
March 15, 2027 | 100 days |
March 15, 2029 | 47 days |
These requirements apply to publicly trusted TLS certificates issued by participating Certificate Authorities. Let’s Encrypt's 64-day schedule is its own implementation plan, while the CA/Browser Forum defines the broader industry limits.
This distinction matters: organisations should not prepare only for Let’s Encrypt's February 2027 change. The wider ecosystem is moving towards significantly shorter certificate lifetimes, regardless of which public CA they use.
The direction is clear. Certificate renewal cycles will become more frequent, and the operational processes behind them will need to keep pace.
What does this mean for certificate management?
The practical impact depends on how certificates are currently managed.
An organisation with centralised discovery, automated renewal and reliable deployment workflows may be well positioned. An organisation with certificates spread across teams, environments and infrastructure with limited visibility over ownership or expiry dates faces a different level of risk.
Take control of your PKI infrastructure
See how Evertrust simplifies certificate lifecycle management.
Get StartedShorter certificate lifetimes can expose weaknesses in several areas.
Certificate discovery and inventory
Organisations need to know where certificates are deployed, which services depend on them, when they expire and who is responsible for managing them.
Without a reliable inventory, certificates can remain hidden across cloud environments, load balancers, applications, endpoints and internal infrastructure.
A certificate that nobody knows about is unlikely to be renewed on time.
Renewal automation
Renewal schedules designed around 90-day certificates may no longer be appropriate.
Let’s Encrypt recommends using ACME Renewal Information (ARI), which allows compatible ACME clients to receive renewal guidance from the Certificate Authority.
Where ARI is not supported, renewal schedules need to be reviewed. Let’s Encrypt recommends renewing at approximately two-thirds of a certificate's lifetime rather than relying on hard-coded dates based on the previous 90-day model.
Organisations should review cron jobs, scripts, ACME clients and runbooks for assumptions that may no longer hold.
Deployment and service continuity
Renewing a certificate is only one part of the lifecycle.
Once a new certificate has been issued, it must reach the systems that rely on it. Services may need to reload, applications may need to retrieve updated certificates, and dependent infrastructure must continue operating correctly.
An automated renewal that fails to deploy the new certificate does not prevent an outage.
The entire process from discovery to deployment needs to be tested.
Monitoring and ownership
Organisations should be able to detect failed renewals, unsuccessful deployments and certificates approaching expiry.
Monitoring should also be connected to clear ownership and escalation processes. If a renewal fails, the relevant team needs to know quickly enough to intervene before the certificate expires.
As renewal cycles become shorter, delayed detection leaves less time to recover.
Five actions to prepare for shorter certificate lifetimes
Organisations do not need to wait until 2027 to start preparing. The transition provides an opportunity to review certificate management processes before renewal windows become even tighter.
Here are five practical steps.
1. Establish a complete certificate inventory
Identify certificates across your infrastructure, including public-facing services, internal applications, cloud platforms, network devices and endpoints.
Capture essential information such as certificate owner, location, issuing CA, validity period, expiry date and dependent service.
The objective is to establish a reliable source of truth rather than maintain disconnected spreadsheets and team-specific inventories.
2. Audit renewal mechanisms
Review existing ACME clients, scripts, scheduled jobs and manual renewal procedures.
Check whether your ACME clients support ARI and whether renewal schedules account for shorter certificate lifetimes.
Pay particular attention to hard-coded renewal intervals that may have been designed around 90-day certificates.
3. Automate the full certificate lifecycle
Renewal should not be treated as an isolated task.
Build automation that covers certificate discovery, request, issuance, deployment, service reload and monitoring. Test the complete workflow to confirm that newly issued certificates actually reach every required endpoint.
4. Review certificate ownership and responsibilities
Identify which teams own the services and infrastructure associated with each certificate.
Clear ownership is essential when renewal or deployment fails. Without it, an organisation may detect an expiring certificate but still struggle to identify who can resolve the issue.
5. Test before the transition
Use staging environments and controlled test deployments to validate automation ahead of the production changes.
Test renewal failures, deployment errors, service reloads and alerting. The goal is to identify operational weaknesses before shorter validity periods make them more difficult to manage.
Why Certificate Lifecycle Management is becoming essential
As certificate lifetimes shrink, managing certificates individually becomes increasingly difficult.
Certificate Lifecycle Management (CLM) provides a centralised approach to discovering, issuing, renewing, monitoring and governing certificates across an organisation's infrastructure.
Rather than relying on individual teams to track expiry dates and manage renewals, organisations can establish consistent processes and improve visibility over their certificate estate.
A mature CLM approach helps organisations:
Discover certificates across heterogeneous environments.
Maintain an up-to-date inventory and monitor certificate status.
Automate certificate requests, issuance and renewal.
Integrate with infrastructure and endpoint management systems.
Monitor expiry dates and identify potential service disruptions.
Establish governance, ownership and auditability.
This becomes particularly important in complex environments where certificates are issued by multiple authorities and deployed across different platforms, teams and business applications.
The objective is not simply to renew certificates faster. It is to make certificate management predictable, controlled and resilient even as renewal cycles continue to shorten.
Shorter certificate lifetimes are a change in operating model
The move to 64-day certificates is another step in a transition that has been underway for several years. The next milestones (100-day maximum validity in 2027 and 47 days in 2029) will continue to reshape how organisations manage digital certificates.
For IT and security teams, the question is no longer whether certificate renewal needs to be automated. It is whether the entire certificate lifecycle can operate reliably at a much faster pace.
Organisations that have visibility over their certificate estate, automated renewal and deployment processes, and clear ownership will be better equipped to adapt.
Those that do not may find that a routine certificate renewal becomes an increasingly frequent source of operational risk.
Shorter certificate lifetimes are not just a change to certificate validity. They are a test of how well organisations manage digital trust across their infrastructure.
Frequently asked questions
When will Let’s Encrypt move to 64-day certificates?
Let’s Encrypt will make 64-day certificates the default for its classic ACME profile on February 10, 2027. The change will apply to certificates issued or renewed on or after that date.
When will TLS certificates become 47 days?
Under the CA/Browser Forum's updated Baseline Requirements, the maximum validity period for publicly trusted TLS certificates will decrease to 47 days from March 15, 2029.
Will all certificate authorities move to shorter certificate lifetimes?
Publicly trusted Certificate Authorities must follow the CA/Browser Forum's TLS Baseline Requirements. The maximum permitted validity period is being reduced progressively, reaching 47 days in March 2029.
What is ACME Renewal Information (ARI)?
ARI is a mechanism that allows an ACME client to receive renewal guidance from a Certificate Authority. It helps clients determine when to renew certificates and supports more reliable automated renewal processes.
Do shorter certificate lifetimes require certificate management automation?
They make automation increasingly important. More frequent renewals increase the workload associated with manual processes and leave less room for operational delays. Automation helps coordinate discovery, renewal, deployment and monitoring.
What is Certificate Lifecycle Management (CLM)?
Certificate Lifecycle Management is the centralised management of digital certificates throughout their lifecycle, from discovery and issuance to renewal, monitoring and eventual retirement.
Explore Certificate Lifecycle Management
Discover how centralised certificate discovery, automation and governance can help organisations manage increasingly dynamic certificate environments.