Samprix

DNS Propagation Checker

Changed a record? See whether 20 public resolvers have the new answer yet, compared with what the domain’s own name servers say.

  • Live DNS lookup
  • Results in seconds
  • No sign-up
  • Free
Have the expected answer 19/ 20
Expected answer from Authoritative 4 name servers
Record A cloudflare.com
MatchesServerAnswerTime
ns3.cloudflare.com 162.159.0.33 · authoritative104.16.133.229104.16.132.229 2ms
ns4.cloudflare.com 162.159.1.33 · authoritative104.16.133.229104.16.132.229 2ms
ns5.cloudflare.com 162.159.9.55 · authoritative104.16.132.229104.16.133.229 2ms
ns6.cloudflare.com 162.159.3.11 · authoritative104.16.133.229104.16.132.229 2ms
Google Public DNS 8.8.8.8 · United States (anycast)104.16.133.229104.16.132.229 7ms
Cloudflare 1.1.1.1 · United States (anycast)104.16.133.229104.16.132.229 3ms
Quad9 9.9.9.10 · Switzerland (anycast)104.16.133.229104.16.132.229 3ms
OpenDNS (Cisco) 208.67.222.222 · United States (anycast)104.16.132.229104.16.133.229 3ms
AdGuard DNS 94.140.14.140 · Cyprus (anycast)104.16.132.229104.16.133.229 236ms
Control D 76.76.2.0 · Canada (anycast)104.16.133.229104.16.132.229 4ms
NextDNS 45.90.28.0 · United States (anycast)104.16.133.229104.16.132.229 2ms
UltraDNS Public 64.6.64.6 · United States (anycast)104.16.132.229104.16.133.229 3ms
Hurricane Electric 74.82.42.42 · United States (anycast)104.16.132.229104.16.133.229 353ms
Lumen (Level 3) 4.2.2.1 · United States (anycast)104.16.133.229104.16.132.229 115ms
Comodo Secure DNS 8.26.56.26 · United States (anycast)104.16.132.229104.16.133.229 131ms
SafeDNS 195.46.39.39 · United States (anycast)Timed out 997ms
CIRA Canadian Shield 149.112.121.10 · Canada (anycast)104.16.133.229104.16.132.229 267ms
CZ.NIC ODVR 193.17.47.1 · Czechia104.16.133.229104.16.132.229 128ms
Yandex DNS 77.88.8.8 · Russia104.16.132.229104.16.133.229 191ms
AliDNS (Alibaba) 223.5.5.5 · China (anycast)104.16.132.229104.16.133.229 66ms
DNSPod (Tencent) 119.29.29.29 · China104.16.133.229104.16.132.229 92ms
114DNS 114.114.114.114 · China104.16.133.229104.16.132.229 240ms
KT 168.126.63.1 · South Korea104.16.133.229104.16.132.229 121ms
UOL 200.221.11.100 · Brazil104.16.132.229104.16.133.229 295ms
Highlighted rows: the domain’s own name servers Answers cached by us for 30s

Advertisement

What this checker does

It asks the same question of two kinds of server. First, the domain’s authoritative name servers, the ones that hold the zone: their answer is the record as it is now. Then 20 public resolvers run by different companies in several countries: each keeps its own cache, so each shows what its users currently get. When they all match the authoritative answer, your change is everywhere.

Reading the results

  • Green tick: this resolver has the same answer as the authoritative servers.
  • Red cross: a different answer, usually the old record still cached. It clears when the old TTL runs out.
  • Grey circle: the resolver didn’t answer in time. One or two of these is normal; it says nothing about your domain.

Large websites and CDNs return different addresses in different places on purpose, so for their A and AAAA records, a mix of answers is expected and not a propagation problem.

Making changes take effect faster

Lower the record’s TTL (to 300 seconds, say) at least one old-TTL period before the change. Make the change, check here, then raise the TTL again. Full details: how long DNS propagation takes.

Did this tool do what you needed?

All tools