DNSSEC not enabled on your zone
DNSSEC signs your DNS records so resolvers can verify the answers are genuine. Without it, a spoofed or poisoned DNS response can quietly redirect your visitors.
Why it matters
DNS cache poisoning and spoofing can point your domain at an attacker's server — for phishing, credential theft, or intercepting email.
DNSSEC doesn't encrypt DNS, but it makes forged answers detectable, so resolvers reject them.
How to check for it
- Your DNS provider's dashboard shows DNSSEC status (in Cloudflare: DNS → Settings → DNSSEC).
- Externally: a DNSSEC checker, or dig +dnssec <domain> and look for RRSIG records.
How to fix it
- Enable DNSSEC at your DNS provider (Cloudflare → DNS → Settings → Enable DNSSEC).
- Add the DS record it gives you at your domain registrar — DNSSEC isn't active until the registrar has the DS record.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- Does DNSSEC encrypt my DNS queries?
- No. DNSSEC is about authenticity — proving an answer wasn't forged. For privacy of queries you'd add DNS over HTTPS/TLS separately.