Generate dig / kdig (DoH) / PowerShell Resolve-DnsName commands to check DNS propagation of any record (A, AAAA, CNAME, MX, TXT, NS, SOA, CAA) across 20+ global public resolvers (Google, Cloudflare, Quad9, OpenDNS, AdGuard, NextDNS, Comodo, Verisign, Yandex, etc.) with region metadata. Compare expected vs actual answers (exact / contains / regex). Compute a TTL-based propagation ETA. Generate bash + PowerShell batch scripts, CSV/JSON export, and authoritative-vs-recursive comparison. 100% client-side — generates commands only; actual lookups require running them in your terminal.
100% Private Works Offline Instant
Generate dig / kdig (DoH) / PowerShell Resolve-DnsName commands to check DNS propagation of any record (A, AAAA, CNAME, MX, TXT, NS, SOA, CAA) across 20+ global public resolvers (Google, Cloudflare, Quad9, OpenDNS, AdGuard, NextDNS, Comodo, Verisign, Yandex, etc.) with region metadata. Compare expected vs actual answers (exact / contains / regex). Compute a TTL-based propagation ETA. Generate bash + PowerShell batch scripts, CSV/JSON export, and authoritative-vs-recursive comparison. 100% client-side — generates commands only; actual lookups require running them in your terminal. Everything runs locally in your browser — your data never leaves your device.
How to use
Enter your input in the tool above.
Adjust any options to your preference.
Use the Copy or Download buttons to save the result.
Everything happens locally — your data never leaves your browser.
Honesty note: DNS propagation checking requires the network. This tool generates dig / kdig (DoH) / Resolve-DnsName (PowerShell) commands for you to run in your terminal against 22+ global resolvers — it never sends queries itself. "Location" reflects the resolver's advertised region; anycast and geo-DNS mean some differences are expected, not failures.
Query A for example.com via Applied Privacy DNS (2a02:1b8:10:234::6). IPv6-preferred (2a02:1b8:10:234::6); Austrian; DoT/DoH only.
Batch scripts & exports
Privacy: All command generation, ETA computation, batch scripts, and exports run locally. History stores only metadata (action + record type + count + timestamp) — never the queried domain names.