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 3/ 20
Expected answer from Authoritative 4 name servers
Record A github.com

13 different answers. This name probably uses location-based DNS, as large sites and CDNs do: each resolver gets addresses near where it asks from. That’s expected, not a propagation problem. Compare records that don’t vary, such as MX, TXT or NS, to check a change.

MatchesServerAnswerTime
dns1.p08.nsone.net 198.51.44.8 · authoritative4.186.157.192 6ms
dns2.p08.nsone.net 198.51.45.8 · authoritative135.235.149.144 142ms
dns3.p08.nsone.net 198.51.44.72 · authoritative135.235.149.144 6ms
dns4.p08.nsone.net 198.51.45.72 · authoritative20.207.73.82 141ms
Google Public DNS 8.8.8.8 · United States (anycast)4.186.157.192 7ms
Cloudflare 1.1.1.1 · United States (anycast)140.82.114.3 3ms
Quad9 9.9.9.10 · Switzerland (anycast)135.235.149.144 3ms
OpenDNS (Cisco) 208.67.222.222 · United States (anycast)135.235.149.144 6ms
AdGuard DNS 94.140.14.140 · Cyprus (anycast)135.235.149.144 254ms
Control D 76.76.2.0 · Canada (anycast)4.187.247.160 5ms
NextDNS 45.90.28.0 · United States (anycast)4.186.157.192 2ms
UltraDNS Public 64.6.64.6 · United States (anycast)4.187.247.160 2ms
Hurricane Electric 74.82.42.42 · United States (anycast)4.236.95.112 224ms
Lumen (Level 3) 4.2.2.1 · United States (anycast)4.234.47.112 127ms
Comodo Secure DNS 8.26.56.26 · United States (anycast)20.26.156.215 147ms
SafeDNS 195.46.39.39 · United States (anycast)4.187.247.160 23ms
CIRA Canadian Shield 149.112.121.10 · Canada (anycast)140.82.114.3 265ms
CZ.NIC ODVR 193.17.47.1 · Czechia140.82.121.4 119ms
Yandex DNS 77.88.8.8 · Russia140.82.121.3 267ms
AliDNS (Alibaba) 223.5.5.5 · China (anycast)20.207.73.82 124ms
DNSPod (Tencent) 119.29.29.29 · China4.187.247.160 57ms
114DNS 114.114.114.114 · China172.182.252.133 217ms
KT 168.126.63.1 · South Korea20.200.245.247 128ms
UOL 200.221.11.100 · Brazil4.228.31.150 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