Skip to content
// free tool

CAA record checker

A CAA record is a short DNS entry that names the companies allowed to issue SSL certificates for your domain. This tool looks up your CAA records the way a certificate authority does, shows which authorities they allow, and reads your current certificate so you can see whether the two match. It is a passive check: public DNS lookups and one ordinary TLS connection, nothing more.
// sample result
odesstra ~ $ check yourbusiness.co.za
[dns]A 203.0.113.24 · MX ok · CAA nonepass
[tls]TLSv1.3 · cert valid · expires in 212dpass
done in 6.2s · nothing attacked
// what it checks

What this tool looks up

  • Your CAA records, found the way certificate authorities find them: if your exact domain has none, we look at its parent domain, and so on up the tree. We show where they were found.
  • Which authorities are allowed, from the issue and issuewild entries, for example letsencrypt.org or sectigo.com.
  • Your current certificate's issuer, from one TLS handshake, so you can compare it with what your CAA record allows.
  • Your other basic DNS records: the A/AAAA addresses your domain points to and whether it lists MX records for email.

If you have no CAA record, the tool says so. That is the default for most domains and is not an emergency: it simply means any publicly trusted certificate authority may issue a certificate for you.

// reading your results

What good looks like

A typical CAA setup
example.co.za.  CAA 0 issue "letsencrypt.org"
example.co.za.  CAA 0 issuewild ";"
example.co.za.  CAA 0 iodef "mailto:security@example.co.za"

Here only Let's Encrypt may issue ordinary certificates, nobody may issue wildcard certificates (the ; means "no one"), and authorities are asked to report refused requests to a security address.

// hacker view

[dns] A 203.0.113.10 · MX ok · CAA none info

// plain english

Any certificate company could issue a padlock certificate for your domain. That's the default and it's common. Adding a CAA record naming the authority you use is a cheap extra safeguard.

// limits

What this check does not do

It makes public DNS lookups and one TLS connection to your site. It doesn't check subdomains you didn't type, doesn't try to request a certificate, and can't see certificates that may exist for your domain on other servers. For that, public Certificate Transparency logs are the right place to look. A CAA record also can't stop an authority that ignores the rules; it reduces risk, it doesn't remove it.

// how to add one

Adding a CAA record safely

  1. 01

    Find your current issuer

    Run this tool or the SSL certificate checker and note the issuer. If you use a CDN such as Cloudflare, check which authorities it uses on your plan, because it may use more than one.

  2. 02

    Add an issue record for each authority you use

    At your DNS provider, add a CAA record with flag 0, tag issue and the authority's domain, such as letsencrypt.org. Add one record per authority.

  3. 03

    Decide about wildcards and reports

    If you never use wildcard certificates, add issuewild ";". Optionally add an iodef record with an email address for reports.

  4. 04

    Recheck after any hosting move

    A new host may use a different authority. Update the CAA record before the move, not after the first renewal fails.

// questions

Common questions

Do I need a CAA record?

It's optional. Without one, any publicly trusted certificate authority may issue for your domain. Adding one is a small, low-cost way to narrow that down, so it's sensible tidy-up for a business domain.

Can a CAA record break my website?

It can stop your certificate renewing if it leaves out the authority your host uses. That's why you should check your current issuer first and update the record before changing hosts. It doesn't affect your existing certificate.

What CAA record do I need for Let's Encrypt?

A record with tag issue and value letsencrypt.org, for example example.co.za. CAA 0 issue "letsencrypt.org". If you also use other authorities, add a record for each.

Why does the tool say the record was found on a different name?

Certificate authorities climb the DNS tree. If shop.example.co.za has no CAA record, they use the one on example.co.za. We show the name where the record was found so you know which one applies.

Does a CAA record make my site secure?

No single setting does that. A CAA record makes one kind of attack, a wrongly issued certificate, harder. The full website security check shows the other basics.

Talk to a human