CAA at united-domains: what the DNS editor can do
At united-domains the DNS records of a domain are organised into sections by type. For CAA there is the section “CAA (Zertifizierungsstellen)” with its own button to add a record. The record follows the usual structure of flag, tag and value, such as 0 issue "letsencrypt.org".
For every domain linked to a webspace or the website builder, united-domains automatically issues a free certificate. The help does not name the certificate authority behind it; the privacy notice lists Sectigo Limited as the company involved in SSL certificates, but united-domains names no CAA value anywhere. Before you restrict CAA for such a domain, read the issuer of the current certificate in the SSL checker and allow exactly that authority.
Many customers use united-domains only as a registrar and run the website elsewhere. The CAA value then depends on the website’s provider, for example letsencrypt.org at most hosts with a free certificate.
How to create the CAA record at united-domains
The way at united-domains:
- In the united-domains portfolio click the “DNS” icon next to the domain.
- Open the DNS records and go to the section “CAA (Zertifizierungsstellen)”.
- Choose “Hinzufügen” (add) and create the record: flag 0, tag issue and the certificate authority’s domain. The help does not describe how the form splits these values.
- Save and use the CAA checker to verify that the record is read.
Click path at united-domains
Official guide from united-domains: CAA-Eintrag anlegen(opens in a new tab)
Structure of the CAA record
A CAA record defines which certificate authorities may issue certificates for the domain. It consists of flag, tag and value: issue allows an authority to issue for the domain, wildcard certificates included, as long as there is no issuewild record. issuewild applies to wildcard certificates only and takes precedence over issue there. iodef names an address for reports. Without a CAA record any authority may issue; as soon as one exists, only those named. So first collect every authority the domain actually uses, including those of the CDN, shop system or mail provider.
The example allows Let’s Encrypt for regular and wildcard certificates. To forbid wildcard certificates altogether, add the line 0 issuewild ";"; to reserve them for another authority, name that one in the issuewild record.
example.com. CAA 0 issue "letsencrypt.org"
example.com. CAA 0 iodef "mailto:security@example.com"Verify and keep an eye on it
The CAA checker below reads the records the way a certificate authority sees them, including inheritance from the apex domain. You see right away whether the record has arrived at united-domains and whether the authority of the current certificate remains allowed. DomainWarn keeps checking CAA and certificate afterwards and alerts you when a renewal would fail because of CAA.