Why "propagation" is a slightly misleading word
DNS changes do not spread outward from your nameservers. The moment you publish a record, your authoritative nameservers serve it immediately to anyone who asks.
What actually causes delay is caching. Every resolver that looked up the old record holds it until its TTL expires, and only then asks again. So the wait is not propagation but expiry, and it is bounded by the TTL you set before the change, not after it.
Reading the comparison
The tool queries Cloudflare, Google, AdGuard, NextDNS and AliDNS. When every resolver returns the same records, the change has cleared caches broadly and you can consider it live.
When they disagree, some resolvers still hold the old answer. That is expected shortly after a change and resolves itself as TTLs elapse. AliDNS is included deliberately because it resolves inside China, where results most often differ from the rest -- if it agrees with the others, propagation is genuinely broad.
Lowering TTL before a planned change
The standard practice is to reduce the record's TTL well before you make a change. If the TTL is 24 hours and you lower it to 300 seconds a day ahead, then by the time you make the actual change resolvers are only caching for five minutes.
Once the change is in place and verified, put the TTL back up. Low TTLs mean more queries against your nameservers and slightly slower lookups for users, so they are a migration tool rather than a permanent setting.
When disagreement is not about caching
Some domains return different answers to different resolvers by design. Geo-aware DNS gives each region its nearest server, so a query resolved in China and one resolved in Europe legitimately produce different addresses that will never converge.
If your domain uses a CDN or geographic load balancing, treat disagreement here as expected. What matters then is whether each answer is a valid endpoint, not whether they match.
Frequently asked questions
How long should I wait before worrying?
Until the old record's TTL has fully elapsed. If it was 3600 seconds, give it an hour from the change. Beyond that, check the record is actually published correctly at your nameservers.
Can I force resolvers to refresh?
Not in general. Some providers offer a cache-flush form for their own resolvers, but there is no way to clear the whole internet. Waiting out the TTL is the reliable answer.
Why do only some resolvers show the new value?
Each caches independently, and each started caching at a different moment. They expire at different times, so partial agreement during a transition is normal.
Does this check my own ISP's resolver?
No. It checks five large public resolvers. Your ISP's resolver caches on its own schedule, so your machine may see the old answer for longer than this tool suggests.