Opens in a new tab

Let’s Encrypt: its CAA record, ACME, and what changed

The free, automated authority behind most of the web’s certificates, and the one most hosts use: Netlify, Vercel, GitHub Pages, Squarespace, WordPress.com, cPanel’s AutoSSL and, among others, Cloudflare. Its CAA value is letsencrypt.org, and it honours the parameters that tie a record to one ACME account.

Run byInternet Security Research Group (ISRG), a US non-profit
CAA valueletsencrypt.org
CAA parametersaccounturi (your ACME account URL) and validationmethods (http-01, dns-01, tls-alpn-01)
ACMEhttps://acme-v02.api.letsencrypt.org/directory
CostFree
CertificatesDomain validated (DV) only — for names and, since January 2026, IP addresses. Wildcards need DNS validation.
Longest certificate90 days by default; 45 days in its tlsserver profile and 160 hours (just over six days) in shortlived. The default falls to 64 days on 10 February 2027 and 45 days on 16 February 2028.
Issuer names on its certificatesYE1, YE2, YR1, YR2, R10–R14, E5–E9
Issues forNetlify, Vercel, GitHub Pages, Squarespace, WordPress.com, Heroku, Fly.io and cPanel’s AutoSSL; one of the authorities Cloudflare, Shopify, Google Cloud, Render and Fastly use

May Let’s Encrypt issue for your domain?

Enter a domain or hostname: we read its CAA records as Let’s Encrypt must — its own, or the nearest parent’s — and say whether they let it issue, for wildcards too, and which authority issued the certificate it serves now.

The CAA record for Let’s Encrypt

Published on your domain, this lets Let’s Encrypt issue for it and for every name under it that has no CAA records of its own. Every authority not named must refuse. Keep the records for any other authority you use — your host’s or CDN’s included.

example.com.  CAA  0 issue "letsencrypt.org"

An issue record covers wildcard certificates too. To let Let’s Encrypt issue wildcards and no one else, add an issuewild record — once there is one, issue records stop counting for wildcards — and an iodef address for authorities to report refused requests to:

example.com.  CAA  0 issuewild "letsencrypt.org"
example.com.  CAA  0 iodef "mailto:security@example.com"

To let only your own ACME account use it, and only by DNS validation, add the account URL your ACME client shows. Anyone else’s request for the domain is then refused, even through Let’s Encrypt:

example.com.  CAA  0 issue "letsencrypt.org; accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/1234567890; validationmethods=dns-01"

How it reads CAA

It climbs from the name to its parents and stops at the first that has CAA records, following CNAMEs on the way. A lookup that fails at or below the name whose records decide stops issuance.

It compares its name letter for letter: letsencrypt.org works, LetsEncrypt.org and a trailing dot do not. It reads flag 1 as critical as well as 128, because so many records use it that way — an unknown tag written with flag 1 stops it too.

Getting a certificate

Through an ACME client — Certbot, acme.sh, Caddy, or your host’s own — with no account to sign up for and no key to paste. Rate limits allow 50 certificates per registered domain per week and 5 identical ones; renewals are exempt from the limits on new certificates.

When a CAA record stops it

When a CAA record stops it, the ACME error (type caa) reads “CAA record for example.com prevents issuance”, naming the name whose records decided. When the lookup itself fails it reads “While processing CAA for example.com: …” with the DNS error — usually a broken DNSSEC signature or nameservers that do not answer CAA queries.

What changed

  • 4 June 2025 — Stopped sending expiry reminder emails, and deleted the addresses it held.
  • 6 August 2025 — Switched off OCSP: revocation is published in CRLs only.
  • 15 January 2026 — Six-day certificates (the shortlived profile) and certificates for IP addresses opened to everyone.
  • 11 February 2026 — Dropped TLS client authentication from its default certificates; the tlsclient profile closed on 8 July 2026.
  • May 2026 — Moved issuance to its new Gen Y intermediates — YE1 and YE2 (ECDSA), YR1 and YR2 (RSA) — and cut the tlsserver profile to 45 days. R10–R14 and E5–E9 stay valid until March 2027 on older certificates.
  • 10 February 2027 — Planned: default certificates fall to 64 days, and to 45 days on 16 February 2028.

Worth knowing

  • Hosts that use it often add accounturi with their own account — Netlify’s documentation shows one. Leave that parameter out unless you run the ACME client yourself.
  • Its roots are ISRG Root X1 and X2; the new Root YE and Root YR are cross-signed by them.

Questions

Do I need a CAA record to use Let’s Encrypt?

No. Without CAA records any authority may issue, Let’s Encrypt included. You need one naming letsencrypt.org only if the domain already has CAA records — then every authority not named, Let’s Encrypt included, is refused.

Why does my host’s certificate fail although my record names letsencrypt.org?

Usually because the host uses another authority too — Cloudflare, Shopify and Google Cloud switch between several — or because an issuewild record without letsencrypt.org governs a wildcard. The check above shows which authority issued the certificate you serve now.

Sources

Checked on 27 September 2026 against these official sources:

Hear about it before the certificate expires

Add your domain and we check its certificate every day, and email you 30, 14, 7 and 1 days before it expires — in time to find a renewal that a CAA record or a changed host has stopped. Free for three domains.

Create a free account