ACME SSL Certificate
Set it up once, let ACME handle every renewal
With Sectigo's ACME support, certificate requests, domain validation, installation and renewal run on your server by themselves. Works with Certbot, acme.sh, win-acme and cert-manager.
- Full refund if validation can't be completed
- 24/7 support tickets
- Works with RFC 8555 clients
What is an ACME SSL certificate?
An ACME SSL certificate is an SSL/TLS certificate that is requested, validated, installed and renewed automatically over the ACME protocol (Automatic Certificate Management Environment). The ACME client on your server talks to the certificate authority directly: no CSR to prepare, no approval e-mail to wait for, no expiry date to track.
ACME was built for Let's Encrypt and standardised by the IETF as RFC 8555 in March 2019. Commercial certificate authorities such as Sectigo, DigiCert and GlobalSign now issue certificates over ACME too; with paid ACME, your client is tied to your account with EAB (External Account Binding) credentials.
- Place your orderAfter your order, the ACME directory URL and EAB credentials are sent to you.
- Connect your clientCertbot, acme.sh, win-acme or cert-manager registers with your account in one command.
- The domain is validatedAutomatically, via HTTP-01 on your web server or DNS-01 in your DNS zone.
- Installed and renewedThe certificate is installed; a new one is fetched before it expires.
ACME SSL plans
ACME SSL is sold as a subscription: during the subscription your ACME client keeps renewing the certificate. Since 15 March 2026, a single certificate is valid for at most 200 days.
- OV
Sectigo ACME Certificate - OV
$12.49/mo
- Organization validation (OV)
- Single domain protection
- Automatic renewal over ACME
- Client bound to your account with EAB
- HTTP-01 and DNS-01 validation
- $1,000,000 warranty
Managing many certificates, a central inventory or internal certificates? See our certificate lifecycle management options
SSL certificate lifetimes are dropping to 47 days
Under ballot SC-081, adopted by the CA/Browser Forum in April 2025, the maximum validity of publicly trusted SSL/TLS certificates shrinks step by step. The period for which a domain validation can be reused shrinks with it, down to 10 days in 2029, so renewing by hand means about eight jobs a year per certificate.
| From | Maximum validity | Domain validation reuse | Renewals per year (at least) |
|---|---|---|---|
| Until 15 March 2026 | 398 days | 398 days | 1 |
| 15 March 2026 | 200 days | 200 days | 2 |
| 15 March 2027 | 100 days | 100 days | 4 |
| 15 March 2029 | 47 days | 10 days | 8 |
For organisation-validated (OV) certificates, organisation details can be reused for at most 398 days since 15 March 2026. Source: CA/Browser Forum, Ballot SC-081v3.
HTTP-01 or DNS-01?
ACME proves that you control the domain with a challenge. Sectigo ACME uses HTTP-01 and DNS-01; there is no e-mail validation.
| Method | How it works | Wildcard | Best for |
|---|---|---|---|
| HTTP-01 | A validation file is placed on your server and read over port 80. | No | Single-server websites, cPanel and Plesk |
| DNS-01 | An _acme-challenge TXT record is added to DNS, automatically through your DNS provider's API. | Yes | Wildcard certificates, internal servers, behind a load balancer |
Give the API key you use for DNS-01 only enough rights to add TXT records, and rotate it regularly.
Connect with the ACME client you already use
Replace ACME_SERVER, EAB_KID and EAB_HMAC_KEY in the commands with the values sent to you after your order. The account is bound once; the client's scheduler handles every renewal after that.
certbot --nginx \
--server "$ACME_SERVER" \
--eab-kid "$EAB_KID" \
--eab-hmac-key "$EAB_HMAC_KEY" \
-d example.com -d www.example.comacme.sh --register-account --server "$ACME_SERVER" \
--eab-kid "$EAB_KID" --eab-hmac-key "$EAB_HMAC_KEY"
acme.sh --issue --server "$ACME_SERVER" --dns dns_cf \
-d example.com -d '*.example.com'wacs.exe --source iis --host example.com,www.example.com ^
--baseuri %ACME_SERVER% ^
--eab-key-identifier %EAB_KID% ^
--eab-key %EAB_HMAC_KEY%apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
name: sectigo-acme
spec:
acme:
server: <ACME_SERVER>
externalAccountBinding:
keyID: <EAB_KID>
keySecretRef:
name: sectigo-eab
key: secret
privateKeySecretRef:
name: sectigo-acme-account
solvers:
- http01:
ingress:
ingressClassName: nginxOther clients that support ACME v2 (RFC 8555) work too, such as lego, Posh-ACME, Certify The Web, Caddy and Traefik.
Let's Encrypt or paid ACME SSL?
Both use the same protocol, so you keep your client. The difference is what the certificate proves and who you can reach when something goes wrong.
| Feature | Let's Encrypt | Sectigo ACME SSL |
|---|---|---|
| Validation type | Domain validation (DV) only | Organisation validation (OV) available |
| Organisation name in the certificate | No | Yes, with OV |
| Account binding | Not required | To your account with EAB credentials |
| Support | Community forum | 24/7 support tickets |
| Price | Free | Subscription; price on the plan card |
Let's Encrypt stopped expiry reminder e-mails on 4 June 2025 and is cutting its default certificate lifetime to 64 days on 10 February 2027 and to 45 days on 16 February 2028. Source: Let's Encrypt.
Four rules for using ACME safely
-
Protect the account key
Keep the ACME account key and EAB credentials in a secrets vault; never write them to logs or code repositories.
-
Add a CAA record
A CAA DNS record lets only the certificate authorities you choose issue certificates for your domain (RFC 8659).
-
Renew early
Renew when about a third of the lifetime is left, and get alerted when an attempt fails.
-
Watch CT logs
Certificate Transparency logs show it when a certificate is issued for your domain without your knowledge.
ACME SSL: frequently asked questions
What people ask most before switching to ACME SSL.
- It is an SSL/TLS certificate requested, validated, installed and renewed automatically over the ACME protocol (RFC 8555). You connect your client once; every renewal after that happens on its own.
- No. ACME is an open IETF standard; commercial certificate authorities such as Sectigo, DigiCert and GlobalSign issue certificates over ACME as well.
- You keep your client: point it at the new ACME directory URL and register the account once with your EAB credentials. In Certbot that is the
--server,--eab-kidand--eab-hmac-keyoptions. - A key identifier (KID) and HMAC key that tie your ACME client to your paid account. Only clients holding them can obtain certificates on your account, so store them like a password.
- Yes; wildcard certificates are issued only with DNS-01 validation. Your client adds the TXT record through your DNS provider's API (Cloudflare, Route 53 and others).
- Yes. win-acme updates the IIS site bindings and adds renewal to Windows Task Scheduler.
- From 15 March 2029, certificates will be valid for at most 47 days and domain validation must be repeated every 10 days. That is roughly eight renewals a year per certificate; ACME does them for you.
- Your client can no longer obtain new certificates; the last one issued stays valid until its own expiry date. Renew the subscription before it ends to avoid an outage.
- No. With ACME, domain validation runs automatically over HTTP-01 or DNS-01; there is no approval e-mail to wait for.
Never see an 'expired certificate' warning again
Pick a plan, connect your client and let ACME do the renewing.