How this check works
The check asks Globalping probes on several continents to look up the same name and record type, each through the resolver its own network uses. That's the closest you can get to "what are people around the world seeing right now?" without asking them. Each row shows the probe's location and network, the answer it received, and the TTL left on that answer. Globalping measurement data, including the name you check, is public.
How to read the results
- Every location returns the new value: resolvers that cached the old record have expired it, or never had it.
- Some locations return the old value: their resolvers cached the old record and will keep serving it until its TTL runs out. The TTL shown tells you how long that will take at most.
- NXDOMAIN at some locations for a new name: those resolvers cached the fact that the name didn't exist, for as long as the zone's SOA allows. See negative caching.
- Different but valid answers everywhere: the domain may use geo-routing or a CDN that answers by location. That's by design, not a propagation problem.
The thing to know
DNS doesn't push changes outward. Your authoritative nameservers have the new value immediately, and every other resolver catches up only when its cached copy expires. So the longest wait is the old record's TTL. To make changes take effect quickly, lower the TTL at least one old-TTL period before the change. The DNS propagation guide walks through the timing, and DNS Name Lookup shows the record's current TTL.
Updated 26 October 2026