Skip to content
FlexibleToolsAI
Security Toolkit · Free, Nothing Stored

DNSSEC Checker

See whether a domain's DNS answers are cryptographically signed and validated. The checker looks for DNSKEY records in the zone and a DS record at the parent, and asks a validating resolver whether the chain of trust verifies — catching half-configured and broken DNSSEC.

Enter a domain and we query it through Google Public DNS over HTTPS, reading the Authenticated Data (AD) flag plus the DNSKEY and DS records. You'll see one of: enabled and validating, signed but missing the DS record at the registrar, failing validation (SERVFAIL — which makes the domain unreachable), or not enabled.

Instant Results

Live checks in seconds

Nothing Stored

No logs of what you check

No Sign-Up

Free, no credits or email

What Does DNSSEC Checker Do & How Does It Work?

Enter a domain and we query it through Google Public DNS over HTTPS, reading the Authenticated Data (AD) flag plus the DNSKEY and DS records. You'll see one of: enabled and validating, signed but missing the DS record at the registrar, failing validation (SERVFAIL — which makes the domain unreachable), or not enabled.

How to Use DNSSEC Checker (Step-by-Step)

  1. 1Enter the domain.
  2. 2Read the DNSSEC status.
  3. 3If it's signed but not delegated, add the DS record at your registrar.
  4. 4If validation fails, fix or roll back the keys urgently.

What DNSSEC protects against

Without DNSSEC, a resolver can be tricked into caching forged DNS answers (cache poisoning), sending visitors or email to an attacker. DNSSEC signs each record set, and validating resolvers reject answers whose signatures don't verify up the chain of trust to the root.

It needs two parts: your DNS host signs the zone (DNSKEY and RRSIG records) and your registrar publishes a DS record that links the parent zone to your key.

Enabling it safely

Most managed DNS providers (Cloudflare, Route 53, Google Cloud DNS) sign zones with one click and give you the DS record to add at the registrar. Broken DNSSEC is worse than none — a mismatched DS makes the domain fail to resolve — so re-check after changing DNS providers. See the rest of your setup with the Domain Security Checker.

Frequently Asked Questions

Does DNSSEC encrypt DNS?

No — it authenticates answers. Encryption of DNS queries is done by DNS-over-HTTPS or DNS-over-TLS.

What do you do with the domains and URLs I check?

Our server performs the lookup once and returns the result to your browser. We don't store the addresses you check or build a history. Private and internal addresses are blocked.

Is it free? Do I need an account?

It's completely free with no sign-up and no daily credits.

Explore More Free Browser Tools

View All 290+ Tools Directory →

All tools run client-side in your browser with zero data uploads, no sign-up, and zero tracking. Discover other popular converters and calculators:

Cryptographic Standards & Zero-Knowledge Privacy Architecture

DNSSEC Checker is engineered to strict security and cryptographic specifications — guaranteeing zero data leakage, zero backend telemetry, and audited implementation:

  • 1. 100% Zero-Knowledge Client Execution: Passwords, private keys, hashes, and API tokens are computed strictly in your browser's local memory via Web Crypto API (SubtleCrypto) and audited @noble/hashes. Nothing is ever sent to or stored on our servers.
  • 2. Official RFC & NIST Compliance: Adheres to established security specifications including RFC 2104 (HMAC), RFC 6238 (TOTP), RFC 9106 (Argon2id), RFC 4122 (UUID v4), and FIPS 180-4 (SHA family).
  • 3. Memory-Hard & Brute-Force Resilient: Incorporates robust hashing algorithms (Argon2id, bcrypt, PBKDF2) with configurable memory and iteration costs to defend against GPU-accelerated cracking.
  • 4. Transparent & Inspectable: Every cryptographic calculation occurs visibly in client-side JavaScript. You can verify through your browser's Network tab that zero outbound requests are made with your sensitive inputs.
  • 5. SSRF-Safe Diagnostic Probing: For internet-facing checks (SSL certificates, DNS records, HTTP security headers), handshakes run through isolated proxies that never log or store queried domains.

Suggest a Feature or Improvement for DNSSEC Checker

Need custom options, higher limits, or extra format support? Let our engineering team know!