ip
ipku.in

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.

Try:google.comdetik.com
Fully propagated18/18

18 of 18 resolvers give the same answer.

The domain's nameserver answerfrom ns.detik.net.id
34.20.177.161
All records of this domain →

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.

A ns2.detik.net.id
json ↗
resolveranswerttltime
✓
Cloudflareanycast
34.20.177.161
3600s16 ms
✓
Googleanycast
34.20.177.161
3600s10 ms
✓
OpenDNS (Cisco)anycast
34.20.177.161
1727s52 ms
✓
NextDNSanycast
34.20.177.161
2163s734 ms
✓
AdGuard DNSanycast
34.20.177.161
876s659 ms
✓
Control DCanada
34.20.177.161
3600s663 ms
✓
Wikimedia DNSUnited States
34.20.177.161
3600s2212 ms
✓
DNS.SBGermany
34.20.177.161
3600s671 ms
✓
dnsforge.deGermany
34.20.177.161
2721s1209 ms
✓
Freifunk MünchenGermany
34.20.177.161
3600s1313 ms
✓
LibreDNSGreece
34.20.177.161
3600s728 ms
✓
Comss.oneRussia
34.20.177.161
8600s1741 ms
✓
AliDNSChina
34.20.177.161
3600s831 ms
✓
DNSPod (Tencent)China
34.20.177.161
3600s926 ms
✓
360 Secure DNSChina
34.20.177.161
3600s3054 ms
✓
IIJ Public DNSJapan
34.20.177.161
3600s1228 ms
✓
BebasIDIndonesia
34.20.177.161
458s620 ms
✓
TiarapIndonesia
34.20.177.161
690s160 ms
01 / faq

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.