Let's Encrypt Goes to 64-Day Certificates: When Does Your ACME Client Actually Renew?
Comments on “Let's Encrypt Goes to 64-Day Certificates: When Does Your ACME Client Actually Renew?”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Let's Encrypt's staging environment began issuing 64-day certificates on 14 October 2026, ahead of the production default on 10 February 2027 and 45 days in 2028. DevOps Daily tested five ACME client installs. Clients using ARI (certbot 5.8, acme.sh 3.1.6, lego 5.5.2) renewed around day 42 of 64, the same two-thirds share as at 45 and 90 days. acme.sh 3.0.7 scheduled renewal at day 59, or day 79 with --days 80, after expiry. Upgrading fixed it. The test used staging and one certificate per setup.
Why it ranked
No. 7 of 43 with a score of 0.66. The panel rated it highest on substantiated (0.93) and new information (0.93), lowest on audience breadth (0.61). Older work: a freshness penalty of 0.100. Placed No. 7, No. 9 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- Measured, reproducible tests of how major ACME clients handle Let's Encrypt's 64-day certificates, with a concrete acme.sh 3.0.7 failure and clear remediation steps. Strong technical depth and practical value for anyone running certificate renewal.
- AI judgeJudge 3gpt-5.6-luna
- A detailed, reproducible comparison of ACME clients under shorter certificate lifetimes, with source inspection, measured staging results, concrete failure modes, and actionable migration guidance.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.66total under rubric v2.3
- Significance0.66
- Reader interest0.80
- Audience breadth0.61
- Practical relevance0.91
- Substantiated0.93
- Technical depth0.91
- New information0.93
- Counts against: Promotional0.05
- Counts against: Overclaim0.13
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.63 | 0.62 | 0.72 | 0.66 | 0.10 | +0.24 | +0.157 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.69 | 0.80 | 0.90 | 0.80 | 0.21 | +0.26 | +0.207 |
| Audience breadthHow many people who build technology does it concern? | 0.55 | 0.67 | 0.62 | 0.61 | 0.12 | +0.13 | +0.080 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.92 | 0.90 | 0.90 | 0.91 | 0.01 | +0.22 | +0.199 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.98 | 0.88 | 0.94 | 0.93 | 0.10 | +0.05 | +0.047 |
| Technical depthHow technically substantive is it? | 1.00 | 0.90 | 0.82 | 0.91 | 0.18 | +0.05 | +0.045 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.91 | 0.90 | 0.98 | 0.93 | 0.08 | +0.05 | +0.047 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.05 | 0.08 | 0.03 | 0.05 | 0.05 | −0.19 | −0.010 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.20 | 0.15 | 0.05 | 0.13 | 0.15 | −0.11 | −0.015 |
| Sum of contributions | +0.757 | ||||||
| Freshness penalty | −0.100 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.657 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested. The freshness penalty is for older work: this one was first published 15 Oct 2026.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-02/7/"><img src="https://rubric.hrih.si/badge/2026-11-02/7.svg" alt="Ranked #7 on Rubric, 2 Nov 2026" width="231" height="28"></a>Claim check
Claim check: 4 matches source · 4 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Matches sourceDate
Let's Encrypt will issue 64-day certificates by default from 10 February 2027, down from 90 days, on the way to 45 days in 2028.
The cited source says the same thing.
The article says “Let's Encrypt will issue 64-day certificates by default from 10 February 2027, down from 90, on the way to 45 days in 2028”
The source says “On February 10, 2027, all Let’s Encrypt subscribers will move to certificates with 64 day lifetimes by default unless they select an even shorter lifetime”
Source cited by the article: letsencrypt.org/2026/10/07/64-day-certs
Matches sourceDate
Let's Encrypt's staging environment switched to 64-day certificates on 14 October 2026.
The cited source says the same thing.
The article says “14 October 2026: staging switches to 64-day certificates”
The source says “We will switch to issuing 64 day certificates in our staging environment on October 14, 2026 to enable testing”
Source cited by the article: letsencrypt.org/2026/10/07/64-day-certs
No source givenNumber
Let's Encrypt's ARI endpoint suggested renewing 64-day staging certificates between day 42.04 and 43.32, which is 65.7 to 67.7 percent of the lifetime, the same share measured at 45 and 90 days.
The article gives no link or citation for it.
The article says “Let's Encrypt's ARI endpoint suggested renewing between day 42.04 and 43.32, 65.7 to 67.7 percent of the lifetime”
The source says No source to compare with.
Matches sourceVersion
certbot added ARI support in version 4.1.0, released in June 2025.
The cited source says the same thing.
The article says “certbot added ARI support in version 4.1.0 (June 2025”
The source says “Certbot 4.1.0 has just been released. The changelog for the release is: #### Added - ACME Renewal Info (ARI) support”
Source cited by the article: community.letsencrypt.org/t/certbot-4-1-0-release/238369
No source givenNumber
acme.sh 3.0.7 scheduled a 64-day certificate for renewal on day 59 with its default settings, five days before expiry, and on day 79 with --days 80, fifteen days after expiry.
The article gives no link or citation for it.
The article says “version 3.0.7 scheduled a 64-day certificate for day 59 with its defaults, five days before it expires, and for day 79 with --days 80, fifteen days after it expired”
The source says No source to compare with.
No source givenNumber
certbot 2.9, installed by apt on Ubuntu 24.04, does not use ARI and became due 30 days before expiry, at day 34 of 64.
The article gives no link or citation for it.
The article says “certbot 2.9, the version apt installed on our Ubuntu 24.04 machine, does not use ARI and became due 30 days before expiry: day 34 of 64”
The source says No source to compare with.
Matches sourceNumber
Let's Encrypt's authorization reuse period drops from 30 days to 10 days, and to seven hours in 2028.
The cited source says the same thing.
The article says “The authorization reuse period drops from 30 days to 10 days, and to seven hours in 2028”
The source says “We will also be reducing the authorization reuse period from 30 days to 10 days. In 2028, the reuse period will shrink to seven hours”
Source cited by the article: letsencrypt.org/2026/10/07/64-day-certs
No source givenCausal conclusion
Upgrading to acme.sh 3.1.6 moved an existing stored schedule of day 79 to day 42 at the next renewal check.
The article gives no link or citation for it.
The article says “Upgrading to 3.1.6 moved that schedule to day 42 at the next check”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN —
Recorded for context only, checked 2 Nov 2026, 05:46 UTC. It played no part in the ranking.