Let’s Encrypt, the free and open certificate authority widely used to secure websites with HTTPS, announced it will shorten the default validity period of its TLS certificates from 90 days to 64 days, starting February 10, 2027.
All certificates issued or renewed from that date will have a 64-day lifespan unless users explicitly select one of the shorter options already available: 45 or six days.
Existing certificates will remain valid until their expiration dates. Let’s Encrypt expects the final 90-day certificate to expire on May 11, 2027. The organization also confirmed no valid certificates will be revoked during the transition.
To help administrators prepare, Let’s Encrypt will introduce 64-day certificates in its staging environment on October 14, 2026, allowing users to test their renewal setups before the change reaches production.
The move is part of a broader effort to improve web security by reducing how long compromised or incorrectly issued certificates remain usable. Simply put, shorter certificate lifetimes mean attackers have less time to exploit a stolen private key.
Of course, shorter validity periods also mean certificates must be renewed more frequently. For website administrators already using automated renewal tools, this should require little or no intervention.
In particular, Let’s Encrypt says users whose ACME clients support ACME Renewal Info should be ready for the transition. ARI allows the certificate authority to inform clients when certificates should be renewed, rather than relying on fixed schedules.
However, administrators using cron jobs or scripts with hardcoded renewal intervals should review their configurations. Instead of renewing a certificate a fixed number of days before expiration, Let’s Encrypt recommends scheduling renewals after approximately two-thirds of its validity period has passed.
The organization suggests checking scripts and configuration files for hardcoded values like 83, 80, or 60 days, which may no longer work reliably with shorter-lived certificates.
Another upcoming change concerns domain validation. Let’s Encrypt will reduce the period during which a previously completed domain authorization can be reused from 30 days to 10 days. In 2028, that period will shrink further to just seven hours.
The goal is to align with upcoming industry requirements and simplify how the certificate authority handles previously validated domains. Most users won’t need to make adjustments unless their ACME clients depend on reusing earlier authorizations.
Importantly, the transition won’t change Let’s Encrypt’s existing rate limits, ACME endpoints, or certificate issuance chains.
Looking further ahead, the organization plans to reduce the default certificate lifetime again, this time to 45 days in 2028. That makes the upcoming 64-day limit an intermediate step rather than the final destination.
For more information, see Let’s Encrypt’s official announcement.
Ah good that way US sanctions cut off designated bad guys from encryption that much faster.
Also good because heavy automation means larger opportunities for the NSA and eyes countries to hack you, change that automation slightly and compromise your infrastructure to their liking and you won’t even notice because things are changing so often you as a human cannot possibly keep up and review these things.
Centralized trust is already experiencing a massive crisis as it’s entirely under the control of very untrustworthy, abusive western authorities centralized within the US and subject to subterfuge by spy agencies, political machinations, sanctions laws, etc.
Attackers really don’t need more than a few days to exploit stolen private keys anyway. Assuming they’re using an attack kit with good zero days in tandem with it (pretty likely with AI assisted exploit finding) so all this will result in is attackers adapting IMO.
In my current setup, I think my reverse proxy does not detect certificate updates (done by a different service), and I am just lucky that usually the service restarts because of some update before the old one expires.
Once that is solved, I am tempted to try the six-day expiration.
use pangolin bro
Not good. Not all systems can recreate automatically a new certificate.
I think the point is to encourage automation. Systems that can’t will need to find a way, or else.
I’m sorry, I don’t see the problem. They had to manually renew them before as well. Yes, it’s annoying to do it more often, but other than that there wouldn’t be much change
I have to manually run renewal scripts because my domain providers aren’t supported via autoscripts.
Did you consider the DNS-PERSIST-01 ACME challenge? You have to add a persistent TXT entry to your DNS, and then you are independent from provider support for renewals.
This is extremely work in progress and to my knowledge only currently available for basic certificates not wildcard ones. I assume since @doomsdayrs@lemmy.ml is dealing with dns stuff, she needs a wildcard cert.
Might be good for the future tho when (if) that is added.
Paternalism!







