DNS propagation checker
When you change a DNS record, the new answer does not reach everyone at once. Each network keeps the old answer until its timer (the TTL) runs out. This tool asks DNS from fifteen places and shows what each one says.
If every place gives the same answer, the change has spread. If they differ, some networks are still holding the old answer and will catch up soon.
How to read the results
- Same answer everywhere means the change has fully spread, or nothing was changed.
- Different answers mean some networks still have the old record cached. Wait for the TTL to pass and check again.
- TTL is how many seconds a network may keep the answer. A low TTL before a change makes the move faster.
- No answer in one place can be a temporary hiccup on that probe. Try again before worrying.
Questions
How long does DNS propagation take?
Usually minutes to a few hours, and rarely up to 48 hours if the old record had a very long TTL. Our DNS propagation guide explains why.
Why does my own computer still show the old address?
Your device and your internet provider also cache answers. Clearing your own cache can help: see how to flush your DNS cache.
Can I lower the TTL to speed things up?
Yes, but it only helps if you lower it before you make the change, because networks keep the old TTL until it expires.
Related guides
More free tools
- DNS lookup
- HTTP header checker
- SSL certificate checker
- Redirect checker
- WHOIS and domain expiry
- MX record lookup
- Robots.txt checker
- Security headers checker
- Ping test from around the world
- Traceroute from around the world
Results are a snapshot taken from our servers at the moment you ask, and can differ from what you see elsewhere. siteupdown.com tests public websites only. Spotted a problem?