ACME protocol
What is ACME protocol?
ACME, defined in RFC 8555, lets a server prove it controls a domain and receive a signed TLS certificate automatically, with no human filling out a CA request form by hand. It's what makes short-lived certificates practical, like Let's Encrypt's 90-day ones. AdminKit's SSL/TLS check can confirm the validity window of a certificate an ACME client like Let's Encrypt issued.
By AdminKit team, Netbase JSC · Updated
ACME (Automated Certificate Management Environment), defined in RFC 8555 (whose status and any later updates are tracked at the IETF Datatracker’s record for RFC 8555), is a protocol that lets a server prove it controls a domain and receive a signed TLS certificate automatically, with no human filling out a request form or exchanging files with a certificate authority by hand. A client proves domain control by completing a challenge the CA specifies, commonly either serving a specific file at a well-known HTTP path or publishing a specific DNS TXT record; once that challenge is validated, the CA issues the certificate and the client installs it, all over a scripted HTTPS API. ACME is what makes short-lived certificates practical: Let’s Encrypt, the CA that popularized it, issues certificates valid for only 90 days, which would be unworkable to renew manually at any scale but is routine when a cron job or server plugin re-runs the same ACME exchange automatically before each one expires. Certbot, the Electronic Frontier Foundation’s ACME client, is one such tool: it renews a certificate once less than a third of its lifetime remains. AdminKit’s guide on how to avoid an expired TLS certificate outage covers automating renewal and checking that it worked.
AdminKit groups aCME protocol under its machine protocols cluster — browse the AdminKit glossary index for other related terms.
Frequently asked questions
How does a server prove domain control to an ACME CA?
By completing a challenge the CA specifies, commonly either serving a specific file at a well-known HTTP path or publishing a specific DNS TXT record. Once validated, the CA issues the certificate and the client installs it over a scripted HTTPS API.
Why does ACME make short-lived certificates practical?
Because the whole issuance process is automated end to end, a cron job or server plugin can re-run the same ACME exchange automatically before each certificate expires -- routine automation that would be unworkable to do manually at any scale.
How long do Let's Encrypt's ACME-issued certificates last?
90 days -- short enough that manual renewal at scale would be unworkable, which is exactly the gap ACME's automation is designed to close.
Does ACME require a human to fill out a request form?
No -- that's the point of the protocol: a server proves it controls a domain and receives a signed certificate automatically, with no human filling out a request form or exchanging files with a CA by hand.