Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
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.

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.
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:
shop.example.co.uk and www.example.co.uk.| Challenge | What you prove | Best used for |
|---|---|---|
http-01 | You can serve a file under /.well-known/acme-challenge/ on port 80 | Single public web servers; the default for most clients |
dns-01 | You can create a _acme-challenge TXT record in the zone | Wildcards, internal hosts with no public port 80, load-balanced estates |
tls-alpn-01 | You can answer a special TLS handshake on port 443 | Environments 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.
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.
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.
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.
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.
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.
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.
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.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.