Check whether your A, MX and NS records have spread across Cloudflare, Google and Quad9 resolvers worldwide.
When you change a DNS record — for example, pointing your domain at a new web host or mail provider — that change is published on your domain's authoritative nameservers immediately, but the rest of the internet does not see it instantly. Resolvers operated by ISPs, public DNS services and companies cache your old records and keep serving them until the cache expires. This tool asks three independent public resolvers — Cloudflare, Google and Quad9 — for your domain's A, MX and NS records over DNS-over-HTTPS, and lines their answers up in one table so you can see at a glance whether they agree yet.
Read the table row by row. The A row shows the IP address your website resolves to: if all three resolvers show your new server's IP, visitors reaching your site through those resolvers will land on the new host. The MX row shows your mail servers, with a priority number in front of each (lower means preferred) — mail will flow to the lowest-priority reachable server, so a stale MX row is how email keeps arriving at an old provider after a move. The NS row shows which nameservers are authoritative for your domain; if you recently changed nameservers, this row is the one that takes longest to settle everywhere, because parent-zone and resolver caches for NS records tend to be long-lived.
A note on how the lookup itself works: the queries go over DNS-over-HTTPS (DoH) rather than the server's built-in DNS resolver. The built-in resolver truncates large DNS answers, which once made genuine records appear missing on this site. DoH returns the full answer set, and the built-in resolver is used only as a last resort if all three DoH endpoints fail. Every check runs fresh against live DNS at the moment you click — nothing here is cached by us.
Propagation is the time it takes for a DNS change to reach resolvers worldwide. There is no central switch: each resolver caches your old records and only re-queries your nameservers once its cached copy expires. Most changes settle within a few hours, but with a long TTL it can take up to 48 hours before the last stragglers catch up.
TTL (time to live) is the number of seconds resolvers are allowed to cache a record, set in your DNS zone. A TTL of 3600 means up to one hour of old answers after a change; 86400 means up to a day. Before a planned move, lower your TTL to 300 (five minutes) at least a day ahead, make the change, then raise it again afterwards for faster everyday lookups.
Each resolver cached your records at a different moment, so each expires its old copy at a different time. Disagreement right after a change is expected and not a sign that anything is broken — it simply means some resolvers have refreshed and others have not yet. It can also reflect a genuine problem, such as one nameserver serving different data from the others, which is worth investigating if the disagreement lasts beyond the TTL.
First, confirm the new record is correct on your authoritative nameservers — a resolver cannot show what was never published. Then wait out the TTL: there is no way to force a public resolver to flush someone else's cache. If the old value persists well past the TTL, check for a second, forgotten copy of the record (for example at your old host or registrar) and make sure all of your nameservers serve identical zones.
No — it only reads public DNS records. To change records, edit the DNS zone at your registrar or DNS host, then use this tool to watch the new values spread.
XYZREG makes it easy to search, register and transfer domain names at transparent yearly prices, with .com domains from only $11.99/yr. Manage DNS, protect your WHOIS privacy, and use free online tools including WHOIS lookup, DNS lookup, IP lookup and SSL checker - no account required.