Let's Encrypt cuts certificates to 64 days: hard-coded renewals break

My take: Shorter certificates are better security, as long as no renewal depends on a fixed number of days. Hunt those down before February 10, 2027.
What to know
- On October 7, 2026, Let's Encrypt, the free certificate authority, announced that every certificate it issues or renews from February 10, 2027 will last 64 days instead of 90, unless you pick a shorter one (45 or 6 days). Valid certificates are not revoked: the last 90-day ones expire around May 11, 2027. In 2028, the default drops to 45 days, as announced earlier.
- Authorization reuse, the time a successful domain check counts for new certificates, goes from 30 days to 10.
- The staging environment, made for testing, has issued 64-day certificates since October 14, 2026.
- Clients that support ARI (ACME Renewal Information: the authority tells the client when to renew) adapt on their own; Certbot does from version 4.1.0, Caddy from 2.8.0. A renewal pinned to a number of days is what breaks: a job that renews every 80 days lets a 64-day certificate expire. Let's Encrypt advises renewing at about two-thirds of the lifetime, and searching cron jobs, scripts and runbooks for 83, 80 or 60 days.
Spotted in Self-Host Weekly.
What changes
On a Synology NAS, DSM renews its Let's Encrypt certificates on its own "before the certificates expire", its help says, without saying when. After February 10, 2027, check the expiry date under Control Panel, Security, Certificate.
Tailscale's HTTPS certificates also come from Let's Encrypt. tailscale serve, used in my Vaultwarden guide, provisions its certificate itself; one made by hand with tailscale cert is yours to renew, Tailscale says.
For everything else: update your ACME client, grep for 60, 80 and 83, and point a test at staging before February 10, 2027.
Source: Sarah Gran, Let's Encrypt, “64-Day Certificate Lifetimes Coming Feb 2027”, October 7, 2026
Drafted with Claude, Anthropic's AI, from my take. Reviewed and owned by me.