whohostsitHas your DNS
change spread?
Ask six public DNS resolvers for the same record and compare their answers.
Use it after moving hosts or changing nameservers.
Six resolvers. One answer?
Each resolver’s answer and TTL, and whether it matches the others, appear here.
PUBLIC DATA. ONE SIMPLE LOOKUP.What DNS propagation really is
DNS changes don’t travel anywhere. Resolvers keep each answer in their cache for the record’s TTL, so after you change a record some of them keep returning the old value until their cached copy expires.
This checker asks six public DNS resolvers at once and highlights any that disagree. If they all show the new value, most visitors will see it too, though your own computer and network may hold the old answer a little longer.
Common questions
How long does DNS propagation take?
Usually minutes to a few hours, depending on the old record’s TTL. Nameserver changes can take up to 48 hours because the registry’s NS records have long TTLs.
How can I speed up DNS propagation?
Lower the record’s TTL, for example to 300 seconds, a day before you make the change. Once the change has spread, you can raise it again.
Does this check DNS from different countries?
Not directly. These resolvers use anycast, so you reach the location nearest to you. It compares the caches of independent DNS networks, which is what matters for most changes.