Let the CA tell you when to renew
Most renewal automation is a cron job that fires at thirty days before expiry because someone picked thirty. The certificate authority knows better than your cron job when a certificate should be renewed, and since 2025 there is a standard way for it to tell you.
The problem with a fixed schedule
A fixed renewal offset has two failure modes. It is wrong for the certificate: thirty days before expiry is early for a 47-day certificate and late for a two-year one. And it is deaf to the authority: when a CA discovers it must revoke a batch of certificates early, because of a validation bug or a compromised intermediate, every client on a fixed schedule keeps waiting for its date while the certificates it holds are about to stop working.
What ARI is
ACME Renewal Information adds one resource to ACME. For each certificate, identified by its issuer key and serial, the authority publishes a suggested window: a start and an end time between which the client should renew, and optionally a link explaining why.1 The client checks the window on a schedule the server sets with a retry hint, and renews at a random time inside the window. In the normal case the window sits around two-thirds of the way through the lifetime. In an incident the authority moves it to now, and every conforming client renews within hours instead of waiting for a revocation many clients never check.1
What Let's Encrypt does with it
Let's Encrypt asks clients to check renewal information for each certificate at least twice a day and to renew when the window opens, keeping the one-third-of-lifetime rule only as a fallback.2 It also removes the main reason people fear renewing early: renewals made through ARI are exempt from its rate limits.3 Most maintained ACME clients already support it.
What to do
- Use a client that reads ARI, and confirm it against the authority's directory, which advertises the endpoint.
- Keep a fallback for authorities that do not publish it: renew with a third of the lifetime left, expressed as a fraction, never as a number of days.
- Serve ARI from your own authority. If you run a private ACME CA, your clients deserve the same instruction, and it is the only clean way to rotate everything early after an internal incident.
- Watch the posture. Publishing a window is worthless if the scheduler on your side never reads it. Make "did the renewal follow the window" a thing you can see.
trstctl does both ends. Its ACME server publishes renewal information for the certificates it issues, and its scheduler reads the window from Let's Encrypt for the certificates it gets there so renewal timing follows the CA's advice rather than a fixed cron. An operator route reports, per certificate, what is being published and whether the scheduler consumed it.4
The issuance page covers ARI on the server side and the posture report, and the ACME page the client side.
Sources
- IETF, RFC 9773: ACME Renewal Information (ARI) Extension.
- Let's Encrypt, Integration Guide, "When to renew": check ARI at least twice a day; renew at one-third remaining as the fallback.
- Let's Encrypt, Rate Limits: renewals made through ARI are exempt from all rate limits.
- trstctl documentation, Issuance and CAs, "Telling clients when to renew: ARI"; Lifecycle: renewal timing follows the authority's window.