DNSSEC (DNS security)
Digital signatures that guarantee a DNS answer was not swapped by an attacker
📖 Detailed description
Without DNSSEC an attack called DNS spoofing or cache poisoning is possible: an attacker slips in a forged answer and sends users to a fake site - identical to the real one, but built to steal passwords. It is like swapping a number in the phone book: you call "your bank" but reach a scammer. DNSSEC prevents this because every answer is cryptographically signed and forms an unbroken chain of trust up to the internet's root servers.
In practice, enabling DNSSEC means generating keys that sign your zone and publishing a DS record at your domain registrar (the company you bought the domain from). It is a technical setting, but worth the effort - especially for banks, stores, and anywhere trust in the domain is critical. Note: DNSSEC guarantees the authenticity of DNS answers, but it does not encrypt traffic - that is what HTTPS is for.
You can check whether your domain has DNSSEC correctly enabled and a DS record published with our free DNS Lookup tool at /dns.
Most common problems
No DNSSEC
The domain is vulnerable to swapped DNS answers and redirecting users to a fake site
No DS record at the registrar
The zone is signed, but the chain of trust is broken - protection does not work
A botched key rollover
A failed key rotation can take the whole domain down (it stops resolving)
Confusing it with encryption
DNSSEC confirms authenticity but does not hide query contents - it is not the same as HTTPS
How to fix it?
Enable DNSSEC in your DNS provider panel and publish the DS record at your domain registrar
Make sure the chain of trust is complete - from your zone up to the root servers
Plan key rollovers carefully, ideally with automation on the provider side
Treat DNSSEC as a complement to HTTPS, not a replacement for it
After enabling it, verify validation with an external tool
Examples
Good example
Bad example
🔗 Related indicators
SPF record (Sender Policy Framework)
A list of servers allowed to send email on behalf of your domain - the foundation of anti-spoofing protection
DMARC record
The rule that tells servers what to do with mail that fails SPF and DKIM checks
DKIM signature (DomainKeys Identified Mail)
A digital seal attached to every email - proof that the content was not altered in transit
Check this indicator for your website
Get a detailed analysis and personalized tips on how to improve this element on your website.
Start free analysis