Skip to main content
SiteScan.top

DNSSEC and CAA: two DNS settings that protect your domain and its certificates

DNSSEC stops forged DNS answers from sending visitors elsewhere; CAA limits which certificate authorities may issue for your domain. What each one protects against, how to switch them on safely and how to avoid locking yourself out.

Infrastructure · Published: 3 November 2026 · 6 min read · Анна Ковалёва

Most of a website's security lives on the server: HTTPS, headers, patched software. But before a browser ever reaches that server, it asks DNS where the domain lives, and before a certificate is issued, a certificate authority decides whether the request is legitimate. Two DNS settings harden exactly those steps. Neither is mandatory, and most of the web runs without them — which is why they are worth knowing about before you need them.

DNSSEC: signed answers

Ordinary DNS answers are not authenticated. A resolver that receives a forged reply — through cache poisoning, or an attacker on the network path — has no way to tell it from the real one, and will happily send visitors to a different server.

DNSSEC adds cryptographic signatures. Your zone signs its records with a key; the parent zone (.com, .de, .ru and so on) publishes a DS record that vouches for that key; the parent is in turn vouched for by the root. A validating resolver follows that chain and rejects any answer whose signature does not check out. Many public resolvers and internet providers validate by default.

Turning it on. With most managed DNS providers it is a single switch: the provider signs the zone and either publishes the DS record at the registrar for you or shows you the values to enter there. If your DNS and your registrar are different companies, copy the DS record exactly.

The part that can hurt. A wrong or stale DS record does not just switch protection off — it makes the domain unresolvable for every validating resolver, so for a large share of visitors the site simply disappears. The two classic causes:

CAA: who may issue certificates

A CAA (Certification Authority Authorization) record lists the certificate authorities allowed to issue TLS certificates for your domain. Since September 2017 every public CA has been required to check it before issuing. If your record says only Let's Encrypt may issue, any other CA has to refuse — even if someone has managed to pass its domain validation by other means.

A typical set of records:

``text example.com. CAA 0 issue "letsencrypt.org" example.com. CAA 0 issuewild ";" example.com. CAA 0 iodef "mailto:security@example.com" ``

The first allows Let's Encrypt to issue ordinary certificates, the second forbids wildcard certificates entirely, and the third asks CAs to report refused requests to that address. Subdomains inherit the records from the domain above them unless they publish their own.

The part that can hurt. CAA applies to every service that obtains certificates for your domain, not just your own server. A CDN, a hosted shop, a status page or an e-mail provider on a subdomain may use a different CA. Forget one, and its next automatic renewal fails — usually weeks later, when nobody connects the expired certificate with a DNS change. Before publishing CAA, list every certificate currently in use; certificate transparency search tools such as crt.sh show every certificate ever issued for your domain and who issued it.

Which one first?

CAA is the easier win: a few records, no risk of taking the site offline, and a real reduction in the chance of a mis-issued certificate. DNSSEC protects against a different and rarer class of attack and needs more care when you change DNS providers. For a domain that handles payments, logins or e-mail for a business, both are worth having; for a small brochure site, CAA alone is a sensible start.

These sit alongside the other domain-level settings — mail authentication in SPF, DKIM and DMARC, renewal dates in expiry dates, and the wider server review in the technical audit.

What SiteScan checks

Every scan looks up the DS record of your registrable domain and its CAA records, and shows both in the "DNS & email" group of the site checks. A signed zone and a published CAA set appear green; their absence is shown as a neutral fact rather than an error, because both are optional hardening. The same group lists your nameservers, mail records and the rest of the DNS picture, and the certificate group shows which authority issued your current certificate — the one your CAA record must allow. Details are in the help pages for DNSSEC and CAA. Run a free scan to see your domain's DNS.

Read next

Check how much of this is on your own site

A free scan surfaces broken links, JS errors and performance problems in about a minute.