Skip to content
LookupOwl

CAA checker

See which certificate authorities may issue for a name, whether anyone else did, and make the records to fix it.

A domain or a host name, such as www.example.com. We follow CAA's rules and climb to the parent domain when the name has none.

Looks at certificates issued in the last 90 days and checks whether the CAA you publish allowed each CA.

Results for www.visualstudio.github.com

Checked live lookup62 ms

JSONCheck again

CAA: Restricted

www.visualstudio.github.com allows 3 certificate authorities for names and wildcards.

Found at
www.visualstudio.github.com
CAA records
  1. 0 issue "digicert.com"PassDigiCert
  2. 0 issue "letsencrypt.org"PassLet's Encrypt
  3. 0 issue "sectigo.com"PassSectigo
  4. 0 issuewild "digicert.com"PassDigiCert for wildcards
  5. 0 issuewild "letsencrypt.org"PassLet's Encrypt for wildcards
  6. 0 issuewild "sectigo.com"PassSectigo for wildcards

Allowed, and who really issued

AuthorityFor namesFor wildcardsIssued in 90 days
DigiCertAllowedAllowedAllowed, not seen
Let's EncryptAllowedAllowedAllowed, not seen
SectigoAllowedAllowedAllowed, not seen

No logged certificates in 90 days.

  • There is no iodef contact, so an authority cannot tell you about a refused or suspicious request. Fix: Add 0 iodef "mailto:[email protected]".

Make a CAA record set

Made in this page from what you pick. Without JavaScript the same form reloads the page with the lines.

Who may issue?
  • Wildcard certificates follow the issue lines, so no issuewild line is needed.
Zone filegithub.com. 3600 IN CAA 0 issue "letsencrypt.org" github.com. 3600 IN CAA 0 issue "digicert.com" github.com. 3600 IN CAA 0 issue "sectigo.com"

Check this record once it is live

Structured result (JSON) · 3.1 KB
{
  "domain": "www.visualstudio.github.com",
  "asOf": "2026-11-16T21:46:25.751Z",
  "verdict": "restricted",
  "found": {
    "name": "www.visualstudio.github.com",
    "queried": "www.visualstudio.github.com",
    "path": [
      "www.visualstudio.github.com"
    ],
    "viaCname": false
  },
  "records": [
    {
      "flags": 0,
      "critical": false,
      "tag": "issue",
      "value": "digicert.com",
      "ca": {
        "id": "digicert.com",
        "name": "DigiCert",
        "known": true
      },
      "params": [],
      "known": true
    },
    {
      "flags": 0,
      "critical": false,
      "tag": "issue",
      "value": "letsencrypt.org",
      "ca": {
        "id": "letsencrypt.org",
        "name": "Let's Encrypt",
        "known": true
      },
      "params": [],
      "known": true
    },
    {
      "flags": 0,
      "critical": false,
      "tag": "issue",
      "value": "sectigo.com",
      "ca": {
        "id": "sectigo.com",
        "name": "Sectigo",
        "known": true
      },
      "params": [],
      "known": true
    },
    {
      "flags": 0,
      "critical": false,
      "tag": "issuewild",
      "value": "digicert.com",
      "ca": {
        "id": "digicert.com",
        "name": "DigiCert",
        "known": true
      },
      "params": [],
      "known": true
    },
    {
      "flags": 0,
      "critical": false,
      "tag": "issuewild",
      "value": "letsencrypt.org",
      "ca": {
        "id": "letsencrypt.org",
        "name": "Let's Encrypt",
        "known": true
      },
      "params": [],
      "known": true
    },
    {
      "flags": 0,
      "critical": false,
      "tag": "issuewild",
      "value": "sectigo.com",
      "ca": {
        "id": "sectigo.com",
        "name": "Sectigo",
        "known": true
      },
      "params": [],
      "known": true
    }
  ],
  "evaluation": {
    "anyCaMayIssue": false,
    "anyWildcard": false,
    "noCaMayIssue": false,
    "wildcardFollowsIssue": false,
    "criticalUnknown": false,
    "allowed": [
      {
        "ca": "digicert.com",
        "name": "DigiCert",
        "known": true,
        "names": true,
        "wildcards": true,
        "accountBound": false,
        "validationBound": false
      },
      {
        "ca": "letsencrypt.org",
        "name": "Let's Encrypt",
        "known": true,
        "names": true,
        "wildcards": true,
        "accountBound": false,
        "validationBound": false
      },
      {
        "ca": "sectigo.com",
        "name": "Sectigo",
        "known": true,
        "names": true,
        "wildcards": true,
        "accountBound": false,
        "validationBound": false
      }
    ]
  },
  "contacts": {
    "iodef": [],
    "contactemail": []
  },
  "issuance": {
    "source": "ct",
    "status": "ok",
    "windowDays": 90,
    "byCa": [],
    "observedNow": null
  },
  "issues": [
    {
      "code": "NO_IODEF",
      "severity": "info",
      "message": "There is no iodef contact, so an authority cannot tell you about a refused or suspicious request.",
      "fix": "Add 0 iodef \"mailto:[email protected]\"."
    }
  ],
  "generated": null
}

Next step

What this page tells you

