How to add a CAA record without breaking your renewals
A CAA record is one of the cheapest hardening steps a domain owner can take: one DNS record, and every publicly trusted certificate authority must check it before issuing for your domain. But it is also one of the easiest to get wrong — authorise too few CAs and your next renewal fails; authorise the wrong issuer domain and the record does nothing at all.
This tool builds the records on your own device. When you enter a domain and pick your CAs, your browser:
- Validates everything — the domain syntax, the flag (only 0 and 128 are defined), the tag names, and the iodef email or URL — so a typo cannot become a live DNS record that blocks issuance.
- Builds one record per CA per type — issue for standard certificates, issuewild for wildcards — with optional accounturi and validationmethods parameters, and an iodef record for violation reports.
- Renders four provider formats — a BIND zone file, and field-by-field Cloudflare, Route 53 and GoDaddy layouts — so you copy what your provider actually asks for instead of translating a zone-file line by hand.
What makes this generator different
The established CAA generators — the ones run by DNS providers and SSL sellers — output a zone-file line and stop there. They assume you know how to turn that line into the fields your provider’s form wants, and they rarely explain what each record does. The other kind of page is a guide that explains CAA and links you to somebody else’s generator. This page is both: validated records, a plain-English explanation of every one, and the exact fields for the four providers most people actually use — Cloudflare, Route 53, GoDaddy and BIND — plus a checker that reads your existing records and tells you whether the CAs you picked are actually permitted. Free, fully client-side, no account, no upload, with a live network-request counter so you can verify the privacy claim yourself.
When is CAA the right choice — and when is it the wrong one?
CAA is right for any domain that serves HTTPS: it costs one DNS record and closes the door on mis-issuance from a CA you never use. It is the wrong choice as a substitute for watching Certificate Transparency logs — CAA cannot tell you about a certificate that was already issued, because browsers do not check CAA and a wrongly issued certificate still works. And it is the wrong choice for a domain whose CA set changes often: every new CA needs a new record, or issuance is refused.
Honest limitations
No live DNS lookup
The tool formats records; it never queries DNS. It cannot see your live records, confirm they published, or warn you about a record already in your zone. Verify with dig +short yourdomain CAA after adding them.
It never publishes anything
You add the records in your DNS provider’s console or zone file. A wrong record can block renewal, so double-check the CA list against your host and CDN before publishing.
CAA does not revoke anything
CAA is checked at issuance, not at connection. A certificate issued in violation still works in every browser; only Certificate Transparency logs reveal it. To deal with an already-issued certificate, revoke it at the issuing CA.
Parameters are only honoured where supported
accounturi and validationmethods are only respected by CAs that support them. A CA that does not understand a parameter ignores it — unless the critical flag is set, in which case it must refuse issuance entirely.
Issuer domains must be exact
Each CA checks for its own issuer domain (letsencrypt.org, pki.goog, sectigo.com). A near-miss — the CA’s website instead of its CAA domain — authorises nobody. The preset list uses the documented CAA domain for each CA.
Wildcards need their own record
Without an issuewild record, issue records also cover wildcards. To allow wildcards from one CA and standard certificates from another, you need explicit issuewild records — the picker builds them for you.