1. Red
  2. Learn
  3. Certificates and TLS

Let's Encrypt 64-day certificates: what to do before Feb 10

Let's Encrypt issues 64-day certificates by default from 10 February 2027. Find hardcoded 60, 80 or 83-day renewals, check ARI and DNS validation, and test in staging.

By Timothy Lindblom, FounderPublished 4 November 20268 min readHow we check facts
On this page
  1. Who has to do something?
  2. What does a fixed renewal schedule do to a 64-day certificate?
  3. How do I find hardcoded renewal numbers?
  4. What is ARI and should I turn it on?
  5. Does shorter domain validation reuse affect me?
  6. What do I ask my host?
  7. How do I test before 10 February?
  8. What about paid certificates and the 47-day rule?
  9. Where does a scan fit?
  10. What to do this week

Let's Encrypt will issue certificates valid for 64 days instead of 90 by default from 10 February 2027. If your renewal is automatic and follows the certificate's real lifetime, you probably need no change. If a script, cron job or panel renews on a fixed 60, 80 or 83-day schedule, change it now and test on the staging environment, which has issued 64-day certificates since 14 October 2026.

FactDetailSource
Announced7 October 2026Let's Encrypt
Staging switches to 64 days14 October 2026same post
Production default becomes 64 days10 February 2027same post
Domain validation reuse30 days down to 10 days on the same dateLet's Encrypt, Dec 2025
Existing 90-day certificatesNot revoked; the last is expected to expire 11 May 2027Let's Encrypt, Oct 2026
Next step45 days by default on 16 February 2028, with 7-hour reuseLet's Encrypt, Dec 2025
Checked4 November 2026this page

Not sure who runs your certificates? Start with which layers your host handles and which are yours, because the same host-or-you question applies here.

Who has to do something?

Let's Encrypt says the group that must act is anyone with non-automated or hardcoded renewal schedules. That covers three kinds of site.

  • Hosted sites with a panel that issues certificates. The host owns the schedule. Your job is to ask.
  • Self-managed servers running Certbot, acme.sh, Caddy, Traefik or a similar client. Your job is to read the renewal configuration.
  • Setups with a custom script, a deploy pipeline, or a monthly calendar reminder. These are the ones that break.

The announcement also says that unless you built your ACME client to rely on validation reuse, you will not need to change anything for the shorter reuse period. That sentence is the answer for most readers, and the sections below show how to confirm it applies to you.

What does a fixed renewal schedule do to a 64-day certificate?

It leaves little or no time to recover from a failed run. The older advice in the Let's Encrypt FAQ is to renew 90-day certificates every 60 days. That worked because it left 30 days of margin. The same number against a 64-day certificate leaves four.

Renewal ruleDays left at renewal, 90-day certDays left at renewal, 64-day cert
Fixed renewal at day 60304
Fixed renewal at day 8010Certificate expired 16 days earlier
Fixed renewal at day 837Certificate expired 19 days earlier
Certbot 4.0.0 and later: renew under one third remainingabout 30about 21
cert-manager default: two thirds through the lifetime30about 21
cPanel AutoSSL: renew within 29 days of expiry2929

The first three rows are arithmetic on the schedule. The last three come from the docs: Certbot says that as of 4.0.0 a certificate is ready for renewal when less than a third of its lifetime remains, cert-manager says renewal is by default two thirds through the duration, and cPanel says AutoSSL attempts to renew Let's Encrypt certificates that expire within 29 days. Values checked 24 October 2026. A tool that takes its timing from the certificate itself adapts. A tool with a number typed in does not.

Shorter lifetimes also shrink the retry runway. A renewal that fails silently at 90 days leaves about 30 days to notice. At 64 days it leaves about 21 on the defaults above. Expired certificates are already more common than most owners expect.

Let's Encrypt certificate lifetime timeline from October 2026 to February 2028 7 Oct 2026 Announced 14 Oct 2026 Staging at 64 days 10 Feb 2027 Production default 64 days, 10-day reuse 11 May 2027 Last 90-day cert expected to expire 16 Feb 2028 45 days, 7-hour reuse Source: Let's Encrypt announcements of 2 December 2025 and 7 October 2026. Spacing is not to scale.
The dated steps from announcement to the 45-day default. Test in the window between the first and third dot.

How do I find hardcoded renewal numbers?

