CAA checker: who can issue certificates for your domain?

GitHubVersion 1.1.0

Enter the hostname your certificate will cover to see which certificate authorities may issue for it. The check finds the CAA policy that applies, even when it's set on a parent domain, and answers separately for normal and wildcard certificates.

How to read the result

The result names the certificate authorities allowed for normal and for wildcard certificates. Each one appears as the domain it uses in CAA, such as letsencrypt.org.

You seeWhat it means
Names, then may issue.Only those certificate authorities may issue.
CAA does not restrict this kind of certificate.CAA lets any certificate authority issue.
No certificate authority is allowed.The policy blocks every certificate authority.
Policy inherited from a nameThe records sit on a parent domain, not on the name you entered.

Where the policy came from lists each name the check asked, in order.

api.github.com

Example

api.github.com has no CAA records of its own, so the check moves up to github.com and finds 7. For normal certificates, digicert.com, globalsign.com, letsencrypt.org, and sectigo.com may issue. Wildcard certificates leave out globalsign.com, because the issuewild records don't list it.

Checked on 9 October 2026.

How does CAA find the policy for a name?

It uses the closest name that has CAA records. The check starts at the exact hostname and moves up one level at a time. The first name with records holds the whole policy, and anything higher up is ignored.

  1. www.shop.example.com has no CAA records.
  2. shop.example.com has no CAA records.
  3. example.com has CAA records. This is the policy.

If no name up to the top-level domain has CAA records, CAA doesn't restrict anyone.

If a name is an alias (a CNAME), its target's CAA records count. The search doesn't climb the target's parent domains. It goes back to the parents of the name you entered. RFC 8659 defines this search.

What do issue, issuewild, and iodef mean?

SettingWhat it does
issueAllows one certificate authority to issue normal certificates. With no issuewild, it covers wildcards too.
issuewildAllows one certificate authority to issue wildcard certificates, such as *.example.com. When any issuewild exists, wildcards ignore issue.
iodefAn email or web address for reports about blocked requests. It doesn't allow or block anything.
issue ";"An empty value. On its own, it allows no certificate authority.
Flag 128Marks a record as critical. A certificate authority that doesn't understand it must refuse to issue.

Several issue records add up, and each one allows one more certificate authority. A policy with only issuewild records leaves normal certificates unrestricted.

Use the value your certificate authority publishes for CAA, such as letsencrypt.org for Let's Encrypt or digicert.com for DigiCert.

Why was my certificate blocked by CAA?

These are the usual causes:

  • A parent domain has CAA records you forgot, and your certificate authority isn't in them.
  • You listed one certificate authority, but your host or CDN gets certificates from another. Check its docs before you restrict issuance.
  • The certificate is a wildcard, and issuewild doesn't list your certificate authority.
  • The CAA lookup itself fails. The result then says the policy couldn't be determined. DNS lookup explains SERVFAIL and other errors, and the DNSSEC checker finds broken signatures, one possible cause.

Being allowed by CAA doesn't mean a certificate will be issued. The certificate authority still checks that you control the domain. This check reads the policy only and doesn't list certificates already issued.

The check asks Cloudflare's public resolver from stack127's server. stack127 doesn't keep the names you check.