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 responding26 / 26Addresses responding to ping
DNS responding26 / 26Addresses answering the DNS check
PING Responsive Rate100.0%Latest confirmed checks
DNS Responsive Rate100.0%Latest confirmed checks
Unconfirmed0 / 52Ping 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.

ICMP RTT / Milliseconds

Rolling 24 hours · UTC

Show

ICMPDNS lookup

Waiting for observations.

Waiting for observations.

Click or tap anywhere on the chart to inspect the nearest sample time. Drag with a mouse to zoom, or use the time buttons. 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 26 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.

26 addresses shown

Public resolver

Cloudflare

12 addresses
Standard1.1.1.1IPV4
ICMPResponding1.60 msChecked 22 Nov 12:27:09 UTC
Standard1.0.0.1IPV4
ICMPResponding1.35 msChecked 22 Nov 12:27:13 UTC
Standard2606:4700:4700::1111IPV6
ICMPResponding1.19 msChecked 22 Nov 12:27:13 UTC
Standard2606:4700:4700::1001IPV6
ICMPResponding0.89 msChecked 22 Nov 12:27:01 UTC
Malware blocking1.1.1.2IPV4
ICMPResponding1.08 msChecked 22 Nov 12:27:13 UTC
Malware blocking1.0.0.2IPV4
ICMPResponding1.55 msChecked 22 Nov 12:26:51 UTC
Malware blocking2606:4700:4700::1112IPV6
ICMPResponding1.22 msChecked 22 Nov 12:26:57 UTC
Malware blocking2606:4700:4700::1002IPV6
ICMPResponding1.55 msChecked 22 Nov 12:27:10 UTC
Malware & adult content blocking1.1.1.3IPV4
ICMPResponding1.36 msChecked 22 Nov 12:27:10 UTC
Malware & adult content blocking1.0.0.3IPV4
ICMPResponding1.47 msChecked 22 Nov 12:26:55 UTC
Malware & adult content blocking2606:4700:4700::1113IPV6
ICMPResponding1.02 msChecked 22 Nov 12:26:47 UTC
Malware & adult content blocking2606:4700:4700::1003IPV6
ICMPResponding1.41 msChecked 22 Nov 12:27:15 UTC
Public resolver

Google Public DNS

4 addresses
Standard8.8.8.8IPV4
ICMPResponding0.43 msChecked 22 Nov 12:27:05 UTC
Standard8.8.4.4IPV4
ICMPResponding0.58 msChecked 22 Nov 12:26:55 UTC
Standard2001:4860:4860::8888IPV6
ICMPResponding0.81 msChecked 22 Nov 12:26:56 UTC
Standard2001:4860:4860::8844IPV6
ICMPResponding0.79 msChecked 22 Nov 12:27:07 UTC
Public resolver

Quad9

4 addresses
Secured9.9.9.9IPV4
ICMPResponding1.01 msChecked 22 Nov 12:27:10 UTC
Secured149.112.112.112IPV4
ICMPResponding0.46 msChecked 22 Nov 12:27:14 UTC
Secured2620:fe::feIPV6
ICMPResponding0.65 msChecked 22 Nov 12:26:59 UTC
Secured2620:fe::9IPV6
ICMPResponding0.49 msChecked 22 Nov 12:27:02 UTC
Public resolver

OpenDNS

2 addresses
FamilyShield208.67.222.123IPV4
ICMPResponding0.71 msChecked 22 Nov 12:26:51 UTC
FamilyShield208.67.220.123IPV4
ICMPResponding0.73 msChecked 22 Nov 12:26:55 UTC
Public resolver

CleanBrowsing

4 addresses
Family185.228.168.168IPV4
ICMPResponding1.26 msChecked 22 Nov 12:26:58 UTC
Family185.228.169.168IPV4
ICMPResponding1.30 msChecked 22 Nov 12:26:50 UTC
Family2a0d:2a00:1::IPV6
ICMPResponding1.34 msChecked 22 Nov 12:26:57 UTC
Family2a0d:2a00:2::IPV6
ICMPResponding1.36 msChecked 22 Nov 12:27:15 UTC

Snapshot retrieved 22 Nov 2026 12:27:17 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 .