DNS Ping Test

Measure ICMP latency to 5 public DNS resolvers from 7 global locations at once

DNS Resolver
Netherlands
Leaseweb
France
Online
Netherlands
Worldstream
Netherlands
M247
Australia
Vultr
Germany
Kirino
England
Leaseweb
Google Public DNS
8.8.8.8 · Google
Cloudflare DNS
1.1.1.1 · Cloudflare
Quad9
9.9.9.9 · Quad9
OpenDNS Home
208.67.222.222 · Cisco
AdGuard DNS
94.140.14.14 · AdGuard
● under 60 ms● 60–120 ms● 120–200 ms● over 200 msEach cell: 4 ICMP packets, average RTT

What Does a DNS Ping Test Measure?

Every time you open a website, your device asks a DNS resolver to translate a domain name into an IP address. If that resolver is far away or congested, page loads start with a delay before a single byte of content arrives. The DNS ping test measures the ICMP round-trip time to five widely used public resolvers from seven global locations, so you can see which resolver answers fastest on each network path.

The test sends four ICMP echo requests to Google Public DNS (8.8.8.8), Cloudflare (1.1.1.1), Quad9 (9.9.9.9), OpenDNS (208.67.222.222) and AdGuard DNS (94.140.14.14) from servers in the Netherlands, France, Germany, England and Australia. Results appear cell by cell as each location finishes, and the green highlight marks the lowest average latency in every row.

How to Use the DNS Ping Test

The test needs no input. Click Start DNS Ping Test and the page automatically contacts every resolver from every location in parallel.

Step 1: Run the test

Press the start button once. Each resolver is probed sequentially on each server to keep the Looking Glass nodes responsive, so a full run usually takes a few seconds.

Step 2: Compare the columns

Each column is a test location and each row is a DNS provider. Read across a row to see how one resolver performs worldwide, or read down a column to compare providers from the location closest to you.

Step 3: Check loss and stability

A cell that shows packet loss or "No ICMP" is worth investigating. Hover any cell to see the minimum, maximum, jitter and packet loss behind the average value.

How to Read the Results

Latency under 60 ms is excellent and typical when a resolver has a nearby anycast point of presence. Between 60 and 120 ms is normal for intercontinental paths, 120 to 200 ms indicates a distant or congested route, and anything above 200 ms suggests the resolver is being reached through a long detour. Since all covered resolvers use anycast, large differences between locations usually point to routing problems rather than resolver capacity.

What the Results Cannot Tell You

Ping only measures network reachability. It does not measure DNS query time, cache hit rate, DNSSEC validation cost or filtering latency. A resolver with the lowest ping is not automatically the fastest for browsing, and a resolver that blocks ICMP can still answer DNS queries perfectly. Use this test as a shortlist and verify with real queries afterwards.

DNS Ping Test vs a Standard Ping Test

A standard ping test checks one host that you choose, such as your game server or your own website. A DNS ping test checks several fixed resolver addresses at the same time and focuses on comparing them. If you need to test a custom hostname or IP, use the main ping test. If you want to see how your target performs from many countries, use the global ping test or the regional ping tests.

Troubleshooting a Slow or Failing DNS Resolver

If one resolver is consistently slower than the others from every location, its anycast network may not have a nearby point of presence. If only one location is slow, the problem is the route between that server and the resolver. If a cell reports packet loss, run the packet loss test and the jitter test to confirm whether the issue is intermittent or persistent before changing your DNS configuration.

Frequently Asked Questions

🔍