Let’s Encrypt announced general availability of its short-lived and IP-address certificates on 15 January 2026. The short-lived certificates are valid for 160 hours, a little over six days. They use an opt-in issuance profile; the announcement did not make six-day validity the default for every certificate.
IP-address certificates cover IPv4 and IPv6 addresses and must use the short-lived profile. This gives eligible services a certificate option that does not depend on presenting a domain name.
The operating implication
Our assessment is that a shorter validity period makes the whole renewal chain a service dependency. Issuance, retrieval, installation and activation need to succeed repeatedly. A green renewal job provides limited assurance if the endpoint continues serving an older certificate.
Teams considering the profile should establish who owns the automation, how a failed run is detected and how the certificate presented to users is checked. The recovery procedure should work when the usual renewal path is unavailable, with enough time remaining to act.
The relevant decision for each environment is whether its operating process can support the chosen certificate lifetime consistently. Changing the validity period should follow that assessment.