Global DNS Checker
Query your domain's DNS records across live vantage points in eight countries to see if global propagation is complete.
The query is performed from 10 measurement points across Turkey · US · Germany · UK · France · Japan · Singapore · India. Results are typically completed within 15 seconds.
What is a DNS propagation check?
When you modify a domain's DNS records, the update does not take effect everywhere at the same time. Recursive DNS servers cache previous answers for the duration specified by the record's TTL (Time to Live), continuing to serve cached data until that timer runs out. This tool queries your domain from real vantage points in eight countries to show exactly what resolvers see in each region. Instead of guessing, you get an accurate, real-time snapshot of your DNS status worldwide.
How to use this tool
- 1Enter your domain name (such as example.com; do not include http:// or https://).
- 2Select the DNS record type you want to inspect: A, AAAA, MX, TXT, NS, or CNAME.
- 3Wait roughly 12 seconds, then compare the records returned by each global vantage point.
How to interpret the results
When should you check DNS propagation?
After Server Migrations
You switched hosting providers and updated your A record. Check which regions are still directing traffic to the old infrastructure.
During Email Deliverability Issues
If incoming email fails, query your MX records. If certain regions still resolve outdated records, the culprit is propagation delay rather than server failure.
Adding Verification Records
When adding TXT records for Google Search Console, SPF, or DKIM, confirm that the record has propagated globally before running verification.
Common mistakes to avoid
Testing from a Single Location
Pinging a domain from your local terminal only tests your local ISP resolver's cache. Propagation issues by definition involve regional discrepancies.
Lowering TTL at the Last Minute
Lowering TTL right before migration does not help; resolvers have already cached the old duration. Lower your TTL to 300 seconds at least 24 hours in advance.
Mistaking Anycast Routing for Errors
With edge networks like Cloudflare, regional resolvers receiving different IPs is intentional, not broken. If Anycast is active, varied IPs are expected.
Frequently asked questions
How long does DNS propagation take?
It depends directly on the record's TTL setting. A typical setting is 3,600 seconds (one hour), though some providers default to 86,400 seconds (24 hours). In worst-case scenarios, full propagation can take up to 48 hours. Lowering the TTL ahead of planned changes shortens this window significantly.
Why do some countries return different IP addresses?
There are two main possibilities: either the DNS update has not reached that region yet, or your domain uses an Anycast CDN such as Cloudflare. CDNs serve the IP of the closest edge server to each probe, which is expected behavior and requires no fix.
Where are the measurement points located?
Queries are routed through ten vantage points across eight countries: Turkey, the US (3 locations), Germany, the UK, France, Japan, Singapore, and India. All run on physical probes within the RIPE Atlas network, querying their respective local resolvers.
Why is this tool better than checking from my own computer?
Queries run from your computer reflect only your ISP's local DNS cache. Because propagation delays vary across networks and geographic regions, issues can only be diagnosed by querying resolvers from multiple physical locations worldwide.
How many lookups can I perform per day?
Because tests execute across live physical hardware worldwide, fair-use limits apply. You can run up to ten queries per hour from the same IP address; site-wide daily quotas reset every 24 hours.