CAA records
CAA records specify which certificate authorities can issue certificates for a DNS name. Use them to authorize providers, restrict certificate issuance, and publish an incident-reporting destination.
What a CAA record is
A Certificate Authority Authorization (CAA) record contains a flag, a tag identifying the policy type, and a value. For example, an Issue policy with the value digicert.com authorizes DigiCert® to issue certificates for the applicable name.
CAA authorization does not replace certificate validation requirements or revoke certificates that have already been issued.
For secondary zones, make record changes at the primary DNS provider. See Secondary DNS zones.
Explore CAA records on the Records page
To view CAA records, go to DNS > Zones, select Primary zones, open the zone, and select the Records tab.
In Grouped view, expand CAA (Certificate Authority Authorization).
The table displays the following information:
Column | Description |
|---|---|
Record name | The complete DNS name, including the zone name |
Tag | The type of authorization or reporting policy |
Value | The certificate authority identifier or policy value |
Flags | Whether the policy is marked critical |
TTL | How long the records can be cached, in seconds |
A record name can contain multiple policy entries. These appear together in the table.
Use Search to locate a record or switch to Table view. Each row provides an actions menu for editing or deleting the record. Select row checkboxes to perform bulk deletion.
Create a CAA record
To create a CAA record, open the zone’s Records tab:
Select Add record, either at the top of the page or beside CAA (Certificate Authority Authorization).
Set Record type to CAA (Certificate Authority Authorization).
Enter Name. Use
@for the zone apex or enter a name within the zone, such aswww.Enter TTL in seconds.
Under Authorization policies, select a Tag.
Select a Provider. For a listed provider, review the automatically populated Value. For Custom, enter the required value.
Select Flags.
To include another policy at the same name, select Add another and complete its fields.
Select Save and close, or Save and add another to create a record at another name.
The form contains these fields:
Field | Description |
|---|---|
Record type | The DNS record type; select CAA (Certificate Authority Authorization) |
Name | The name to which the CAA policies apply; use |
TTL | The cache duration, in seconds |
Tag | The certificate issuance or incident-reporting policy type |
Provider | A listed certificate authority, Custom, or None |
Value | The value associated with the selected tag |
Flags | 0: Not critical or 128: Critical |
For a zone named example.com, entering www creates policies at www.example.com. Entering @ creates them at example.com.
Use the delete icon beside a policy to remove that entry before saving.
Choose the critical flag
The Flags field controls how a certificate authority handles an unrecognized or unsupported policy tag:
0: Not critical: The authority can ignore the unrecognized or unsupported tag
128: Critical: The authority must not issue a certificate if it cannot recognize or support the tag
Recognized and supported policies apply regardless of the flag value. Select 128: Critical only when you intend unsupported tags to prevent issuance.
Update or delete a CAA record
To update a CAA record:
Locate the record on the Records tab.
Open its actions menu and select Edit.
The Record type and Name fields are read-only in the edit form.
Update TTL or the entries under Authorization policies.
Use Add another to add a policy or the delete icon to remove one.
Select Update.
To delete the CAA record, open its actions menu, select Delete, and confirm. To delete multiple records, select their checkboxes and use Delete in the selection toolbar.
Deletion cannot be undone. To remove only one provider or reporting destination, edit the record and remove that policy entry.
Notice
Deleting CAA records does not prohibit issuance. A parent policy may become applicable, or CAA may no longer restrict issuance for that name. Verify the resulting policy after removal.
Choose a policy and certificate authority
Select the tag that matches the certificate or reporting policy you want to configure.
Tag | DNS property | Purpose |
|---|---|---|
Issue |
| Authorizes issuance for DNS names, including wildcard issuance when no Issue Wild policy is present |
Issue Wild |
| Specifies the authorities permitted to issue wildcard certificates |
Issue Mail |
| Specifies the authorities permitted to issue S/MIME certificates for email addresses |
Issue VMC |
| Specifies the authorities permitted to issue Verified Mark Certificates |
IODEF |
| Specifies a destination for certificate issuance incident reports |
These tags serve distinct purposes. Issue Mail, for example, controls email certificate authorization independently of Issue and Issue Wild.
Authorize standard or wildcard certificates
Add a policy with Tag set to Issue for standard, non-wildcard certificates.
Select the certificate authority under Provider.
Review the populated Value and select Flags.
If you need a separate wildcard policy, select Add another and choose Issue Wild.
Select the provider authorized for wildcard issuance.
Save the record.
When Issue Wild policies are present, they govern wildcard issuance instead of the Issue policies. Without an Issue Wild policy, the Issue policies also govern wildcard issuance. An Issue Wild policy alone does not restrict non-wildcard issuance.
For *.example.com, configure the policy at example.com using Name @. Do not enter * merely to select wildcard certificate issuance.
Authorize multiple certificate authorities
Configure the first provider’s policy.
Select Add another.
Select the same tag and another provider.
Repeat for each authority you intend to authorize.
Save the record.
For example, two Issue entries can authorize different providers. Use a separate policy entry for each rather than combining provider identifiers in a single Value.
Authorize S/MIME or Verified Mark Certificates
Select Issue Mail for S/MIME or Issue VMC for Verified Mark Certificates.
Select the intended provider.
Confirm the provider’s required CAA value and support for the certificate type.
Review Flags and save the record.
For S/MIME, configure the policy for the DNS name used in the email address. For example, a policy for addresses ending in example.com belongs at example.com. CAA authorization does not complete email address validation.
Use a custom provider value
Select Custom when the provider is not listed or its instructions require additional parameters:
Select the appropriate Tag.
Set Provider to Custom.
Enter the provider’s CAA identifier and any supported parameters in Value.
Review Flags and save the record.
Enter only the value for the selected tag, not a complete BIND record. Use the identifier and parameter syntax supplied by the certificate authority.
Prevent certificate issuance
Selecting None sets Value to ;, representing an empty issuer value for the selected authorization tag.
To prevent both standard and wildcard TLS certificate issuance under the applicable policy:
Create or edit the CAA record at the intended name.
Set Tag to Issue.
Set Provider to None.
Leave Flags at 0: Not critical.
Select Add another.
Set the second policy’s Tag to Issue Wild and Provider to None.
Remove other Issue and Issue Wild entries that authorize providers at that name.
Review the policy summary and save.
An empty issuer entry does not override another entry that authorizes issuance for the same policy type.
To permit standard certificates while preventing wildcard issuance, retain the required Issue authorizations and configure Issue Wild with Provider set to None.
These TLS policies do not replace Issue Mail or Issue VMC policies. Review each certificate type separately. A restrictive policy can also prevent future certificate renewals, so check dependent services before saving.
Configure incident reporting
Use IODEF to publish a destination where a certificate authority may send incident reports. Reporting depends on the authority’s support and practices; publishing a destination does not guarantee reports.
To add an email reporting destination:
Create or edit the CAA record.
Under Authorization policies, add a policy with Tag set to IODEF.
The Provider field displays Custom.
In Value, enter a reporting URI such as
mailto:security@example.com.Leave Flags at 0: Not critical, unless your policy requires otherwise.
Save the record.
IODEF values can also identify an HTTP or HTTPS endpoint that supports the required reporting protocol. A reporting-only policy does not itself restrict certificate issuance.
How policies apply across DNS names
For TLS certificates, a certificate authority checks the requested DNS name for CAA records. If none are found, it checks successive parent names until it finds a CAA record set.
For example, when checking www.shop.example.com, it checks that name, then shop.example.com, then example.com. A closer CAA record set takes precedence; its policies are not combined with the parent’s policies.
CAA lookups also follow CNAME records to their canonical names. You cannot add a CAA record at a name that already has a CNAME record. Review the target’s CAA configuration when investigating issuance problems involving a canonical name.
For certificate requests containing multiple DNS names, authorization must be checked for each name. See CNAME records for configuration restrictions.
TTL and policy changes
The TTL, or time to live, specifies how long the CAA records can be cached. Enter this value in seconds. For example, 300 represents five minutes.
After changing a policy, cached copies may continue to contain the previous authorization until their TTL expires. Lowering the TTL does not shorten the lifetime of copies already cached using the previous value.
Before changing certificate providers:
Add the new provider’s required authorization.
Verify the published CAA records on the authoritative nameservers.
Allow previously cached policies to expire.
Confirm issuance with the new provider before removing an authorization that existing workflows still need.
Changing a CAA policy does not revoke existing certificates.
For change preparation and recovery, see Update or delete DNS records safely.