Official update · Let’s Encrypt announcement dated October 7, 2026
Let’s Encrypt sets February 10, 2027 as the date when newly issued or renewed default certificates move to 64-day lifetimes. The organization says it will not revoke valid certificates because of this transition.
The announced schedule
| Date | Announced change |
|---|---|
| October 14, 2026 | Scheduled availability of 64-day certificates in staging |
| February 10, 2027 | 64-day production default |
| February 16, 2028 | Planned 45-day production default |
What administrators should check
The announcement recommends checking ACME client support for ARI, which supplies renewal timing information, and reviewing fixed-interval renewal schedules. A test schedule does not prove that renewal works on every server.
Operational clarification — 24 October 2026: The official timeline reduces classic-profile domain-authorization reuse from 30 to 10 days on 10 February 2027, then to 7 hours on 16 February 2028. This authorization window is not certificate lifetime. Added to prevent confusion between them; AI-assisted clarification, not an ACME client test or server configuration change.
BYT01’s perspective
Look for evidence that renewal and certificate deployment complete, with a failure alert. This is an operational reading of the announcement. BYT01 has not inspected readers’ configurations or changed its own certificates.
Follow related infrastructure reporting in BYT01 Quick News.
Sources and verification
BYT01 checked the sources on October 14, 2026.
Decision and evidence limits
BYT01 conclusion: Check renewal, deployment and failure alerts together; test the change before production.
| Item | Evidence boundary |
|---|---|
| Article type | Official-announcement guidance; no inspection of reader systems. |
| Material limitation | Let’s Encrypt’s schedule does not prove that your ACME client or deployment renews correctly. |
| Measurement requirements | Record client/version, ARI support, renewal time, deployed certificate and failure alert; this article does not change production certificates. |
The timeline documents the issuer’s plan; successful renewal and deployment in your own environment require separate verification.
This editorial revision used AI assistance and has no recorded independent human expert sign-off.
Test protocols and evidence · Commercial disclosure · Corrections policy · Related decision guide
Update — 23 October 2026: Revised the decision summary, evidence limits, comparison conditions, disclosure and links. This is an editorial revision date, not a new hardware measurement or a recheck of every retailer offer.