What CAA records do
A CAA record names a certificate authority allowed to issue TLS certificates for your domain. Every public authority must check CAA before issuing, and must refuse when it isn't on the list. That stops someone who tricks an authority you don't use from getting a valid certificate for your site. CAA records sit at the root of your domain and cover its subdomains too, unless a subdomain publishes its own.
This builder writes the records from a few choices and checks them against the authority that issues your current certificate, so publishing them never blocks your own renewals.
Building the records
- Enter your domain so the zone file lines carry the right name. It is optional.
- Tick the authorities that issue your certificates, or start from a preset for your hosting platform. Authorities we don't list can be added by their CAA identifier, one per line, from the authority's own documentation.
- Choose who may issue wildcard certificates, such as
*.example.com: the same authorities, no one, or only the ones you list. - Optionally, under More options, limit the validation methods authorities may use, tie issuing to one ACME account, and add an address for reports of refused requests.
The records update as you change a setting. Each one is a separate CAA record with the same name; copy the values into your DNS host one by one, or paste the zone file lines.
Don't lock yourself out
The most common CAA mistake is leaving out the authority that renews your certificate. Nothing breaks on the day you publish, but the next renewal is refused, often by an automated process nobody watches, and the site shows a certificate error when the current certificate runs out. Hosting platforms and CDNs that renew for you are affected the same way, and some use more than one authority.
Enter your current authority, or press Look up my current certificate and we run the SSL check for your domain and fill it in. If the authority isn't on your list, the result says so in red before you publish anything.
Wildcards, methods and accounts
When you don't list wildcard authorities separately, the authorities allowed to issue normal certificates may issue wildcard ones too. Choosing No one adds a record that forbids wildcard certificates entirely, which suits domains that never use them.
Validation methods such as dns-01 and http-01 limit how an authority may confirm you control the
domain. An ACME account URI limits issuing to your own account at that authority, so another customer of
the same authority can't get a certificate for your domain. These settings apply to every authority you
list, and the account URI works only with exactly one authority.
Who CAA protects you from
Certificate authorities confirm that you control a domain before they issue a certificate for it, and almost always they get it right. CAA is the extra lock for the rare times they don't: a mistake in an authority's checks, a hijacked DNS answer on the path an authority uses, or an attacker who briefly takes over a web server on one of your subdomains. With CAA in place, every authority you didn't list must refuse, whatever else happens, so the attacker has to fool your chosen authority instead of the weakest one on the internet.
CAA doesn't replace monitoring. Certificate Transparency logs record every certificate issued for your domain, and checking them now and then is still the best way to spot one you didn't ask for. Together, CAA narrows who can issue and the logs show what was issued.
Checking what you have now
To see your current CAA records, run a DNS lookup for the CAA type. The SSL check shows which authority issued your certificate and when it expires, so you can plan the change before the next renewal.