Updated 2 Nov 2026: Add independently measured 64-day staging renewal timing for five ACME client installs; document acme.sh 3.0.7 --days 80 post-expiry failure and safe tested ARI/default behaviour. Existing publication unchanged.

Key details

  1. October 7, 2026: Let's Encrypt publishes a concrete 64-day transition and testing notice.
  2. October 14, 2026: 64-day default issuance begins in staging.
  3. February 10, 2027: default classic-profile issuance and renewal drops from 90 to 64 days.
  4. May 11, 2027: Let's Encrypt expects the last pre-cutover 90-day certificate to expire.
  5. Authorization reuse shrinks from 30 days to 10 days, then seven hours in 2028.
  6. ARI-aware clients receive renewal timing; custom scripts should renew at about two-thirds of the certificate lifetime.
  7. No change to ACME endpoints, issuance chains or published rate limits.
  8. Independent October 15 tests measured five ACME client installs against 64-, 45- and 90-day lifetimes; methodology and artefacts were published.
  9. On 64-day staging certificates, ARI suggested renewal on days 42.04–43.32.
  10. acme.sh 3.0.7 with --days 80 scheduled renewal on day 79.04, 15 days after certificate expiry; default --days 60 scheduled day 59.04.
  11. In tested defaults, certbot 5.8, acme.sh 3.1.6 and lego 5.5.2 followed roughly day 42–43; certbot 2.9 renewed earlier around day 34.

What builders should take away

  1. Inventory certificate issuance and renewal paths, including third-party appliances, CI jobs, DNS hooks and hosting panels.
  2. Use the October 14 staging cutover to test the complete issuance, install and service-reload sequence.
  3. Replace fixed 60/80/83-day timers with ARI-aware clients or renewal based on certificate lifetime.
  4. Monitor expiry dates and alert independently of renewal jobs.
  5. If your custom ACME client reuses prior authorizations, test behavior with the 10-day reuse window.
  6. Audit acme.sh version and stored --days settings, not only the frequency of cron or systemd renewal runs; a frequent timer can still skip an internally deferred renewal.
  7. Use Let's Encrypt staging to reproduce a 64-day renewal with the exact client, deploy hooks and configuration you operate.

What changed

Let's Encrypt confirmed on October 7, 2026 that certificates issued or renewed under its default classic profile from February 10, 2027 will be valid for 64 days instead of 90. The staging environment will issue 64-day certificates from October 14, 2026 for testing. Existing 90-day certificates remain valid and are not revoked; the last are expected to expire May 11, 2027. The authorization reuse window also falls from 30 days to 10 days. A further move to 45-day default certificates and a seven-hour authorization reuse period is planned for 2028. An independent October 15 staging investigation tested five ACME client installs against 64-, 45- and 90-day certificate lifetimes. The tests found that modern ARI-capable certbot 5.8, acme.sh 3.1.6 and lego 5.5.2 renewed or became eligible around two-thirds of the 64-day lifetime (about day 42–43), while apt-packaged certbot 2.9 without ARI renewed around day 34 and remained safe. Old acme.sh 3.0.7 scheduled its default 60-day renewal around day 59 (only five days before expiry), and a configured --days 80 scheduled around day 79, fifteen days after expiry. The tester published methodology, measurements and reproducible artefacts. This is a limited version-and-configuration test, not a universal certification of every ACME deployment.

Why it matters

The shift is an infrastructure compatibility test disguised as a shorter expiration date. Standard ACME clients that support ACME Renewal Information (ARI) can receive renewal timing guidance from Let's Encrypt, but custom cron jobs, appliance integrations and scripts that renew on a fixed calendar or wait until a certificate is nearly 90 days old can fail silently. The consequence is expired TLS and downtime, not merely more frequent certificate orders. Operators can test in staging in October rather than discovering the issue in February. The staging measurements turn a generic warning about hardcoded renewal days into a reproducible failure case: acme.sh 3.0.7 with --days 80 can let a 64-day certificate expire before its next planned renewal. Operators should check installed client versions, stored renewal parameters, cron/systemd timers, ACME Renewal Information support and deploy hooks before the February change. Certbot 2.9's lack of ARI did not cause expiry in the tested default configuration; it renewed earlier. Do not generalise these results to untested clients or wrappers.

Staging changes in October, production in February

The October 14 staging switch allows certificate managers and hosting providers to validate renewal and deployment behavior ahead of the February 10 default change. Production issuance and renewals from that date will have 64-day validity; no mass revocation is planned.

ARI clients should be fine; fixed-day cron jobs are the risk

Let's Encrypt says ACME Renewal Info-compatible clients should handle the change. For custom automation it recommends renewal at approximately two-thirds of the certificate lifetime, not on a fixed date. Check cron, scripts and runbooks for hard-coded 83-, 80- or 60-day assumptions. Renewal must also deploy the certificate and reload the relevant service.

Authorization reuse is shrinking too

The CA will reduce authorization reuse from 30 days to 10 days with the February change, then to seven hours in 2028. This matters mainly to custom ACME integrations that cache prior domain-validation state; routine ACME clients generally should not require a change.

No new issuance chains or rate-limit changes

Let's Encrypt says ACME endpoints and certificate chains are unchanged, and existing rate limits are unaffected. Its February 2026 rate-limit guidance explains that qualifying renewals remain exempt from new-order limits, so increased renewal frequency does not itself imply new rate-limit pressure.

Independent staging tests show the risky combinations

DevOps Daily issued staging certificates with five ACME client installs and measured renewal decisions at 64, 45 and 90 days. With 64-day certificates, ARI's suggested window was day 42.04–43.32; certbot 5.8 renewed at day 42.50, acme.sh 3.1.6 scheduled day 42.16 and lego 5.5.2 allowed renewal from day 42.67. Certbot 2.9 from Ubuntu 24.04 apt did not use ARI but renewed around day 34, leaving roughly 30 days. In contrast, acme.sh 3.0.7 default --days 60 scheduled day 59.04 and --days 80 scheduled day 79.04, fifteen days after expiry. The test author notes some 45-day cases used copied state or source rather than directly issued certificates, so operators should read the methodology before generalising.

Check the stored schedule, not just the cron frequency

A daily cron does not help if the ACME client internally decides the certificate is not due until day 79. Inspect renewal configuration and wrapper scripts for --days 60/80, fixed 83-day thresholds and stale acme.sh installations. Update the client, test staging renewal and ensure certificate deployment hooks reload the serving application. The tests indicate acme.sh 3.1.6 follows the ARI window; they do not prove every configuration is safe.

What to watch next

  • Whether common hosting panels and older ACME clients ship fixes before February 10.
  • Whether operators report staging incompatibilities after October 14.
  • Whether Let's Encrypt adjusts the 2028 45-day rollout details.
  • Whether operators report expiry incidents from older acme.sh configurations after February 10, 2027.

Still unclear

  • Impact depends on the ACME client and custom automation; modern ARI-compatible setups may need no action.
  • The 2028 shorter-lifetime stage remains a future scheduled transition.
  • The five-client staging test does not establish behaviour for every client, plugin, certificate profile or modified renewal script.

Sources

Direct reading behind this dossier.

4 sources

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment