NexaYori Tools DNS propagationHelp
DNS propagation

6 of 9 resolvers give a different answer github.com A

Large sites and CDNs hand out different addresses on purpose, by location or in rotation, so A/AAAA differences aren’t always a problem. Compare SOA serials to check whether a zone change has propagated.

ResolverAnswer
Cloudflare
4 ms · TTL 60s
Differs
140.82.113.4
Google
82 ms · TTL 60s
Differs
140.82.112.3
Quad9
172 ms · TTL 45s
Differs
140.82.112.4
OpenDNS (Cisco)
99 ms · TTL 60s
Match
140.82.114.4
AdGuard (unfiltered)
113 ms · TTL 60s
Match
140.82.114.4
Control D
68 ms · TTL 24s
Match
140.82.114.4
Mullvad
279 ms · TTL 11s
Differs
20.26.156.215
DNS.SB
281 ms · TTL 38s
Differs
140.82.112.3
AliDNS
346 ms · TTL 5s
Differs
140.82.116.3
Each resolver caches answers until their TTL expires, so a recent change can take up to that long to show everywhere. Terminal: curl "…/propagation?q=example.com&type=MX"