DNS propagation checker
Changed an A, CNAME, NS or MX record? Ask 20 public DNS resolvers what they answer right now, and see how far your change has spread.
Moving a site? Use the migration checklist
Every step from lowering the TTL to checking email after the switch, on one printable page. With a free account you keep your preview links in one place and run a QA report of the site on the new server.
What this tool checks
DNSPeek sends the same question, for example “what is the A record of example.com?”, to 20 public resolvers in parallel from DNSPeek’s server and shows each answer with its remaining TTL where the resolver reports one. Enter the value you expect after your change, such as the new server’s IP, and every resolver is marked as already updated or not yet, with the share that has the new value.
Without an expected value, the tool shows whether resolvers agree: useful to spot a change that only some of them have picked up. Answers that differ only because the site rotates addresses or answers by location (same network, such as one Cloudflare or Google network) count as consistent. The tool also says when the name does not exist, when it has no record of the type you asked for, and when DNSSEC validation fails.
How to read the result
A green row returns the expected value; a red row still returns something else or did not answer in time. The TTL is how many more seconds that resolver may keep its cached answer, so a resolver showing the old IP with a TTL of 120 will ask again within two minutes. The highest TTL among the old answers tells you the longest you may still have to wait.
Record types
A and AAAA point a name at an IPv4 or IPv6 address, CNAME points it at another name, NS names the servers responsible for the zone (check it after moving DNS to a new provider), MX routes email and TXT holds verification and SPF records.
Before you switch, you can test the site on the new server with a preview link. The full guide is in the docs: Check DNS propagation.
Frequently asked questions
How long does DNS propagation take?
Usually minutes to a few hours. Each resolver keeps the old answer until its cached copy expires, which is at most the TTL the old record had. A record with a TTL of 3600 seconds can take up to an hour to change everywhere; a lowered TTL of 300 seconds takes about five minutes.
Why do some resolvers still show the old IP?
They cached the old record before you changed it and will keep it until its TTL runs out. Nothing is wrong unless a resolver still shows the old value well after the old TTL has passed, which usually means the record was changed in the wrong place, for example at the registrar instead of the DNS provider that is actually in use.
Which resolvers does this tool ask?
Twenty public resolvers run by Google, Cloudflare, Quad9, OpenDNS, AdGuard, Lumen, UltraDNS, Yandex, CleanBrowsing, NextDNS, Control D, DNS4EU, CIRA Canadian Shield, HiNet, AliDNS, Hurricane Electric, Gcore, DNS.SB, dnsforge.de and KT, with home regions in North America, Europe and Asia. They are asked from DNSPeek’s server: the big anycast resolvers answer from their location nearest to it, so the check shows what public DNS returns, not what a visitor in every country sees.
When is a domain counted as propagated?
When at least 90% of the resolvers that answered return the value you expect, and at least half of all resolvers answered. Resolvers that time out are left out of the percentage, so one unreachable resolver cannot hold the result back. If the value you expect is a Cloudflare address, any Cloudflare address counts.
Why do resolvers show different Cloudflare IPs?
Cloudflare answers with the address of an edge server near each resolver (anycast), so resolvers in different regions get different Cloudflare IPs, such as 188.114.96.3, 104.21.66.63 or 172.67.201.135, for the same site. That is normal. When the IP you expect is a Cloudflare address, DNSPeek counts a resolver as matched when every address it returns belongs to Cloudflare’s published ranges, not only when it returns that exact IP.
I use Cloudflare proxy — how do I check my migration?
With the proxy on (orange cloud), public DNS shows only Cloudflare’s addresses and hides your origin server. When you change the origin IP inside Cloudflare, DNS does not change at all and Cloudflare applies the new origin within seconds, so a DNS check cannot show that switch. Check the new server directly instead: “Is my domain switched?” asks your new IP for the site, and a DNSPeek preview link with the new IP as the target shows the whole site from that server before you change anything in Cloudflare.
Can I get an email when propagation is done?
Yes. Create a DNSPeek preview link for the domain and the new server IP, then turn on “Alert me when DNS has propagated” in the link settings. DNSPeek checks every 5 minutes and emails you once the domain has propagated. Alerts are part of the Pro plan.
Moving a site to a new server?
See the site on the new server before you change DNS: DNSPeek gives you one HTTPS preview link that works on any device and that you can share with your team or client. No hosts file, no VPN.
Create a free preview link