Domain & Record Type

Quick test: google.com github.com cloudflare.com example.com (MX)

Auto-refresh every 30 seconds

ℹ How it works — Queries are made via DNS-over-HTTPS (DoH) directly from your browser.
⚠ CORS limitation — Most providers block browser-based queries. Only those with CORS enabled (e.g. Cloudflare) will respond. Failed queries mean the provider is blocking browser requests — not that your DNS is broken.
💡 For comprehensive checking — use WhatsmyDNS.net or CLI tools: dig @8.8.8.8 example.com · nslookup example.com 8.8.8.8

Propagation Progress

0 / 11

Waiting… 0%

Checked

Successful

Failed

Unique Results

DNS Server Results

—

Reference

Reading Card States

Green tint: Server responded, record found
Amber tint: Result differs from most common answer
Red tint: Query failed or no records found
Pulsing badge: Currently checking…

Why Most Queries Fail (CORS)

Browser security restricts cross-origin DNS fetches
Cloudflare permits CORS; most others don't
Failures indicate provider restriction, not DNS breakage
Your DNS records are still resolving correctly

CLI Alternatives

dig @1.1.1.1 example.com A
nslookup example.com 8.8.8.8
host -t MX example.com 1.1.1.1
WhatsmyDNS.net — server-side checking

When to Deploy

Wait for 100% on responding servers
Propagation typically takes 5–30 min
TTL affects how long old records cache
Use auto-refresh to monitor live