Decide who may issue certificates for your domain.

Pick your certificate authorities and get correct CAA records in BIND, Cloudflare, Route 53 and GoDaddy formats — validated, explained in plain English, and ready to paste into your DNS. Checked entirely on your device.

  • Your domain never leaves the device
  • 4 provider formats · copy buttons
  • Validation + plain-English explanations
  • Existing-records checker included

Generate your CAA records

Just the domain — no https://, no path.
60–86400. 3600 (1 hour) is a good default.

Which certificate authorities may issue?

Tick a CA, then choose Standard (any certificate) and/or Wildcard (*.example.com). Every CA you actually use — including your host’s or CDN’s — must be listed, or renewal will fail.

The issuer domain the CA checks for — not its website. Find it in the CA’s CAA documentation.
Applies to the custom CAs above:
Optional. CAs report here if issuance is requested and refused.
An email address, or a full https:// URL that accepts reports.
Restricts issuance to one ACME account. Only CAs that support accounturi honour it.
Allowed validation methods (optional):
Try a sample:
Enter a domain and pick your certificate authorities, then press Generate CAA records. Everything stays on this device. Records download instantly.

Check your existing CAA records

Already have CAA records? Paste them below — one per line, as shown by dig +short yourdomain CAA — and this checks whether the CAs you picked above are actually permitted. It reads only the text you paste; it never queries DNS.

Uses the CAs ticked in the picker above. Nothing is uploaded — the check runs in your browser.

Privacy you can verify, not just trust

Your domain is yours — which CAs you use says something about your infrastructure. Sending it to a hosted generator means handing that to a stranger’s server. This one can’t: your domain and choices are processed entirely in your browser. Your data never leaves the device — the only third-party requests are the site’s own analytics, which count page views — and it uploads nothing, ever. There is no DNS lookup and no file fetched after load for the generation itself. Don’t take our word for it:

New cross-origin requests during use: 0
  1. Press F12 to open developer tools, then the Network tab.
  2. Generate records above. Watch: apart from the site’s analytics, nothing new is requested — no uploads, and no domain data ever leaves your device.
  3. Extra credit: disconnect your internet after this page loads — generating still works.

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:

  1. 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.
  2. 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.
  3. 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.

Frequently asked questions

Does my domain leave my device?

No. Your domain and choices are processed entirely in your browser — your data never leaves the device, and the only third-party requests are the site’s own analytics, which count page views. You can verify it yourself with the network-request counter in the privacy section below the generator. The tool never queries DNS and never publishes anything.

What is a CAA record and why should I add one?

A CAA (Certification Authority Authorisation) record tells every publicly trusted certificate authority which issuers may issue certificates for your domain. Since 2017, CAs must check CAA before issuing and refuse where the record does not permit them. Without a CAA record, any CA in the world may issue for your domain — so a compromised or mistaken validation at a CA you never use could still produce a valid certificate for your site.

Which certificate authorities should I authorise?

Every CA you actually get certificates from — including any used by your hosting provider, CDN or managed platform — plus any CA you plan to move to. Authorising too few is the common mistake: if the CA you use is not listed, issuance is refused and your renewal fails. Authorising too many weakens the control. If you are unsure, check your current certificate or your host’s documentation before publishing.

What does flag 128 (issuer critical) do?

Flag 128 marks a record as critical: a CA that does not understand the record’s tag or parameters must refuse to issue rather than ignore the record. Flag 0 means the opposite — a CA may ignore a record it does not understand. Use 128 only when you are sure your CAs support every parameter you set (accounturi and validationmethods); otherwise a CA that does not understand a parameter will refuse issuance entirely.

What is iodef for?

iodef tells certificate authorities where to report a policy violation — for example, if someone requests a certificate for your domain and the request is refused because of your CAA policy. The value is a mailto: email address (such as mailto:[email protected]) or an https:// URL that accepts reports. It is optional, but it is the only way you hear about refused issuance attempts.

How do I add these records at Cloudflare, Route 53 or GoDaddy?

Use the format tabs above the output. Cloudflare and GoDaddy take one record per row in their DNS form: Type CAA, Name or Host @, then the Flag, Tag and Value shown. Route 53 takes one CAA record set per domain with one value per line, quotes included. A BIND zone file takes the full lines, quotes included, with the trailing dot on the domain name.

Does a CAA record stop a certificate that was already issued?

No. CAA is checked at issuance, not at connection — browsers do not check CAA, and a certificate issued in violation of a CAA record still works in every client. The violation is only detectable afterwards, through Certificate Transparency logs. CAA prevents future mis-issuance; it does nothing about a certificate that already exists. To deal with an already-issued certificate, revoke it at the issuing CA.

What does this tool NOT do?

It never queries DNS, so it cannot see your live records or confirm they published — verify with dig +short yourdomain CAA or your provider’s DNS page after adding them. It does not publish anything: you paste the output into your own DNS provider. And accounturi and validationmethods parameters are only honoured by CAs that support them; a CA that does not understand a parameter ignores it unless the critical flag is set.