DNS Propagation Checker Reference
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.
About DNS Propagation Checker Reference
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.
FAQ
Does this tool perform live DNS propagation checks?
No. DNS propagation checks require the network — and this tool is 100% client-side, so it generates the exact `dig`, `kdig` (DNS-over-HTTPS), and PowerShell `Resolve-DnsName` commands for you to copy and run in your terminal against 20+ global public resolvers (Google, Cloudflare, Quad9, OpenDNS, AdGuard, NextDNS, Comodo, Verisign, Yandex, etc.). The resolver list, region metadata, expected-value matcher, TTL-based ETA, and batch scripts all work offline. "Location" reflects the resolver's advertised region — anycast and geo-DNS mean some differences are expected, not failures.
How does expected-value matching work?
You enter the value you expect every resolver to return (e.g. `93.184.216.34` for an A record) and pick a matcher: exact (the answer must equal your expected value), contains (your expected value must appear in the answer set — useful for round-robin / multi-value records), or regex (the answer is tested against a JavaScript regex). The tool then emits a comparison one-liner per resolver — typically a `dig +short | grep` chain for bash or a `Resolve-DnsName | Where-Object` chain for PowerShell — so you can paste the batch and immediately see which resolvers have propagated and which are stale.
How is the propagation ETA computed?
Enter the record's TTL (in seconds, e.g. 3600 for 1 hour) and the tool computes the worst-case ETA as the time it takes the slowest caching resolver to expire its old answer. For example, a 3600s TTL means up to 1 hour after the authoritative change for every recursive resolver to refresh. The tool also reports the 50th-percentile ETA (about half the TTL) as a typical propagation time, and a 95th-percentile ETA (about 2× the TTL) for slow stragglers. These are statistical estimates based on RFC 1035 TTL semantics — actual propagation depends on resolver behavior, DNSSEC validation, and anycast routing.
Why do some resolvers return different answers and not count as failures?
Anycast (the same IP announced from many locations), geo-DNS (different answers per region), and CDN routing (different IPs per resolver's perceived geography) all mean legitimate differences across resolvers. The tool flags every difference from your expected value but separates "differs" from "unreachable" (NXDOMAIN, SERVFAIL, timeout). When you see a difference, check the resolver's region and consider whether CDN/geo-DNS could legitimately explain it before treating it as a propagation failure.
What extra features does this tool have versus other propagation checkers?
(1) 20+ global public resolver presets with region metadata (Google, Cloudflare, Quad9, OpenDNS, AdGuard, NextDNS, Comodo, Verisign, Yandex, Control D, Mullvad, etc.). (2) 8 record types (A, AAAA, CNAME, MX, TXT, NS, SOA, CAA). (3) dig / kdig (DoH) / PowerShell Resolve-DnsName command variants. (4) Expected-value matcher (exact / contains / regex). (5) TTL-based propagation ETA (50th/95th/worst case). (6) Authoritative vs recursive comparison command. (7) Bash batch script generator. (8) PowerShell batch script generator. (9) CSV export of the command plan. (10) JSON export of the command plan. (11) Region filter (run only resolvers in selected regions). (12) Add custom resolver. (13) Copy-to-clipboard per command. (14) localStorage history (max 20). (15) Shareable URL. 100% client-side — never sends queries itself.
Related tools
.bashrc / .zshrc Alias & Config Manager
Build shell aliases, functions, exports, and PATH edits in a visual editor, then export a clean, commented .aliases file sourced from both .bashrc and .zshrc — with shadowing detection against shell builtins and common CLI tools, function suggestions when args are needed, starter packs (git, docker, kubectl, navigation, safety, ls, dev, devops, data science), import of existing rc files, dedupe, history (localStorage), and shareable URL. 100% client-side.
Add / Subtract Date Calculator
Add or subtract years, months, weeks, days, hours, minutes and seconds from a starting date/time. Calendar-day or business-day mode with custom weekend + holiday list. Month-end policy toggle (clamp to last day vs overflow). Repeat/series mode (e.g. every 2 weeks x 10) with CSV export. Shareable URL. 100% client-side.
Age Calculator
Calculate exact age from a birth date in calendar years/months/days (no negative-day bugs) plus totals in months/weeks/days/hours/minutes/seconds. Next-birthday countdown with weekday. Feb-29 birthday policy toggle. Milestones (1,000 days, 10,000 days, 1 billion seconds). Zodiac sign + Chinese zodiac. Age gap comparison. Shareable URL. 100% client-side.