A CAA record is a short entry in your DNS that lists the certificate authorities allowed to issue certificates for a name. Before an authority issues, it must look the record up and refuse if it is not on the list. Most sites have none, which means every authority is allowed.

Type a domain or a host name and you get one sentence first: restricted, open, blocked, or could not read. Below it is every record written out line by line with the authority it names, then a grid with one row per authority. The grid shows who may issue for ordinary names, who may issue for wildcards, and who really did issue in the last 90 days.

  • Restricted. Some authorities are named. Everyone else must refuse.
  • Open. No record, or a record that only holds contact details. Any authority may issue.
  • Blocked. The record says no authority may issue. Right for a domain that never needs a certificate, a problem for one that does.
  • Could not read. The DNS server failed the question. Authorities refuse to issue until it answers.

Did anyone else issue?

Every publicly trusted certificate is recorded in open Certificate Transparency logs. This page reads the entries for your name from the last 90 days, matches each issuer to its CAA identifier, and marks it allowed or not by the records you publish now. A certificate from an authority your records do not allow sorts to the top of the grid with the words "Issued, not allowed by this CAA".

The logs are run by other people and are sometimes down. When they are, the page says so, keeps the CAA answer, and shows the issuer of the certificate your host serves right now instead. It never turns a log outage into an error.

How CAA is read

This page follows the rules authorities follow (RFC 8659), so what you see is what they see.

  • Names are looked up from the bottom. For www.shop.example.com the authority asks there first, then shop.example.com, then example.com, then com. The first name with any CAA record decides. The result says where it was found.
  • An alias is followed. If the name is a CNAME, the lookup follows it, and if the target has nothing it continues from the target's parent.
  • issue and issuewild. issue says who may issue for ordinary names. issuewild says who may issue wildcards. With no issuewild, wildcards follow issue. This page flags every authority that differs between the two.
  • Parameters. A value can end in extra settings. accounturi and validationmethods (RFC 8657) tie an authority to your account or to the checks it may use, and the page marks those rows as bound.
  • The critical flag. A record with the flag set and a tag the authority does not know means it must refuse. The page shows such a record in full.

Making a record set

Under the result is a form that writes the records for you. Tick the authorities you use, say whether wildcards are allowed, add an address for reports if you want one, and bind an authority to your account if you can. It shows the lines for a zone file, Cloudflare, Route 53 or Google Cloud DNS, each with a copy button.

  1. Pick who may issueTick every authority that issues for you. A missing one will be refused, so check your certificate tools first, for example your ACME client and any host that orders certificates for you.
  2. Publish the linesAdd them to the zone of the name. Several CAA records at one name add up.
  3. Check itRun the checker again once DNS has updated. The grid should show every authority you ticked as allowed.

With no record at all, the maker comes first, because writing one is the next step. The form works without JavaScript: it reloads the page with the lines in it, and with JavaScript the lines change as you tick.

What CAA cannot do

CAA stops an honest authority from issuing by mistake. It does not stop someone who can edit your DNS, and it does not stop an authority you list from being compromised. Pair it with strong access to your DNS account and, where you can, DNSSEC. To see the certificate your server serves, use the SSL checker; to see everything logged for a domain, use certificate search; for the raw records, use CAA lookup.

Questions people ask

Is having no CAA record a problem?

It is not a fault, and the page says so calmly. It does mean any certificate authority may issue for your name. Adding a record that lists only the authorities you use narrows that to the ones you chose.

What does "Issued, not allowed by this CAA" mean?

A certificate for your name was logged from an authority your records do not list. Authorities check CAA when they issue, so the record may have been added after the certificate. If the date is after your record went live, look into how it was ordered.

Which names do my CAA records cover?

The name they sit on and every name below it that has no CAA record of its own. A record on example.com covers www.example.com unless www has its own. A record on a subdomain replaces the parent's for that subdomain.

Why do I need to list a wildcard authority separately?

You do not have to. Wildcards follow the issue lines unless you publish an issuewild line. Add issuewild only when wildcards should be handled differently, for example to allow one authority for names and none for wildcards.

What is the identifier for my authority?

Let's Encrypt is letsencrypt.org, Google Trust Services is pki.goog, DigiCert is digicert.com, Sectigo is sectigo.com, GlobalSign is globalsign.com, and Amazon uses amazon.com and three other names. The page names the company behind each identifier it knows and says when it does not know one.

My certificate order was refused with a CAA error. What now?

Run the checker on the exact name in the order. If your authority is not in the grid as allowed, add it. If the page says it could not read the records, the problem is the DNS answer, so check the zone and its DNSSEC.

Does the record maker send what I type anywhere?

With JavaScript, no: the lines are made in your browser from your choices. Without it, the form sends your choices to this site as part of the page address so the page can write the lines. An ACME account address is not a secret.

Can I check a name that is not on the public internet?

No. This page asks public DNS and public logs, so it works for public names only.

Use it from AI, the API or the command line

Every LookupOwl tool is also a free API and an MCP tool, with no key and no account. This one is caa_check. Please be kind to the rate limits.

curl
curl "https://lookupowl.com/api/v1/tools/caa-check?q=github.com"
MCP
claude mcp add --transport http lookupowl https://lookupowl.com/mcp