Let's assume you've already automated your public TLS certificate operations, and you did it the right way using the ACME standard wherever possible. That's good, but it can and will get better.
ACME automates certificate issuance and renewal, but traditional renewal schedules aren't designed to respond to unexpected events, such as certificates that need to be replaced early. The ACME Renewal Information (ARI) extension was created, in part, to address this limitation.
Now Google is making ARI an important part of its plans for quantum-resistant public TLS certificates. Its draft Chrome Quantum-resistant Root Program Policy emphasizes ACME and ARI support, recognizing that automation will become even more important as certificate lifetimes shrink.
When both your ACME client and certificate authority (CA) support ARI, the CA can recommend earlier renewal windows. This makes certificate management more dynamic and helps reduce the risk of unexpected outages.
The move toward 47-day public TLS certificates isn't the only change coming to the Web PKI.
In early 2026, the Chrome team announced plans to use Merkle Tree Certificates (MTCs) in its proposed quantum-resistant root program.
Why? Performance.
Post-quantum cryptography (PQC) introduces substantially larger digital signatures, which can affect TLS connection performance. MTCs address this challenge by organizing certificate information into Merkle trees.
Rather than signing every certificate individually, the CA signs cryptographic information representing the tree using a post-quantum algorithm such as ML-DSA. Smaller hash values and cryptographic proofs allow clients to verify individual certificates without transmitting a separate large signature for each one.
Google's proposed program is separate from its existing root program, but it offers a glimpse of how quantum-resistant public TLS certificates might work.
And automation is central to that vision.
The CA/Browser Forum's Baseline Requirements establish strict deadlines for certificate revocation. In certain serious circumstances, CAs must revoke affected certificates within 24 hours.
The CA/Browser Forum has also strengthened its expectations for how CAs prepare for mass certificate revocation, underscoring the need to replace large numbers of certificates quickly when problems arise.
That's not much time if your certificate automation is waiting for its next scheduled renewal.
Traditional ACME clients commonly renew certificates according to an established schedule. If a certificate must be replaced unexpectedly, that schedule may not respond quickly enough to avoid an outage.
Unless your scheduled renewal happens to fall within that window, you could find yourself dealing with an emergency.
ARI provides a better approach.
It introduces the concept of a renewal window, a period during which the CA recommends that the client renew a particular certificate.
An ARI-capable client retrieves this information and can adjust its renewal schedule accordingly. If the CA responds with a renewal window containing the current time, the client can renew immediately.
ARI doesn't guarantee that an outage won't happen. Certificate validation, issuance, and deployment can still fail. But it gives automated systems a better opportunity to respond.
ARI also benefits CAs. By distributing renewal windows over time, they can better manage demand and avoid sudden spikes in certificate operations.
As renewals become more frequent, this becomes increasingly valuable.
Google's emphasis on ARI isn't just about avoiding revocation-related outages. It's also about preparing the Web PKI for a different certificate type.
The Automation Support section of the draft Chrome Quantum-resistant Root Program Policy requires participating MTC CAs to make subscriber certificates available through an ACME-based service.
This doesn't directly require subscribers to use ACME. But as certificate lifetimes shrink, manual certificate management becomes increasingly impractical.
The policy also requires MTC CAs to support ARI, allowing subscribers to receive earlier renewal recommendations, including in response to revocation events.
Google additionally recommends support for the ACME Profiles Extension (draft-ietf-acme-profiles), which allows clients to request different certificate profiles.
That's an important advance, but out of scope here.
The larger point is that Google wants certificate management systems that can respond dynamically to changing requirements.
ARI helps make that possible.
One line in Google's draft policy is especially noteworthy:
"To evaluate whether Subscriber ACME clients reliably poll and act upon ARI signals, MTC CAs issuing Subscriber certificates with validity periods exceeding 7 days SHOULD conduct operational ARI testing."
Why seven days?
The CA/Browser Forum recognizes Short-lived Subscriber Certificates as certificates valid for seven days or less.
Their short lifetimes limit how long a compromised certificate can remain usable. The CA/B Forum Baseline Requirements make revocation support optional for these certificates. Therefore, Google won’t require ARI for them.
Short-lived certificates also reflect a broader shift in thinking about revocation. Because traditional revocation mechanisms can be difficult to operate effectively at scale, limiting a certificate's lifetime provides another way to reduce the window of exposure.
Google's proposed MTC architecture also emphasizes seven-day validity periods. For longer-lived certificates, the draft policy recommends testing whether clients respond appropriately to ARI signals.
You could choose to renew a seven-day certificate every six days. Depending on your CA and supported profiles, you might even issue certificates daily.
Once reliable automation is in place, frequent renewals become much more practical, although monitoring and deployment reliability remain essential.
This is another reason ARI matters. It supports the flexibility needed for increasingly short certificate lifetimes.
You don't need to wait for quantum-resistant certificates to prepare.
The CA/Browser Forum has already begun reducing maximum public TLS certificate lifetimes, with the limit reaching 47 days in March 2029.
If you're using ACME, that's a good start. But it's worth checking whether your automation can respond when circumstances change.
A few questions to consider:
For DigiCert customers, CertCentral provides ACME-based certificate automation to help reduce manual issuance and renewal tasks.
You'll also want to confirm ARI support for your specific CA service and ACME client, along with your ability to deploy certificates automatically.
These capabilities matter whether you're preparing for shorter certificate lifetimes, unexpected revocations, or the longer-term transition to PQC.
Once you have normal automation in place, keeping your PKI running shouldn't require a lot of work from administrators. Until something bad happens.
At such times, often involving an unexpected revocation, you need to fix the problem, and fast.
On vacation? It's Christmas Eve? PKI doesn't care.
You may have mere hours to avert a potentially expensive outage.
ARI helps by allowing your certificate automation to respond to changing renewal requirements. It won't eliminate every risk, but it can reduce the need for emergency intervention.
And as certificate lifetimes shrink and Google's quantum-resistant plans advance, that flexibility will become more valuable.
"It won't happen to me" is not a business strategy.
It could happen to you. But with reliable automation and ARI support in place, you can significantly reduce the risk.
[CTA] Take the next step with certificate automation
Using DigiCert CertCentral? Learn how to install and configure the ACME automation agent to automate certificate management.