Search your own configuration for the three numbers Let's Encrypt names, 60, 80 and 83. These are the operator steps. Run them on each server or in each repository that handles certificates.

  • Search cron entries and systemd timers for renewal jobs and read how often they run and what they pass.
  • Search deploy scripts, Ansible roles and CI jobs for 60, 80, 83 and 90 near words like renew, days or cert.
  • Open the renewal configuration of each ACME client and look for a fixed days-before-expiry setting.
  • Check monitoring thresholds. An alert that fires at "under 30 days left" is permanently red on a 64-day certificate that renews at about 21 days left, and an alert that fires at "under 7 days" is the only warning you get.
  • Look for calendar reminders or tickets that assume a three-month cycle.

Let's Encrypt's integration guide recommends renewing automatically when a third of the lifetime remains, which for 64 days is about 21 days. That is the pattern to copy: express the rule as a fraction of lifetime instead of a fixed number of days.

What is ARI and should I turn it on?

ARI, ACME Renewal Information, is defined in RFC 9773, published June 2025. The server returns a suggested renewal window for a specific certificate, and the client picks a time inside it. Let's Encrypt says that if your renewals are automated and your client supports ARI, you should be all set, because the server tells the client when to renew.

Let's Encrypt's integration guide recommends checking ARI for each certificate at least twice a day. Its rate limits page adds that renewals coordinated by ARI are exempt from all rate limits, which matters when a failed run tempts someone to reissue by hand. Without ARI, the limit of five certificates for the same set of names in seven days is a real constraint.

Whether your client supports ARI is a question for its documentation or release notes, and we did not verify support per client. If it does not, a fraction-of-lifetime rule is a sound fallback.

Does shorter domain validation reuse affect me?

Only if you rely on it. When Let's Encrypt validates a domain, it remembers the result for a period, called authorization reuse. On the profiles page the classic profile shows 30 days today. The October announcement confirms the cut to 10 days, and the December post dates it to 10 February 2027 and the next cut, to 7 hours, to 16 February 2028.

The people affected are those who prove control by hand, and which manual validation setups break has its own page. Examples are a person who adds a DNS TXT record once and issues several certificates over the following weeks, or a process that validates in one step and requests certificates days later. Automated HTTP or DNS challenges that run at each issuance are unaffected.

The December post also describes a new validation method, DNS-PERSIST-01, as arriving in 2026 to allow "set it once" DNS entries. It is not in production yet: Let's Encrypt staff said on 25 June 2026 that it will not deploy until an open issue in the draft is resolved, per its community forum. Plan around the 10-day reuse instead.

What do I ask my host?

If a control panel issues your certificates, send one message and keep the reply.

Do you issue my site's certificates from Let's Encrypt, and does your renewal schedule adapt to the 64-day default that starts on 10 February 2027? Please confirm whether your system uses ACME Renewal Information or a fixed number of days before expiry, and how you alert me if a renewal fails.

Also ask about any certificate you installed yourself, such as a paid or imported one. Panels usually do not renew those.

Let's Encrypt stopped sending expiry notification emails on 4 June 2025, per its upcoming features page. If you relied on those emails, you now need your own alert for each certificate. The same page lists the end of clientAuth certificates, and whether your mTLS will break is a separate check.

How do I test before 10 February?

Let's Encrypt asks subscribers to test in staging, which issued 64-day certificates from 14 October 2026. Certbot users can add the --test-cert or --dry-run flag, and the staging directory is https://acme-staging-v02.api.letsencrypt.org/directory. Staging keeps separate ACME accounts from production, so create one for testing (Certbot does this automatically).

  1. Issue a staging certificate with your real client and configuration.
  2. Read its validity dates to confirm it lasts 64 days.
  3. Trigger the renewal path and confirm it runs without a human.
  4. Break something on purpose in staging, such as a blocked challenge, and confirm your alert fires.

What about paid certificates and the 47-day rule?

The Let's Encrypt change is separate from the industry schedule, which applies to every public CA. Per the CA/Browser Forum ballot SC-081v3 and DigiCert's summary, the maximum certificate life is:

FromMaximum certificate lifetime
15 March 2026200 days
15 March 2027100 days
15 March 202947 days

Let's Encrypt is going shorter than the maximum. The Forum schedule matters to you if you buy certificates. A one-year subscription may now mean several reissues in the year, each needing validation and installation; why a one-year cert now lasts 200 days explains the first step.

Where does a scan fit?

