NexaYori Webmaster DNS propagationHelp
DNS propagation

4 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
3 ms · TTL 42s
Match
140.82.114.3
Google
84 ms · TTL 60s
Match
140.82.114.3
Quad9
249 ms · TTL 19s
Differs
140.82.112.4
OpenDNS (Cisco)
94 ms · TTL 60s
Match
140.82.114.3
AdGuard (unfiltered)
395 ms · TTL 60s
Match
140.82.114.3
Control D
115 ms · TTL 22s
Match
140.82.114.3
Mullvad
607 ms · TTL 42s
Differs
20.26.156.215
DNS.SB
1283 ms · TTL 50s
Differs
140.82.112.4
AliDNS
562 ms · TTL 1s
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"