Built for Monero · Login = a 16-digit number, no email · .com $12.49/year, same price every year
Language: English
Search a domain

Guide · checked 16 November 2026

How do I add a CAA record to a domain?

Last updated: · 5 min read

Quick answer

How do I add a CAA record to a domain?

To add a CAA record to a domain at Shroudname, open the DNS tab, click Add record, choose CAA, keep @ as the name and Flags at 0, pick the tag issue and type the certificate authority, such as letsencrypt.org, then click Add and Save changes. From then on, only the authorities you list may issue certificates for it.

In brief
  • What it does: tells certificate authorities which of them may issue certificates for the domain (RFC 8659).
  • Three tags: issue for normal certificates, issuewild for wildcards, iodef for where to report a refused request.
  • Mandatory check: public certificate authorities must look up CAA before issuing, a CA/Browser Forum rule since September 2017.
  • Sub-domains inherit the record of the domain unless they have their own.
  • List every issuer you use, or the missing one will be refused at the next renewal.

What are the steps in the DNS tab?

Six steps for an issue record with Let's Encrypt; repeat step 4 for each other authority you use.

  1. List the authorities you use

    Check which certificate authorities issue for the domain today: the host, the CDN, any mail or forwarding service with HTTPS. Public certificate logs show past issuers.

  2. Open the DNS tab

    In My domains, click Manage on the domain, then DNS, and click Add record.

  3. Choose CAA, name @, Flags 0

    In Type, choose CAA. Keep @ for the domain and all its sub-domains. Leave Flags on 0 — normal; 128 marks the record critical.

  4. Pick the tag and the authority

    In Tag, choose issue — may issue certificates. In Certificate authority, type the CA's identifier, letsencrypt.org for Let's Encrypt. Click Add.

  5. Optional: issuewild and iodef

    Add issuewild if wildcards follow a different rule, and iodef with a mailto: or https: address to receive reports of refused requests.

  6. Click Save changes and check

    Save, then run dig CAA example.com. The answer should list each record exactly as entered.

What does each CAA tag do?

A CAA record has three parts after the name: flags, a tag and a value; the tag decides what the value means.

CAA record tags accepted in Shroudname's DNS editor, with example values (RFC 8659)
TagMeaningExample valueNote
issueThis CA may issue certificatesletsencrypt.orgOne record per allowed CA
issuewildThis CA may issue wildcard certificatesletsencrypt.orgOverrides issue for wildcards only
iodefWhere to report a refused requestmailto:[email protected]mailto: or https: address
issue with ;Nobody may issue;Blocks all issuance, for a domain with no HTTPS

Why add a CAA record at all?

Without a CAA record, any public certificate authority may issue a certificate for the domain once its own checks pass; with one, all but the listed authorities must refuse. That narrows the ways a certificate could be obtained for your name by someone who is not you.

The CA/Browser Forum made the CAA check mandatory for public authorities in September 2017, and RFC 8659 defines the record in its current form. Let's Encrypt documents an extra parameter, accounturi, which ties issuance to one ACME account (RFC 8657), and validationmethods, which can limit it to DNS-01, for example.

CAA works best alongside two other layers: signed DNS answers, as in how to enable DNSSEC on my domain, and an account protected by two-factor codes. So how to add a CAA record to a domain is one step of a short security checklist, not the whole of it.

What breaks if a CAA record is wrong?

The next certificate from an authority you forgot to list is refused, often at an automatic renewal months later, and the site then shows a certificate error. The record itself changes nothing until a certificate is requested.

Cases to check before saving:

  • A CDN or host that uses its own authority for edge certificates.
  • HTTPS web forwarding: the certificate for a forwarded name is issued for you; see how to forward a domain to another URL, and ask support which issuer to allow before you restrict.
  • Sub-domains run by another team or service, which inherit the record from @.

If a renewal fails, add the missing issue record and retry; the record takes effect as soon as the CA reads it.

Which domains need a CAA record most in 2026?

Domains that carry logins, payments or brand trust need it most; for a parked name with no HTTPS, a single issue ; record that forbids all issuance is the tidy choice. Extensions such as .app and .dev are on the HSTS preload list, so their sites only load over HTTPS, and the certificate chain matters from day one.

According to Shroudname's survey of 12 November 2026, a .app renews for $15.99 at Shroudname against $22.68 on average at Namecheap, Dynadot, GoDaddy, Cloudflare and Njalla; the .app page has the details. A service asking you to prove control of the name first will want a TXT record, covered in how to verify domain ownership with a TXT record. Whatever the extension, how to add a CAA record to a domain takes the same six steps.

Frequently asked questions

What value do I use for Let's Encrypt?

letsencrypt.org, with the tag issue (and issuewild if you want wildcards handled separately), as Let's Encrypt's documentation states.

Should I set Flags to 128?

Usually not. 128 marks the record critical, so an authority that does not understand a tag must refuse; 0 is the normal value.

Do sub-domains need their own CAA record?

No. A sub-domain without its own CAA record follows the closest parent that has one, so a record on @ covers the whole domain.

Can I allow two certificate authorities?

Yes. Add one issue record per authority; each listed authority may then issue.

Does a CAA record affect existing certificates?

No. It is checked only when a certificate is issued or renewed; certificates already issued stay valid until they expire.

Verdict
  • CAA on @, flags 0, issue plus the authority, Save changes: six steps, and only the listed authorities can issue.
  • List every issuer first: a forgotten one fails at the next renewal, not today.
Sources (4)
  1. RFC 8659: DNS Certification Authority Authorization (CAA) Resource Record — IETF (read 2026-11-16)
  2. Certificate Authority Authorization (CAA) — Let's Encrypt (read 2026-11-16)
  3. RFC 8657: CAA Record Extensions for Account URI and ACME Method Binding — IETF (read 2026-11-16)
  4. Ballot 187: Make CAA Checking Mandatory — CA/Browser Forum (read 2026-11-16)

Lock down certificate issuance

CAA records with issue, issuewild and iodef tags, free in the DNS tab of every domain.

.com $12.49/year · XMR · no email

Search a domain