A scan from outside sees the certificate your site serves right now, including its chain and expiry. The free scan's TLS check reads TLS protocols, weak ciphers, chain and expiry. It cannot see how the certificate will be renewed, which client holds the schedule, or whether a renewal job is healthy. Those facts sit on your server or with your host, and a passing result today says nothing about a renewal in three weeks. The five things an outside scan cannot show apply here as they do to patches. The free scan is one per domain, with no card, and a good first outside look at what is being served.

What to do this week

  • Write down every place a certificate is issued: panel, CDN, load balancer, origin server, internal tools.
  • For each, record who renews it and how that schedule is expressed.
  • Replace any fixed 60, 80 or 83-day setting with a fraction of lifetime or ARI.
  • Send the host question above for anything managed for you.
  • Test in staging before 10 February 2027 and set an alert for failed renewals.
  • Add the 16 February 2028 step to your calendar, because 45 days leaves even less room.

The wider list of what to fix from October is in the October 2026 security checklist, and the other TLS guides cover the rest of the certificate changes.

Questions people ask

Do I need to do anything about the Let's Encrypt 64-day change?

If your certificates renew automatically and nothing in your setup is hardcoded to 60, 80 or 83 days, usually not. Let's Encrypt says most users of automatic issuance will not need changes. Confirm your renewal runs and that no script assumes a 90-day certificate.

Will my existing 90-day Let's Encrypt certificate stop working on 10 February 2027?

No. Let's Encrypt says it will not revoke valid certificates as part of this change. Certificates issued before the switch keep their 90-day life, and the last one is expected to expire on 11 May 2027.

My hosting panel handles SSL. Is that my problem?

Mostly your host's. Panels that issue Let's Encrypt certificates for you must renew on a schedule that fits 64 days. Ask the host in writing whether its renewal timing changes on 10 February 2027, and whether you have any custom certificate that it does not manage.

What is ARI and do I need it?

ARI is ACME Renewal Information, a way for Let's Encrypt to tell your client when to renew each certificate. You do not strictly need it. It is the method Let's Encrypt recommends, and renewals it coordinates are exempt from rate limits.

I paid for a one-year SSL certificate. Does this affect me?

This change is about Let's Encrypt. Paid certificates follow a separate industry schedule: a 200-day maximum from 15 March 2026 and 100 days from 15 March 2027. Your subscription may run a year while each certificate lasts far less, so you may have to reissue or automate.

Sources

  1. Let's Encrypt: 64-day certificate lifetimes (Sarah Gran, 7 October 2026)The announcement. Staging 14 October 2026, production 10 February 2027, reuse 30 to 10 days. Checked 4 November 2026.
  2. Let's Encrypt: Decreasing certificate lifetimes to 45 days (2 December 2025)The full path from 90 to 64 to 45 days, with the 10-day reuse step on 10 February 2027 and the 7-hour step on 16 February 2028. Checked 4 November 2026.
  3. Let's Encrypt community forum: dns-persist-01 deployment status and timelineLatest staff post, 25 June 2026: no production deployment until an open draft issue is resolved. Checked 4 November 2026.
  4. Let's Encrypt: Profilesclassic, tlsserver and shortlived profiles with their validity and reuse values.
  5. Let's Encrypt: Integration guide, renewalCheck ARI at least twice a day; backstop renewal at one third of lifetime remaining.
  6. Let's Encrypt: Upcoming featuresDated changes, including the end of expiry emails and clientAuth issuance.
  7. Let's Encrypt: Rate limitsARI-coordinated renewals are exempt from all rate limits.
  8. Let's Encrypt: Frequently asked questionsThe older advice to renew 90-day certificates every 60 days.
  9. Let's Encrypt: Staging environmentDirectory URL and the certbot --test-cert and --dry-run flags.
  10. RFC 9773: ACME Renewal Information (ARI) ExtensionHow a server tells a client when to renew. Published June 2025.
  11. Certbot documentation: renewalFrom Certbot 4.0.0, renew when less than a third of the lifetime remains.
  12. cert-manager: Certificate resourcesDefault duration 90 days; renewal by default two thirds through the lifetime.
  13. cPanel documentation: Guide to SSLAutoSSL renews Let's Encrypt certificates that expire within 29 days.
  14. CA/Browser Forum ballot SC-081v3The industry schedule behind the shorter lifetimes, March 2026 to March 2029.
  15. DigiCert: TLS certificate lifetimes will officially reduce to 47 daysThe 200, 100 and 47-day maximums with their dates.

Facts on this page are dated and point at the primary source next to them. If a vendor status changes after the date shown, the vendor's page wins; tell us at support@run.cloud and we will update it.