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
What the propagation check shows
20 public resolvers
Google, Cloudflare, Quad9 and 17 more operators in several countries.
The source of truth
Your own name servers’ answer, to compare every resolver against.
Who has the change
Match, different or no answer, for each resolver.
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.
Frequently asked questions
What is DNS propagation?
Nothing is pushed out when you change a record. Resolvers around the world cache the old answer for as long as its TTL allows, then ask again and get the new one. “Propagation” is that cache expiring, resolver by resolver.
How long does DNS propagation take?
Up to the record’s old TTL, often one hour and at most a day or two. Changing name servers at the registrar takes longer, because the TLD’s own NS records commonly have a TTL of 48 hours. See our guide for how to make planned changes take effect in minutes.
Which answer is the right one?
The one from the domain’s authoritative name servers, shown at the top. They hold the record itself; every other resolver is showing a copy. If the authoritative answer is wrong, the change hasn’t been saved at your DNS host.
Why do the resolvers show different answers even after hours?
Some answers differ on purpose: big sites and CDNs give different IP addresses depending on where you ask from. If the authoritative servers themselves disagree, the zone isn’t synchronised between them, which your DNS host needs to fix.
Are these servers really in those countries?
The country is where each operator is based. Most large resolvers are anycast: one address served from many locations, and we reach the site nearest our server. They are still separate caches run by separate companies, which is what shows whether an old answer is still out there.