DNS Propagation Checker
See whether a DNS change has spread to resolvers. Free, no sign-up
What the results mean
- Same as most: this resolver gives the answer most of them give.
- Different: it gives another answer — often the old one, still in its cache from before a change.
- No majority: the answers are split evenly, so none of them is "most".
- NXDOMAIN: the resolver answered that the name does not exist.
- No answer: the resolver did not answer in time, could not be reached, or sent something that was not an answer. That says nothing about your domain.
Agreement shows what these resolvers answer now. It cannot show that every resolver in the world has your change: there are a great many of them, each with its own cache.
Questions about this tool
How long does DNS propagation take?
A change does not travel anywhere: each resolver keeps the answer it has until its TTL runs out, then asks the domain's nameservers again. So a changed record reaches every resolver within the old record's TTL — often minutes, sometimes hours. A change of nameservers can take a day or two, because the servers of a domain ending hand out nameserver records with long TTLs.
Why do resolvers give different answers?
Each keeps its own cache. One that asked before your change still holds the old answer; one that asked after it has the new one. A name that answers differently by place, as many content delivery networks do, can also give different addresses to different resolvers.
Where are the resolvers asked from?
Every resolver is asked from this website's server, over DNS over HTTPS. One marked worldwide (anycast) answers from its location nearest to that server, so this shows what each service answers, not what every country sees.
What does "No answer" mean?
The resolver did not reply in time, could not be reached, or sent something that was not a DNS answer. It is a failure of the question, not a sign that your record is missing. Ask again in a minute.
Can I make a change reach resolvers sooner?
Lower the record's TTL a day before you change it, so resolvers keep the old answer for less time, and raise it again afterwards. Google Public DNS and Cloudflare each also have a page where you can ask them to forget a name they have cached.