No test yet. Select Start to begin.

Compare how carriers in each region resolve the same domain

No test yet. Select Start to begin.

Global latency distribution

Timeout > 250ms 101ms - 250ms 51ms - 100ms <= 50ms
Timeout > 250ms 101ms - 250ms 51ms - 100ms <= 50ms
Region / ISPFastestSlowestAverage

DNS resolution statistics

DNS results

Test node Target Type DNS results IP location Records Details Latency

Comparing DNS answers

Run the same record query from different locations to compare returned values and response times. CDNs and geographic routing can intentionally return different addresses.

A multi-location DNS lookup resolves the same domain from nodes around the world and from carriers in mainland China at once, then lists the A and AAAA answers, the location of each IP and the response time. It shows how far a DNS change has propagated and whether one region resolves differently from the rest.

Different answers are expected when a domain uses a CDN or GeoDNS. Answers that point to unrelated or reserved addresses in only some regions can indicate DNS poisoning or hijacking.

Frequently asked questions

Why do I still see the old record?

A recursive resolver may still have the previous answer cached until its TTL expires. Check the authoritative servers and compare more than one resolver.

How long does a DNS change take to propagate?

It depends on the TTL of the old record. With a TTL of 600 seconds, resolvers cache the old answer for at most 10 minutes, so most regions update within about 15 minutes. With a TTL of 86,400 seconds, it can take a full day. Lower the TTL in advance before changing an IP address.

What is DNS poisoning and how can I spot it?

DNS poisoning happens when a device on the path answers a query first with a forged IP. Signs include answers that do not belong to the domain, such as reserved or unrelated overseas addresses, and that do not match the authoritative DNS. Encrypted DNS (DoH or DoT) avoids most poisoning.

Why is DNS resolution slow in some regions?

The recursive resolver in that region may need to query a distant authoritative server, or the carrier’s resolver may be overloaded. Using a DNS provider with servers in the region or a longer TTL reduces lookups to the origin.

This page has expired
The page verification expired. Refresh the page and try again.