Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is the ACME Protocol?

ACME is the protocol defined in RFC 8555 that lets a server prove it controls a domain and collect, renew, and revoke TLS certificates automatically, with no human in the loop.

Illustration for the cybersecurity term ACME Protocol
Home / Blog / Cybersecurity Terms / What Is the ACME Protocol?
17 November 2026

What Is the ACME Protocol?

What Is the ACME Protocol?

ACME, the Automatic Certificate Management Environment, is the protocol a server uses to prove that it controls a domain name and then collect a TLS certificate for it without anyone filling in a form. The IETF published it as RFC 8555 in March 2019, after Let’s Encrypt had already proved the model at scale. Today it issues the majority of publicly trusted web certificates.

The appeal is simple. Certificate expiry used to be a calendar problem solved by a spreadsheet and a reminder, and the spreadsheet regularly lost. ACME turns renewal into a cron job.

How an Order Is Fulfilled

An ACME client holds an account key pair registered with the certificate authority. Every request it sends is signed with that key, so the CA knows who is asking. A single issuance runs through five steps:

  1. The client creates an order listing the identifiers it wants, for example shop.example.co.uk and www.example.co.uk.
  2. The CA returns one authorisation per identifier, each offering a choice of challenges.
  3. The client satisfies a challenge, placing a token where only the domain’s controller could place it, and tells the CA to validate.
  4. The CA checks from several network locations and marks the authorisation valid.
  5. The client sends a certificate signing request, the CA signs it, and the client downloads the chain and reloads the web server.

The Three Challenge Types

ChallengeWhat you proveBest used for
http-01You can serve a file under /.well-known/acme-challenge/ on port 80Single public web servers; the default for most clients
dns-01You can create a _acme-challenge TXT record in the zoneWildcards, internal hosts with no public port 80, load-balanced estates
tls-alpn-01You can answer a special TLS handshake on port 443Environments where port 80 is closed entirely

Only dns-01 can issue a wildcard such as *.example.co.uk, which is why many organisations end up granting an ACME client API credentials for their DNS provider. Scope those credentials to the single challenge record if the provider allows it; a token that can rewrite the whole zone is a far larger prize than the certificate it protects.

Why Automation Stopped Being Optional

Let’s Encrypt issues certificates valid for 90 days, deliberately short enough that nobody can manage them by hand. The direction of travel is shorter still. In April 2025 the CA/Browser Forum adopted a schedule that reduces the maximum lifetime of a public TLS certificate to 47 days by 15 March 2029, and Let’s Encrypt has begun offering six-day certificates. Any organisation still renewing manually has a deadline.

Shorter lifetimes also limit the damage done by a stolen private key, because revocation checking is unreliable in practice. A certificate that expires on its own in a week needs no revocation infrastructure to be trusted.

Where ACME Goes Wrong

The account key is the asset to protect. Anyone who steals it can order certificates for every domain the account has already validated, so keep it off shared file systems and out of container images. Publish a CAA record naming the CAs you use, and tighten it with the accounturi parameter so that only your own ACME account qualifies.

Domain validation is still only as strong as DNS and BGP. A route hijack that redirects validation traffic can produce a genuinely signed certificate for someone else’s domain, which is why CAs now validate from multiple vantage points and why Certificate Transparency monitoring matters: it is how you find out that a certificate you did not request exists.

ACME Inside the Perimeter

The protocol is not limited to public CAs. Smallstep’s step-ca, EJBCA, and HashiCorp Vault’s PKI engine all speak ACME, so internal services, Kubernetes ingress controllers, and device fleets can enrol against a private certificate authority using the same clients. External Account Binding ties an ACME account to an existing customer record, which commercial CAs use for paid certificates.

Popular clients differ in philosophy: Certbot and acme.sh are general purpose, lego is a Go library with wide DNS provider support, and Caddy requests and renews certificates with no configuration at all. Whichever you choose, monitor expiry independently of the client, because a renewal that silently fails looks exactly like one that worked until the morning it does not. Our infrastructure security testing services routinely find certificate automation that stopped running months earlier.

FAQ – Frequently Asked Questions

Do I Need to Pay for an ACME Certificate?

No. Let’s Encrypt, Google Trust Services, and Buypass all issue publicly trusted certificates through ACME at no cost, and they are cryptographically identical to paid ones. Commercial CAs also offer ACME endpoints for their paid products, usually with External Account Binding. What you pay for with a commercial certificate is warranty, organisation validation, or support, not stronger encryption.

Can ACME Issue Certificates for Internal Servers?

Yes, in two ways. A public CA can issue for an internal host if the name is a real domain you control and you use the dns-01 challenge, since no inbound connection is needed. Alternatively, run a private CA that speaks ACME, such as step-ca or Vault PKI, and distribute its root to your estate. Internal names that are not real domains cannot get a public certificate.

What Happens If My ACME Client Stops Renewing?

Nothing, until the certificate expires, and then every browser and API client refuses the connection. Most clients attempt renewal at one third of the remaining lifetime, giving roughly 30 days of retries on a 90-day certificate. Monitor expiry with an external check rather than trusting the client’s own logs, and alert well before the final week.

Is a 47-Day Certificate Lifetime Really Coming?

Yes. The CA/Browser Forum agreed a phased reduction in 2025: 200 days from March 2026, 100 days from March 2027, and 47 days from March 2029. Domain validation reuse shrinks alongside it. Organisations that cannot automate issuance will face renewals every few weeks, so planning the automation now is cheaper than scrambling later.

Related Terms

You May Be Interested In These

What Is Network Detection and Response (NDR)?

Cybersecurity Terms

17 November 2026

What Is Network Detection and Response (NDR)?

Read More
How Do You Build a Security Team?

Cybersecurity Terms

17 November 2026

How Do You Build a Security Team?

Read More
What Is Alert Escalation?

Cybersecurity Terms

17 November 2026

What Is Alert Escalation?

Read More