DNS propagation checker
See what public resolvers answer for a record right now, so you know whether a DNS change has reached everyone.
How it works
We ask every resolver in the list for the same record at the same moment, then group identical answers so differences stand out.
- 1Pick the recordA or AAAA for a website, MX for email, NS after moving DNS host, TXT for verification codes.
- 2Compare answersThe majority answer is marked and anything different is flagged. A resolver that doesn't reply is shown as “Couldn't check” and not counted.
- 3Read the TTLThe time to live left on an old answer is the longest you'll wait for that resolver to update.
Worked example: moving example.com to a new server
Lowering the TTL to 300 s a day before the change would have finished the switch in about 5 minutes.
Frequently asked questions
How long does DNS propagation take?
As long as the old record's TTL: often 5 minutes to an hour. Changing nameservers takes longer, commonly up to 48 hours, because the registry's own records are cached for days.
Why do resolvers show different answers?
Each one cached the record at a different moment, so each one's copy expires at a different time. Some also serve a stale copy briefly while they fetch a new one.
Can I make it faster?
Only in advance: lower the TTL a day before the change. After the change you can't clear other people's caches, though some public resolvers have a page to refresh one name.
Why does my computer still show the old site?
Your browser, operating system and router keep their own copies. If every resolver here shows the new answer, restart the browser or clear your system's DNS cache.
Which record type should I check?
A and AAAA for where a website points, CNAME for aliases like www, MX for email, NS after changing DNS provider, and TXT for verification and email security records.