DNS probes / ICMP

Every answer
starts somewhere.

Compare DNS lookup and ICMP ping measurements to public resolver addresses from Stealth’s New York City network.

Explore measurements
01 / The latest observations

A signal from
each address.

See how public DNS resolvers respond over IPv4 and IPv6, with ping and DNS lookup measurements from our New York City network.

Ping responding30 / 30Addresses responding to ping
DNS responding30 / 30Addresses answering the DNS check
PING Responsive Rate100.0%Latest confirmed checks
DNS Responsive Rate100.0%Latest confirmed checks
Unconfirmed0 / 60Ping and DNS checks without a current result
ICMP / Measurement history

A view over time.

Checks run every 30 seconds. The chart shows recorded successful checks at their actual measurement times; missing observations remain gaps.

Choose a measurement
ICMP RTT / Milliseconds

Rolling 24 hours · UTC

Waiting for observations.

Waiting for observations.

Click or tap anywhere on the chart to inspect the nearest sample time. Drag across the chart to zoom; on touchscreens, first select a time range. Use the arrow keys to inspect sample times. Missing observations remain gaps.

History requires JavaScript and an available monitoring feed.

Time / UTC
Select a point to inspect its measurement.
Choose addresses 30 selected
View observations as a table

Sampling times use the selected timezone. Empty values mean no qualifying successful ping was available for that point.

Sample time / UTCAddressICMP round trip / ms
History is not available.
ICMP / Round-trip time

Public resolver addresses

Measurements available.

30 addresses shown

Public resolver

Cloudflare

12 addresses
Standard1.1.1.1IPV4
Responding1.23 msChecked 01 Nov 19:53:09 UTC
Standard1.0.0.1IPV4
Responding1.24 msChecked 01 Nov 19:53:13 UTC
Standard2606:4700:4700::1111IPV6
Responding0.93 msChecked 01 Nov 19:53:13 UTC
Standard2606:4700:4700::1001IPV6
Responding1.28 msChecked 01 Nov 19:53:01 UTC
Malware blocking1.1.1.2IPV4
Responding3.09 msChecked 01 Nov 19:53:13 UTC
Malware blocking1.0.0.2IPV4
Responding2.42 msChecked 01 Nov 19:53:21 UTC
Malware blocking2606:4700:4700::1112IPV6
Responding1.21 msChecked 01 Nov 19:53:27 UTC
Malware blocking2606:4700:4700::1002IPV6
Responding1.60 msChecked 01 Nov 19:53:10 UTC
Malware & adult content blocking1.1.1.3IPV4
Responding1.51 msChecked 01 Nov 19:53:10 UTC
Malware & adult content blocking1.0.0.3IPV4
Responding1.02 msChecked 01 Nov 19:53:25 UTC
Malware & adult content blocking2606:4700:4700::1113IPV6
Responding1.38 msChecked 01 Nov 19:53:17 UTC
Malware & adult content blocking2606:4700:4700::1003IPV6
Responding1.37 msChecked 01 Nov 19:53:15 UTC
Public resolver

Google Public DNS

4 addresses
Standard8.8.8.8IPV4
Responding0.49 msChecked 01 Nov 19:53:05 UTC
Standard8.8.4.4IPV4
Responding0.60 msChecked 01 Nov 19:53:25 UTC
Standard2001:4860:4860::8888IPV6
Responding0.47 msChecked 01 Nov 19:53:26 UTC
Standard2001:4860:4860::8844IPV6
Responding0.76 msChecked 01 Nov 19:53:07 UTC
Public resolver

Quad9

4 addresses
Secured9.9.9.9IPV4
Responding1.00 msChecked 01 Nov 19:53:10 UTC
Secured149.112.112.112IPV4
Responding0.46 msChecked 01 Nov 19:53:14 UTC
Secured2620:fe::feIPV6
Responding0.65 msChecked 01 Nov 19:52:59 UTC
Secured2620:fe::9IPV6
Responding0.55 msChecked 01 Nov 19:53:02 UTC
Public resolver

AdGuard DNS

4 addresses
Default94.140.14.14IPV4
Responding1.44 msChecked 01 Nov 19:52:58 UTC
Default94.140.15.15IPV4
Responding1.45 msChecked 01 Nov 19:53:23 UTC
Default2a10:50c0::ad1:ffIPV6
Responding25.73 msChecked 01 Nov 19:53:19 UTC
Default2a10:50c0::ad2:ffIPV6
Responding25.78 msChecked 01 Nov 19:53:20 UTC
Public resolver

OpenDNS

2 addresses
FamilyShield208.67.222.123IPV4
Responding0.66 msChecked 01 Nov 19:53:21 UTC
FamilyShield208.67.220.123IPV4
Responding0.66 msChecked 01 Nov 19:53:25 UTC
Public resolver

CleanBrowsing

4 addresses
Family185.228.168.168IPV4
Responding1.23 msChecked 01 Nov 19:52:58 UTC
Family185.228.169.168IPV4
Responding1.29 msChecked 01 Nov 19:53:20 UTC
Family2a0d:2a00:1::IPV6
Responding1.39 msChecked 01 Nov 19:53:27 UTC
Family2a0d:2a00:2::IPV6
Responding1.39 msChecked 01 Nov 19:53:15 UTC

Snapshot retrieved 01 Nov 2026 19:53:28 UTC. A page refresh does not make an older measurement current.

02 / Reading the measurements

One useful signal.
A wider picture.

Each address is checked every 30 seconds. Ping uses ICMP and measures round-trip time from our New York City monitoring point to the responding address and back.

DNS lookup sends an example.com A query over UDP port 53. A successful check receives a NOERROR response containing at least one A answer. The duration measures the DNS request and response after socket setup; it does not test DNS over TCP, DNS over TLS, or DNS over HTTPS. A resolver may answer from cache, and a single query is not a comprehensive DNS benchmark.

Public DNS providers often use anycast, so results can vary by location, network path and time. A response here is not a guarantee of resolver availability or lookup speed for every user. Some services may not answer ICMP at all.

Looking for a resolver that fits your needs? Read our public DNS guide .