Your CA Can Ask You to Renew Early. Is Anything Listening?
When a CA finds out it issued certificates the wrong way, it has to revoke them. The rules give it 24 hours for some problems and at most 5 days for others. That's not much time to replace a certificate, especially one somebody installed by hand.
It happens more often than you'd think. On July 29, 2024, DigiCert found a bug in how it checked domain ownership and told customers they had 24 hours to replace 83,267 certificates. Some got more time after a customer went to court. On February 29, 2020, Let's Encrypt found a bug in its CAA checks that affected 3,048,289 certificates. It revoked about 1.7 million within days and let the rest expire, because revoking them all would have broken too many sites.
Those owners were told by email, and had to read it in time.
What ARI is
ARI (ACME Renewal Information) lets a CA tell your renewal client when to renew. For each certificate it publishes a window, "renew between these two times", and the client checks it every so often. It became a standard in June 2025, as RFC 9773.
On a normal day the window just spreads renewals out so they don't all land at once. The useful part is that the CA can move it. Before a revocation, the CA can move the window into the past, and every client that checks it renews right away. Nobody has to read an email.
Who offers it
When we added ARI to CertAvert on November 5, we asked the public CAs we see most. Let's Encrypt, Google Trust Services, Sectigo and ZeroSSL answer. DigiCert and Buypass don't offer it. SSL.com lists it in its ACME directory, but every request we sent got an error.
They don't all pick the same window. On a normal day, from what we've seen:
| CA | Renew at about |
|---|---|
| Let's Encrypt | 2/3 of the lifetime |
| Google Trust Services | 60 to 75% (a one-hour window) |
| Sectigo, ZeroSSL | 85% |
On a 90-day Let's Encrypt certificate that's about 60 days in, with 30 left.
Is your client listening?
Only if it supports ARI, and only if it runs often enough to see the window move.
certbot has supported it since 4.1.0 (June 2025), and certbot renew checks it by default. lego and win-acme do too, and so does Caddy, through the ACME library it's built on. Others are partway there or not at all, so check your client's release notes rather than assuming.
The second part matters as much. A window moved up today doesn't help if your renew job runs once a week. Most clients are meant to run daily or more, and let the client decide whether to renew.
And ARI only helps certificates that renew on their own. The one copied onto a load balancer or an appliance by hand still needs a person.
What it doesn't promise
A CA can move the window before revoking. It doesn't have to. ARI is a courtesy, not a rule, so a revocation can still come without warning. It's one more chance to find out early, not a guarantee.
Where CertAvert fits
CertAvert asks the CA for each domain's window several times a day and shows it on the Expiry alerts tab. When the CA moves it up, every plan, Free included, gets one email saying which certificate, the old and new window and the CA's explanation if it gave one. It's meant for the certificates your client won't renew on its own.
Check yours
Put a domain through the free ARI tool. It shows the current renewal window from the certificate's CA, or says the CA doesn't offer one. It takes a few seconds and doesn't need an account.
Sources
- RFC 9773: ACME Renewal Information (ARI) Extension
- Let's Encrypt: ARI is now an RFC
- Mozilla Bugzilla 1910322: DigiCert, random value in CNAME without underscore prefix
- Let's Encrypt community: 2020.02.29 CAA Rechecking Bug
- Let's Encrypt community: Revoking certain certificates on March 4
- certbot changelog (4.1.0)