DNS Propagation Checker
Just changed a DNS record or moved hosting? See whether public resolvers in several countries already use the new value, compared directly with what your domain's nameserver answers.
0 of 18 resolvers give the same answer. 18 resolvers still give a different answer, usually an old cached one. The TTL column shows how long their cache has left.
Each resolver is asked over DNS-over-HTTPS from the ipku.in server, and the domain's nameserver is asked directly. Anycast resolvers answer from the site nearest our server.
| resolver | answer | ttl | time |
|---|---|---|---|
≠ Cloudflareanycast | 74.125.200.2674.125.200.27142.250.4.26142.250.4.27172.253.158.26 | 136s | 6 ms |
≠ Googleanycast | 64.233.187.2664.233.187.2774.125.203.2674.125.204.2674.125.204.27 | 300s | 6 ms |
≠ OpenDNS (Cisco)anycast | 64.233.187.2664.233.187.2774.125.203.2774.125.204.2674.125.204.27 | 300s | 3 ms |
≠ NextDNSanycast | 74.125.24.26172.217.70.27172.253.118.26172.253.118.27172.253.134.26 | 300s | 3 ms |
≠ AdGuard DNSanycast | 172.217.76.26172.217.76.27192.178.223.26192.178.223.27 | 300s | 3 ms |
≠ Control DCanada | 74.125.24.2674.125.24.27172.217.194.26172.253.118.26172.253.118.27 | 255s | 3 ms |
≠ Wikimedia DNSUnited States | 64.233.170.2664.233.170.27172.253.118.26172.253.118.27172.253.134.27 | 300s | 6 ms |
≠ DNS.SBGermany | 64.233.170.2664.233.170.27172.253.118.26172.253.118.27172.253.134.26 | 300s | 5 ms |
≠ dnsforge.deGermany | 64.233.166.2664.233.167.2664.233.167.2774.125.206.2674.125.206.27 | 300s | 196 ms |
≠ Freifunk MünchenGermany | 66.102.1.26142.251.127.26142.251.127.27142.251.168.26 | 232s | 196 ms |
≠ LibreDNSGreece | 142.251.127.26142.251.127.27 | 300s | 190 ms |
≠ Comss.oneRussia | 64.233.164.2764.233.165.2664.233.165.27142.251.1.26142.251.1.27 | 3600s | 206 ms |
≠ AliDNSChina | 74.125.136.27142.250.9.26142.250.9.27172.253.124.26172.253.124.27 | 138s | 2 ms |
≠ DNSPod (Tencent)China | 74.125.68.2774.125.130.2674.125.130.2774.125.200.2674.125.200.27 | 300s | 69 ms |
≠ 360 Secure DNSChina | 108.177.97.26108.177.125.26108.177.125.27142.250.157.26142.250.157.27 | 256s | 42 ms |
≠ IIJ Public DNSJapan | 142.251.169.26142.251.169.27172.217.221.27192.178.226.26192.178.226.27 | 300s | 69 ms |
≠ BebasIDIndonesia | 74.125.68.2774.125.130.2674.125.130.2774.125.200.2674.125.200.27 | 300s | 27 ms |
≠ TiarapIndonesia | 74.125.68.2774.125.130.2674.125.130.2774.125.200.2674.125.200.27 | 222s | 8 ms |
DNS propagation, briefly.
What is DNS propagation?
▼
After a DNS record changes, resolvers around the world keep the old answer cached until its TTL runs out. Propagation is the time until every resolver uses the new value. The change itself is live on your nameserver right away; what you wait for is caches expiring.
How long does DNS propagation take?
▼
At most the TTL of the old record, usually 5 minutes to a day. A nameserver change at the registrar can take up to 48 hours, since NS records at TLD servers like .com usually have a TTL of 1 to 2 days. Lower the TTL a few hours before a move to make the switch faster.
Why do some resolvers give a different answer?
▼
Most often an old cached answer that has not expired yet. It can also be GeoDNS or load balancing (a CDN, say), which hands out different IPs per location on purpose, or a resolver that filters certain domains.
Can I use it from a terminal?
▼
Yes. curl 'ipku.in/en/tools/dns-propagation?q=example.com&type=MX' returns every resolver's answer as plain text, and /api/propagation/example.com?type=MX returns JSON.