DNSSEC check: are your DNS records signed?
DNSSEC adds cryptographic signatures to your DNS records, so resolvers can detect forged answers that would send your visitors or email to an attacker's server. Enabling it is usually one switch at your DNS host plus a DS record at your registrar. SiteShield passes it when DNS answers come back validated (2 of 100 points).
What is DNSSEC?
Your DNS host signs each record set; a DS record at your registrar links your zone to the parent (.com, .ae and so on) so validating resolvers can build a chain of trust from the DNS root down to your records. If a signature doesn't verify, a validating resolver refuses the answer instead of passing on a forgery.
Why it matters
DNSSEC signs your DNS records so attackers can't redirect your visitors to a fake copy of your site by poisoning DNS.
DNS poisoning or hijacking can redirect visitors to a lookalike site, or redirect your mail. DNSSEC doesn't encrypt anything, but it makes forged DNS answers detectable. It's a small item in the grade because other layers (HTTPS certificates) also protect visitors, but it's cheap to enable.
SiteShield maps this check to:
See how these standards fit together in the UAE website security checklist.
How SiteShield grades it
This check, "DNSSEC", can cost up to 2 points: a fail loses all 2, a warning loses 1. Every scan starts at 100.
| Result | When | Points lost |
|---|---|---|
| Pass | Cloudflare's public DNS-over-HTTPS resolver returns the domain's A record with the AD (authenticated data) flag set, meaning it validated the signatures. | 0 |
| Warning | The answer isn't validated: DNSSEC is not enabled, or the DS record is missing at the registrar. | 1 |
| Not checked | The lookup failed, so the status couldn't be determined. | 0 |
How to check it yourself
dig +dnssec example.com A @1.1.1.1 | grep -E 'flags:.* ad'
# the 'ad' flag means the answer was validated
dig +short DS example.com
Or run a free SiteShield scan, which checks this and 16 other settings in one go.
How to fix it
The quick version: Enable DNSSEC at your DNS provider (one click on Cloudflare) and add the DS record at your registrar.
Cloudflare
- Go to DNS → Settings and click Enable DNSSEC.
- If your domain is registered with Cloudflare Registrar, the DS record is added automatically. Otherwise copy the DS details Cloudflare shows into your registrar's DNSSEC page.
Other DNS hosts
Turn on DNSSEC/zone signing in the DNS host's panel, then add the DS record at your registrar. Check that your registrar supports DS records for your domain's extension; most generic and many country domains do.
Before you move DNS
Turn DNSSEC off (remove the DS record) before changing DNS providers, wait for the DS TTL to expire, then re-enable at the new provider. Moving with a stale DS record makes the domain unreachable for validating resolvers.
Nginx / Apache / WordPress
Not applicable: DNSSEC is configured at your DNS host and registrar, not on the web server.
FAQ
Can DNSSEC take my site offline?
Only if it's misconfigured, typically a DS record at the registrar that no longer matches the keys at the DNS host (for example after moving DNS). Follow the order above and it's safe.
Does DNSSEC encrypt DNS?
No. It signs records so tampering is detectable. Encrypting DNS queries is a separate thing (DNS over HTTPS or TLS).
Test your DNSSEC now
Run all 17 checks on your website and email domain in about 30 seconds. Free, no signup, passive checks only.
Rather not do it yourself? Fix it for me starts at AED 750 (about USD 205 by PayPal), quote agreed first. Monitoring re-scans weekly for AED 99/month or AED 990/year.