DNSSEC for a business domain: what it protects and what it does not
Every visit to your website and every email sent to your company starts with a DNS lookup. A resolver asks where example.com lives, gets an answer, and trusts it. Classic DNS has no way to prove that the answer really came from your DNS provider and was not changed on the way.
DNSSEC (DNS Security Extensions) adds that proof. Your DNS zone is signed with cryptographic keys, and a validating resolver checks the signatures before it uses the answer. If the signature does not match, the resolver refuses the answer instead of sending your customers to the wrong server.
The short answer: DNSSEC protects the integrity of your DNS records between your DNS provider and the resolvers that validate. It does not encrypt anything, it does not hide your records, and it does not help if someone logs into your registrar or DNS account and changes the records there. It is worth enabling for a business domain, but only together with good care of the accounts that control the domain.
What DNSSEC protects
DNSSEC is described in RFC 4033 and its companion documents, and RFC 9364 (BCP 237, February 2023) collects the current set of standards. It gives a resolver 2 assurances:
- Data origin authentication: the answer was signed by the keys published for your zone.
- Data integrity: nobody changed the answer after it was signed, including answers that say a name does not exist.
The trust comes from a chain. The root zone has been signed since 15 July 2010, top level domains such as .com and .org are signed, and each parent zone publishes a DS (Delegation Signer) record that points to the key of the child zone. A validating resolver walks that chain from the root down to your domain. If any link is missing, your domain is treated as unsigned.
In practice this closes the door on forged DNS answers: cache poisoning of a resolver, or a network on the path that rewrites responses. For a company, that matters for the website, for the MX records that route your mail, and for the TXT records that carry SPF, DKIM and DMARC (see SPF, DKIM and DMARC explained).
What DNSSEC does not protect
Knowing the limits is just as important, because DNSSEC is often expected to do things it was never designed for.
- No confidentiality. RFC 4033 says it plainly in section 1: the extensions do not provide confidentiality. Anyone can still see which names are looked up.
- No protection against a compromised account. If an attacker logs into your registrar or DNS hosting account, they can change records, change nameservers, or remove DNSSEC entirely. The new records will be signed by your own provider and will validate. This is why CISA's Emergency Directive 19-01 of 22 January 2019 on DNS infrastructure tampering focused on account passwords, multi-factor authentication and watching for unexpected record changes. Our article on nameserver and registrar changes covers those early signs.
- No protection for a record that points to the wrong place. A dangling CNAME to a cloud service you no longer use is signed just as well as a correct one. See subdomain takeover.
- No protection where nobody validates. The signatures only help if the resolver of the person looking up your domain checks them. Many large public resolvers and ISPs do, but not all.
How to check whether your domain is signed
You can check it yourself in a minute with dig:
dig +short DS example.com
dig +dnssec +multi DNSKEY example.com
dig +dnssec A www.example.com
The first command asks the parent zone for a DS record. No output means the chain of trust is not set up at the registry, even if your DNS provider signs the zone. The second shows the keys your zone publishes, and the third should return an RRSIG record next to the answer.
To see whether a validating resolver accepts the answer, look at the flags in the header of a query sent to a resolver that validates:
dig @1.1.1.1 www.example.com A
The ad flag (authenticated data) in the response means the answer was validated. A SERVFAIL for a name that works elsewhere is the typical sign of a broken signature. Visual tools such as DNSViz draw the whole chain and show exactly which link fails.
Enabling DNSSEC without taking your domain offline
DNSSEC is one of the few DNS settings that can make a domain disappear for validating users, so it pays to do it in order.
- Sign the zone at your DNS provider. Most managed DNS services do this with 1 switch and handle the key management for you.
- Choose a current algorithm. RFC 9904 (November 2025) lists algorithm 13 (ECDSAP256SHA256) and algorithm 15 (ED25519) as recommended for signing. RFC 9905 says the SHA-1 based algorithms 5 and 7 must not be used for new signatures, so a zone still signed with them should be moved.
- Publish the DS record at the registrar. Your DNS provider gives you the values. Some registries can pick them up automatically through CDS and CDNSKEY records (RFC 8078).
- Verify from the outside with the commands above before you consider it done.
Where DNSSEC usually breaks
Typical DNSSEC outages are not attacks. They come from changes made in the wrong order:
- Moving to a new DNS provider while the old DS record stays at the registrar. The new provider signs with different keys, the old DS no longer matches, and validating resolvers return
SERVFAIL. Remove the DS first, wait for the old record to expire from caches, then move, then add the new DS. - Turning signing off at the provider but leaving the DS at the registrar. The result is the same outage.
- A DS record for a key that was rolled without updating the parent.
A short checklist for a business domain:
- DS record present at the registry and matching a published DNSKEY
- algorithm 13 or 15, no SHA-1 based algorithm
adflag set when queried through a validating resolver- multi-factor authentication on the registrar and DNS accounts
- a written order of steps for any change of DNS provider
How Datahorses helps
Business Alerts check your domains from the outside, every day, and need no access to your systems. Missing or broken DNSSEC is one of the checks in what we guard, next to nameserver and registrar changes and the records that carry your email authentication. When something changes or fails validation, a specialist reviews it and you receive the exact steps for your DNS provider, as described in what happens when we find something. You can see how it looks in the example dashboard.
More articles
CAA records: deciding which certificate authorities may issue for your domain
A CAA record tells certificate authorities which of them may issue a TLS certificate for your domain. It takes a few minutes to set up and closes a door most companies leave open.
DKIM key rotation: when and how to rotate your selectors
A DKIM key that never changes is a key that stays useful to anyone who obtains it. Selectors let you replace it without a single failed signature. Here is when and how.
SPF "too many DNS lookups" (permerror): how to fix the 10 lookup limit
Every tool that sends mail for you adds an include to your SPF record. Past 10 DNS lookups the record breaks for everyone. Here is how to count them and how to fix it.