Skip to main content

Let's Encrypt cuts cert lifetimes to 64 days in Feb 2027

Let's Encrypt announces a reduction in free SSL/TLS certificate lifetimes to 64 days, starting in February 2027.

AI-written
Inewgen
09 Oct 2026Source: Ars Technica2 min read (0 views)
Share
Let's Encrypt cuts cert lifetimes to 64 days in Feb 2027

Stock photo for illustration only, not from the actual event

Font size
  • Let's Encrypt cuts free SSL/TLS certificate lifetimes
  • The new duration will be reduced to 64 days
  • The change takes effect starting February 2027
  • Website administrators must prepare for automated renewals

Let's Encrypt, the prominent provider of free digital security certificates, has announced a significant shift regarding the validity period of its SSL/TLS certificates. The organization will reduce the maximum lifetime of these certificates down to just 64 days, with the new policy officially taking effect in February 2027.

This reduction in certificate longevity is part of an ongoing industry-wide effort to enhance internet security standards. By shortening the validity window, the initiative ensures that encryption credentials remain robust and minimize potential windows of vulnerability should a certificate ever be compromised.

Shortening SSL/TLS certificate lifetimes is a growing security trend designed to force routine cryptographic hygiene. While manual renewals would become burdensome under a 64-day cycle, modern infrastructure overwhelmingly relies on automated protocols like ACME clients to handle renewals seamlessly in the background. Administrators who still rely on manual processes will need to adopt automation before the 2027 deadline to prevent unexpected downtime.

Web administrators and developers utilizing Let's Encrypt services will need to audit their infrastructure and ensure their certificate management pipelines are fully automated to accommodate the 64-day restriction ahead of the February 2027 enforcement date.

Source: Ars Technica

Comments

Leave a Comment
0/2000

Found something wrong in this article? Report an issue with this article