CAA record explained: control your SSL certificates
Published on June 19, 2026 9 min read
A CAA record defines which certificate authorities may issue an SSL certificate for your domain. Learn how to set one up and check it.
A CAA record is a DNS setting that lets you define which certificate authorities (CAs) are allowed to issue an SSL certificate for your domain. It helps prevent a wrong or fraudulent certificate from being created for your domain. This guide explains what a CAA record does, how it is structured, which CAA record LJPc already sets up for you, and how to set one up and check it yourself.
What is a CAA record?
CAA stands for Certification Authority Authorization. It is a separate type of DNS record, known technically as type 257, defined in the internet standard RFC 8659. With a CAA record you tell certificate authorities which parties may and may not create a TLS or SSL certificate for your domain.
A certificate authority, or CA for short, is the organization that issues SSL certificates. Well-known examples are Let's Encrypt, Sectigo, and DigiCert. Without a CAA record, any publicly trusted CA can issue a certificate for your domain. With a CAA record, you limit that to the CAs you explicitly allow.
Why set up a CAA record?
The purpose of a CAA record is to prevent certificates from being issued incorrectly. When someone requests a certificate for your domain from any CA, that CA first checks your CAA record. If the CA is not listed, it refuses the request.
This check has been mandatory since 8 September 2017. The CA/Browser Forum, the group of certificate authorities and browser makers, states in its Baseline Requirements that every publicly trusted CA must consult the CAA record before issuing a certificate. If you use a free CA such as Let's Encrypt, it follows the same rule.
Setting up a CAA record is not required, but it is an extra layer of security for your domain.
What does a CAA record look like?
Every CAA record has three parts: a flag, a tag, and a value. Here is an example:
example.com. CAA 0 issue "letsencrypt.org"
In this example, 0 is the flag, issue is the tag, and letsencrypt.org is the value. Below is what each part means.
The flag
The flag is a number between 0 and 255. In almost all cases you use 0. The value 128 turns on the so-called critical flag: if a CA does not recognize the tag, it must then refuse the request. For the standard tags below, leave the flag at 0.
The tag
The tag determines what the record controls. There are three tags:
| Tag | Meaning |
|---|---|
| issue | Authorizes a CA to issue certificates for the domain. |
| issuewild | The same as issue, but for wildcard certificates such as *.example.com. If at least one issuewild record exists, it overrides issue for wildcard requests. |
| iodef | An address (mailto: or https://) where a CA sends reports about requests that are not allowed. |
The value
For the issue and issuewild tags, the value is the identifier of the CA, for example letsencrypt.org. An empty value, written as a semicolon, means that no CA at all may issue a certificate:
example.com. CAA 0 issue ";"
If you want to allow more than one CA, add a separate issue record for each one:
example.com. CAA 0 issue "letsencrypt.org"
example.com. CAA 0 issue "sectigo.com"
Common CA identifiers
These are the values for a number of well-known certificate authorities. Always check the documentation of your own CA, because some CAs use more than one identifier.
| Certificate authority | Value in the record |
|---|---|
| Let's Encrypt | letsencrypt.org |
| DigiCert | digicert.com |
| Sectigo | sectigo.com |
| GlobalSign | globalsign.com |
| Google Trust Services | pki.goog |
| Amazon | amazon.com |
CAA at LJPc hosting
A hosting package with LJPc already has a CAA record for Let's Encrypt in your DNS zone: 0 issue "letsencrypt.org", on your domain itself and on * (the names that are not listed separately in your zone). Let's Encrypt issues the free SSL certificate that we request and renew for you automatically. If you use that certificate, your CAA record is already in order. If you only have DNS management with LJPc, check the list of DNS records for your domain to see whether a CAA record is there.
If you use a certificate from another issuer, such as Sectigo or DigiCert, add that issuer with its own issue record on your domain, next to Let's Encrypt. Keep the Let's Encrypt records in place: without them, your free certificate can no longer renew.
Adding a CAA record
Like an A record or a TXT record, you add a CAA record in the DNS management of your domain. Where that is depends on your package. If your domain comes with a hosting package, you manage your DNS records in Plesk. If you only have DNS management with LJPc, you do it in the customer portal. Which route applies to you is explained in managing DNS records. Your records only work if your domain uses the LJPc nameservers; how to set them is explained in changing your nameservers.
In the customer portal
- Log in to the customer portal, open the Services menu, choose Domains and open your domain.
- Under DNS records, click Add record and choose CAA under Type.
- Under Name, enter
@for your whole domain, or the name of a subdomain, for exampleshop. You do not need to add your domain name after it. - Leave Flags at 0.
- Under Tag, choose issue for certificates, issuewild for wildcard certificates, or iodef for reports.
- Under Issuer or report URI, enter the value without quotation marks, for example
sectigo.com. For iodef, enter an address, for examplemailto:admin@example.com. - Leave TTL at 3600 seconds or choose a value between 60 and 86400, and click Save.
In Plesk
You open Plesk from the customer portal; how that works is explained in opening Plesk from the customer portal.
- In Plesk, go to Websites & Domains, click the Hosting & DNS tab of your domain and then DNS. Then click Add Record.
- Choose CAA under Record type.
- Leave Domain name empty if the record is for your whole domain. Only fill it in if the record belongs to a subdomain.
- Under Tag, choose issue, issuewild, or iodef.
- Under Value, enter the issuer without quotation marks, for example
sectigo.com. Plesk sets the flag to 0 itself. - Confirm with OK. Plesk then queues the record, but does not apply it to your DNS zone yet.
- Click Update above the list. Plesk shows a notice there that your changes are not saved yet. Only after you click Update does the record go into your DNS zone.
When you edit or delete a CAA record, you also click Update afterwards, otherwise your DNS zone stays as it was. If you decide not to apply the queued changes after all, click Revert in the same notice.
Subdomains, wildcards, and how CAs find the record
A CA finds the CAA record by working up the domain name, from the most specific name toward the root. It first looks at the exact name, for example www.example.com. If it finds no CAA record there, it tries example.com, and so on up to the level directly below the root. The first set of records it encounters is the one that counts.
Because of this, a CAA record on your main domain automatically applies to all subdomains. If you want to allow a different CA for a subdomain, you place a separate CAA record on that subdomain. For that name, the separate record replaces the rules of the main domain.
For wildcard certificates, such as *.example.com, there is a dedicated tag: issuewild. If at least one issuewild record is present, it applies to wildcards and the regular issue tag is ignored for wildcards. If there is no issuewild, the issue tag also decides whether wildcards are allowed. With issuewild ";" you block wildcard certificates entirely.
Checking your CAA record
After you save a CAA record, you can check whether it is correct. On macOS and Linux you use the dig command:
dig CAA example.com +short
On Windows you use nslookup:
nslookup -type=CAA example.com
With a hosting package from LJPc you will at least see 0 issue "letsencrypt.org". At LJPc, a new or changed record usually reaches our name servers within a minute. To see that right away, query one of our name servers directly, for example with dig CAA example.com @ns1.ljpc.network +short. Servers that still have the old value in their cache only see the change once the TTL expires, which at LJPc is usually after an hour. Read more in DNS propagation.
There are also online CAA checkers that let you verify the same thing without using the command line.
Common problems
Running into an issue? This table points you in the right direction.
| Problem | Cause | Solution |
|---|---|---|
| A certificate cannot be created or renewed | Your CAA record does not allow the CA you use | Add the correct CA with an issue tag. For the free certificate from LJPc, that is letsencrypt.org |
| A wildcard certificate is refused | An issuewild record is present that does not name the CA | Adjust the issuewild tag or add the correct CA |
| Your new record is not in your DNS zone | Plesk queued the change but did not apply it | Click Update above the list of records |
| A change does not take effect right away | The old value is still cached (TTL) | Wait until the TTL has expired, at LJPc usually an hour |
| The CA cannot read the record | A DNS or DNSSEC error (SERVFAIL) | Check your zone and your DNSSEC settings |
More solutions are in troubleshooting DNS problems.
CAA compared to DNSSEC and DANE
A CAA record protects the moment of issuance: it decides who may create a certificate. It does not check the connection itself and does not stop a CA that ignores the rules. So it is a valuable measure, but not an airtight one.
You can combine CAA with other techniques. With DNSSEC you sign your DNS data, so a CA can trust that your CAA record was not altered along the way. If your domain is registered with LJPc and uses our name servers, we turn on DNSSEC automatically. DANE goes a step further and defines which certificate itself is valid. Mail servers use it to verify, while setting up the connection, that the certificate is correct. Where CAA works at issuance, DANE works at the connection.
With a CAA record, you stay in control of who may issue certificates for your domain. Need help? Create a support ticket and we will look into it with you.
Frequently asked questions
Is a CAA record required?
No, setting up a CAA record is not required. It is recommended, though, because it gives you extra control over who may issue certificates for your domain. A hosting package with LJPc already includes a CAA record that only allows Let's Encrypt, the issuer of your free SSL certificate.
What happens if I have no CAA record?
Without a CAA record, any publicly trusted certificate authority may issue a certificate for your domain. With a CAA record, you limit that to the CAs you have listed, and every other CA must reject the request.
Does a CAA record fully block an attacker?
No. A CAA record is only checked at issuance, and only by CAs that follow the rules. It does not stop a CA that ignores the rules, and it does not invalidate a certificate that was already stolen. It mainly reduces the chance of certificates being issued incorrectly by trusted CAs.
Does a CAA record also apply to my subdomains?
Yes. A CA works up the name from the most specific part and uses the first CAA record it finds. As a result, a record on your main domain also applies to subdomains, unless a subdomain has its own CAA record. That separate record then counts for that name.
How long does it take for a CAA record to become active?
At LJPc, a new or changed record usually reaches our name servers within a minute. If you work in Plesk, click Update above the list after saving, otherwise the change is not applied. Servers that still have the old value in their cache only see the change once the TTL expires, which at LJPc is usually after an hour.
Which value do I use for Let's Encrypt?
For Let's Encrypt you use the value letsencrypt.org. A complete record then looks like this: 0 issue "letsencrypt.org". As long as there is no issuewild record, this record also covers wildcard certificates. A hosting package with LJPc already has this record in your DNS zone.
I use a certificate from another issuer. What should I do?
Add that issuer with its own issue record on your domain, for example 0 issue "sectigo.com". Keep the record for Let's Encrypt, because your free certificate from LJPc needs it to renew. The value your issuer uses is listed in its documentation.