Has your DNS change gone through?
Type a domain and pick a record type. We ask the domain’s own nameservers, then public resolvers, and tell you who already sees the new value and how long the rest may take. Free, no sign-up, and we don’t keep what you type.
Nothing checked yet
Enter a domain and a record type above. We’ll compare the nameservers with public resolvers in a few seconds.
What this checks
- What the domain’s own nameservers answer, asked directly, with the TTL they hand out.
- What Google, Cloudflare, Quad9 and our own resolver have, with the time left on each cached copy.
- How long a resolver that still has the old answer may keep it.
- One record type per check, and only nameservers at public addresses.
Why DNS changes take time (TTL)
Every DNS answer comes with a TTL, a number of seconds a resolver may keep it. Your nameservers change instantly, but a resolver that cached the old answer keeps serving it until its TTL runs out. Lower the TTL a day before a planned change to make the switch quicker.
What we keep
Only a daily count of how many checks ran and how they ended. Not the domain you typed, not your address, no cookies. To answer, the name is sent to the domain’s nameservers and to the Google, Cloudflare and Quad9 resolvers.
Questions people ask
How long does DNS propagation take?
As long as the old record’s TTL, at most. Many records have a TTL of 5 minutes to an hour. Nameserver changes at the registry can take up to two days.
Why does one resolver still show the old value?
It cached the answer before you made the change and keeps it until the TTL runs out. The Cached for column shows how long that is.
Can I make it go faster?
Not for answers that are already cached. Next time, lower the TTL a day before the change, then raise it again afterwards.
Is this a worldwide check?
No, and on purpose. Public resolvers are anycast and answer from the site closest to our server. What matters is whether your nameservers have the new value and how long caches may hold the old one.