Let's Encrypt certificates drop to 64 days on February 10. Find the hard-coded 60 before it finds you
Most sites will sail through Let's Encrypt's move to 64-day certificates. The ones that don't will have a renewal number typed into a cron job years ago, an alert tuned for 90 days, or a certificate someone uploads by hand.

From February 10, 2027, Let's Encrypt issues 64-day certificates by default, down from 90, and cuts authorization reuse from 30 days to 10. If your ACME client supports ACME Renewal Info, you're probably fine. If renewals are hard-coded, search cron jobs, wrapper scripts and runbooks for 83, 80 or 60, switch to renewing at about two-thirds of lifetime, retune expiry alerts, and list every certificate someone still installs by hand. Staging has issued 64-day certificates since October 14, 2026, so test there first.
What's changing, and who can stop reading
On February 10, 2027, Let's Encrypt starts issuing certificates that last 64 days by default, down from 90. Every certificate issued or renewed from that date gets the shorter life. Let's Encrypt expects the last 90-day certificate to expire around May 11, 2027, and it won't revoke anything early. Its staging environment has issued 64-day certificates since October 14, 2026.
If your renewals are automated and your ACME client supports ACME Renewal Info (ARI), Let's Encrypt says you "should be all set." ARI lets the certificate authority tell your client when to renew, so the client adapts to whatever lifetime it's handed. Check your client's documentation to confirm it has ARI. If it does, the rest of this note is mostly a list of places to make sure that client is actually the one doing the work.
If you're not sure, keep reading. Let's Encrypt itself suggests a search: "Grep for common hardcoded numbers like 83, 80 or 60 in cron jobs, wrapper scripts and runbooks."
Here's what each of those numbers means, and where else they hide.
Sequence of work
The dates that matter
- Oct 14, 2026
Staging issues 64-day certificates.
- Feb 10, 2027
64-day default; authorization reuse drops to 10 days.
- May 11, 2027
Last 90-day certificate expected to expire.
- Feb 16, 2028
45-day default; reuse drops to seven hours.
Why 83, 80 and 60 break
Those numbers come from the 90-day era. They're renewal points measured from the day a certificate was issued.
- 83 days. That's a week before a 90-day expiry. On a 64-day certificate, day 83 is nearly three weeks after the certificate has already expired.
- 80 days. Same story, ten days before the old expiry and 16 days after the new one.
- 60 days. That's the classic "renew at two-thirds," and it gave a month of slack. A renewal job set to run every 60 days used to leave a month of slack. On a 64-day certificate it leaves four days. One failed run over a long weekend and the site is down.
Let's Encrypt's advice is to renew at about two-thirds of the lifetime, whatever it is. For 64 days that's around day 42 or 43. Better still, express the rule as a fraction, or let ARI decide, so you don't repeat this exercise in 2028. That's when the default drops again, to 45 days, on February 16, 2028.
Decision guide
Old renewal numbers on a 64-day certificate
| Consideration | On a 90-day certificate | On a 64-day certificate |
|---|---|---|
| Renew at day 83 | A week of slack. | 19 days after expiry |
| Renew at day 80 | Ten days of slack. | 16 days after expiry |
| Renew every 60 days | A month of slack. | Four days of slack |
| Alert under 30 days left | Rarely fires. | Fires every cycle |
A renewal job set to run every 60 days used to leave a month of slack. On a 64-day certificate it leaves four days.
Where the numbers hide
The grep is a good start, but it only finds what's in files you know about. In our experience the trouble sits in these places:
Cron jobs and systemd timers. Look for fixed schedules and for flags that say "renew if fewer than N days remain." Thirty days remaining on a 90-day certificate was relaxed. On a 64-day certificate it's fine for now, but it means renewing at day 34, and at 45 days it leaves very little room.
Wrapper scripts. The shell script someone wrote to renew, copy the files to three servers and reload nginx. It often carries its own date math, separate from the ACME client.
Monitoring thresholds. An alert that fires when a certificate has fewer than 30 days left was quiet most of the time with 90-day certificates. With 64-day certificates renewed at two-thirds, there are about 21 days left at renewal time. That alert will fire every cycle, people will learn to ignore it, and then it won't help on the day it matters. Retune it to fire when a certificate passes its expected renewal point without being renewed.
Runbooks and wikis. "Certificates renew automatically every 60 days" in a runbook is how a new engineer decides an expiry warning is nothing to worry about.
Hand-installed certificates. Load balancers, CDNs, mail servers and appliances where someone downloads a certificate and uploads it through a web console. Every one of these now needs attention about every six weeks instead of every couple of months. That's the strongest argument for automating them, and Let's Encrypt says the same: automate reload and deployment, and alert on renewal failures.
Third-party hosts. If an agency or vendor manages part of your stack, ask them directly. Don't assume.
Containers and images. A certificate baked into a container image or a machine image at build time lives as long as that image is deployed. If a service only gets rebuilt every couple of months, a 64-day certificate inside it will expire first. Certificates should be fetched at runtime or mounted from a store that renews them, not copied in.
Mobile apps that pin certificates. If one of your apps pins a specific leaf certificate rather than a public key or an issuing CA, each renewal can break it. Shorter lifetimes mean more renewals, so check how pinning is set up before February, and give app store review time to ship any fix.
The quieter change: 10-day authorization reuse
Alongside shorter certificates, Let's Encrypt is cutting the authorization reuse period from 30 days to 10. In 2028 it shrinks to seven hours.
Let's Encrypt says most people won't need to change anything "unless you have specifically designed your ACME client to rely on validation reuse." Here's how that tends to show up in real setups: someone proves control of a domain once, for example by adding a DNS record by hand, and later issuances quietly ride on that proof. With a 10-day window those later issuances will start asking for validation again. If a person has to edit DNS each time, that person is now part of your uptime.
Let's Encrypt has said it expects a new validation method, DNS-PERSIST-01, in 2026, which is meant to reduce the need for DNS changes on every renewal. Until it's available and your DNS provider and client support it, the safe answer is DNS validation automated through your provider's API.
What isn't changing: rate limits, ACME endpoints and issuance chains all stay the same.
A three-week plan before February 10
Week one: inventory. List every hostname with a public certificate, who issues it, what renews it and what deploys it. Include the hand-installed ones.
Week two: test in staging. Point one representative setup at Let's Encrypt staging, which already issues 64-day certificates, and let it renew. Watch the full path: issue, copy, reload, and alert.
Week three: fix and retune. Replace fixed day counts with ARI or a two-thirds rule, update the monitoring thresholds, and rewrite the runbook line. Then automate one of the hand-installed certificates, starting with the one whose outage would hurt most.
If you'd like a second pair of eyes on how your web application renews, deploys and monitors its certificates, our web applications team does this kind of operational cleanup. Get in touch and tell us how many hostnames you're running.
Related work: Sutton Place.
We build alongside the people doing the work.
Bring us the problem you’re thinking about.