DNS Propagation Checker
Fast, accurate and free online dns propagation checker tool running directly in your browser.
-
1Enter data
Enter content, paste text or load a file from disk. -
2Click the button
The tool will immediately process your data in the browser. -
3Get the result
Copy the finished text or save the file to your device.
return "Result ready in 0.1s";
}
DNS Propagation Checker
Check the propagation of a selected DNS record across popular resolver servers.
Results
Legend
- Found - the record has propagated to this resolver.
- Missing - the resolver does not return the record yet.
- Error - the query failed or timed out.
The tool queries popular DNS resolvers (such as Google and Cloudflare) and reports whether the record is visible.
Rate this tool:
Related tools
Other tools you may find usefulDns Propagation Checker: Why is your website still not working and how to check it?
You changed A records, reconnected the server at the registrar, and the client calls with complaints that he sees an old version of the website? This is a classic DNS propagation problem. In my opinion, there is nothing more frustrating in the work of a webmaster than waiting "blindly". That's why I created this tool - so you can see in a second what the world sees.
What exactly is DNS propagation?
Imagine that DNS is a huge, global phone book. When you change hosting, you change your "phone number" (IP address). However, this book does not magically update everywhere at the same time. Thousands of servers around the world (resolvers) store old data in cache to serve results faster to users. The time it takes for all these servers to "learn" about the change is calledpropagation.
From my experience, this process takes from a few minutes to up to 48 hours. Sounds like forever? Yes, especially when you are pressed for deadlines. OurDns Propagation Checkerpolls servers in various locations, showing you the status of operations in real time.
How to use our tester?
I designed this interface to be as raw and specific as possible. There are no unnecessary bells and whistles, but pure diagnostic information.
1. Enter the domain
Enter the address in theDomainfield. You don't need to add protocols like http://. The tool automatically validates the correctness of the entry thanks to the built-in regular expression.
2. Select the record type
This is the key moment. If you are checking to see if the page is pointing to a new server, selectA. If you are waiting for mail, selectMX. We support the most popular types: A, AAAA, CNAME, MX, NS, TXT.
Technical Analysis: What's Happening Under the Hood?
As the author of this tool, I want to show you that it is not just a simple script. In the backend (PHP/Livewire) I implemented theDnsPropagationHelperclass, which queries a predefined list of global resolvers.
Important technical note:The tool also measureslatency(delay) in milliseconds. If you see a result of 20ms, it means that the DNS server responded quickly. If you see "—", there is probably a timeout or connection error.
Supported record types – what do you need to know?
- A Record (Address):Maps a domain name to an IPv4 address. This is where you most often visit when changing hosting.
- AAAA Record:Same as above, but for modern IPv6.
- CNAME (Canonical Name) record:Alias for another domain. Often used for CDN services (Cloudflare) or e-commerce platforms (Shopify).
- MX (Mail Exchange) record:Responsible for email routing. If you mess it up, your emails will simply disappear into the void.
- NS (Name Server) record:Indicates which DNS servers manage your domain.
- TXT record:Most often used to verify domain ownership (e.g. in Google Search Console) or email security settings (SPF, DKIM).
Color legend – how to read the results?
I don't like wasting time reading long tables, so I introduced a color coding system:
- Green (OK):The record was found and downloaded successfully.
- Yellow (MISS):The DNS server responded but did not find any data for this record. This may mean the record hasn't gotten there yet.
- Red (ERROR):A communication error occurred with the resolver.
Why is DNS "so slow"? My observations
I often hear the question: "Why does my friend's website on another network already work, but not mine?" The answer lies in theTTL (Time To Live)parameter. This is the time (expressed in seconds) for which a given record is to be kept in the cache.
If you had TTL set to 86400 (24 hours) before changing the IP, most of the world will be able to see your old server 24 hours a day. My advice is always:reduce the TTL to 300 seconds the day before you plan to migrate. This is a trick that saves a lot of stress and phone calls from impatient customers.
Common errors when checking propagation
Sometimes the tool says "OK" and you still see the old stuff in the browser. Why? Because your own browser and your operating system (Windows/macOS) also have their own DNS cache! In this case, try theipconfig /flushdnscommand in the console. If that doesn't help, our tester is the final proof whether the problem is with the global network or just your computer.
Advantages of the tool
- Speed thanks to Livewire (no page reload).
- Polling real world servers.
- No tracking - we respect your privacy.
- Validating domain syntax on the fly.
When to use?
- After changing VPS/Dedicated server.
- When configuring external email (e.g. Google Workspace).
- When implementing an SSL certificate (TXT verification).
- When you suspect a failure at your DNS provider.