DNS Leak Test, Which DNS Am I Using & Public DNS Benchmark | MyIPDNS

Test for DNS leaks, discover which DNS resolvers and egresses you are using, and benchmark public DNS speed and DNSSEC validation.

DNS Health & Leak Check

Live inspection of your DNS egresses, provider inference, and query characteristics
Testando...
Escaneando...

Public DNS Recommendations

Unbiased recommendations filtered by technical metrics and benchmarks from your vantage

Unfiltered resolvers with sample size >= 6 and 7-day availability >= 95%, sorted by latency.

Provider Variant Endpoints Latency Availability
114 DNS Standard UDP53: 114.114.114.114 UDP53: 114.114.115.115 - >=95%
AdGuard DNS Unfiltered UDP53: 94.140.14.140 UDP53: 94.140.14.141 UDP53: 2a10:50c0::1:ff UDP53: 2a10:50c0::2:ff DOT: unfiltered.adguard-dns.com DOH: unfiltered.adguard-dns.com - >=95%
AliDNS Standard UDP53: 223.5.5.5 UDP53: 223.6.6.6 UDP53: 2400:3200::1 UDP53: 2400:3200:baba::1 DOT: dns.alidns.com - >=95%
Applied Privacy DNS Standard DOT: dot1.applied-privacy.net DOH: doh.applied-privacy.net - >=95%
Baidu DNS Standard UDP53: 180.76.76.76 - >=95%
Cisco OpenDNS Standard UDP53: 208.67.222.222 UDP53: 208.67.220.220 - >=95%
Cloudflare Standard UDP53: 1.1.1.1 UDP53: 1.0.0.1 UDP53: 2606:4700:4700::1111 UDP53: 2606:4700:4700::1001 DOT: one.one.one.one DOH: cloudflare-dns.com - >=95%
Digitale Gesellschaft Standard DOT: dns.digitale-gesellschaft.ch DOH: dns.digitale-gesellschaft.ch - >=95%
dnsforge.de Standard UDP53: 176.9.93.198 UDP53: 176.9.1.117 UDP53: 2a01:4f8:151:34aa::198 UDP53: 2a01:4f8:141:316d::117 DOT: dnsforge.de DOH: dnsforge.de - >=95%
DNS.SB Standard UDP53: 185.222.222.222 UDP53: 45.11.45.11 UDP53: 2a09:: UDP53: 2a11:: DOT: dot.sb DOH: doh.sb - >=95%
Google Public DNS Standard UDP53: 8.8.8.8 UDP53: 8.8.4.4 UDP53: 2001:4860:4860::8888 UDP53: 2001:4860:4860::8844 DOT: dns.google DOH: dns.google - >=95%
IIJ.JP DNS Standard DOT: public.dns.iij.jp DOH: public.dns.iij.jp - >=95%
LibreDNS Standard DOT: dot.libredns.gr DOH: doh.libredns.gr - >=95%
Mullvad Standard DOT: dns.mullvad.net DOH: dns.mullvad.net - >=95%
Quad 101 Standard UDP53: 101.101.101.101 UDP53: 101.102.103.104 - >=95%
Quad9 Unsecured UDP53: 9.9.9.10 UDP53: 149.112.112.10 UDP53: 2620:fe::10 UDP53: 2620:fe::fe:10 DOT: dns10.quad9.net DOH: dns10.quad9.net - >=95%
UncensoredDNS Standard DOT: anycast.censurfridns.dk DOH: anycast.censurfridns.dk - >=95%
Yandex DNS Standard UDP53: 77.88.8.8 UDP53: 77.88.8.1 UDP53: 2a02:6b8::feed:ff UDP53: 2a02:6b8:0:1::feed:ff DOT: common.dot.dns.yandex.net - >=95%

Resolvers with Client Subnet (ECS) disabled and encrypted DoH/DoT endpoints, prioritized by official no-log claims.

Loading privacy resolvers...

Trusted resolvers verified by real-world DNSSEC validation tests, sorted by 7-day minimum availability.

Loading authority resolvers...

Select specific features to filter matching resolvers (multiple selections form an intersection).

Select features to filter recommendations.

DNS Setup Tutorials & One-Click Copy

Windows 11 (DoH)

  1. Open Settings → Network & internet.
  2. Click Wi-Fi or Ethernet → Hardware properties.
  3. Under DNS server assignment, click Edit.
  4. Switch from Automatic (DHCP) to Manual and turn on IPv4.
  5. Enter Preferred DNS (e.g. 1.1.1.1) and select Encrypted only (DNS over HTTPS).

macOS

  1. Open System Settings → Network.
  2. Select your active network connection → Details...
  3. Navigate to the DNS tab.
  4. Click + and add your preferred DNS address (e.g. 1.1.1.1).
  5. Click OK and Apply.

Android (Private DNS / DoT)

  1. Open Settings → Network & internet.
  2. Tap Private DNS.
  3. Select Private DNS provider hostname.
  4. Enter the DoT hostname (e.g. one.one.one.one or dns.google).
  5. Tap Save.

iOS / iPadOS

  1. Open Settings → Wi-Fi.
  2. Tap the (i) icon next to your connected network.
  3. Scroll down to Configure DNS → choose Manual.
  4. Tap Add Server, enter the IP (e.g. 1.1.1.1), and tap Save.
  5. For encrypted DoH profiles, install the official signed mobileconfig profile.

Routers (Universal)

  1. Access your router admin console (e.g. 192.168.1.1).
  2. Locate WAN / Internet / DHCP settings.
  3. Replace Primary and Secondary DNS with your preferred resolver IPs.
  4. Save and reboot connected devices to flush DHCP leases.

Web Browsers (Chrome / Edge / Firefox)

  1. Open Browser Settings → Privacy and security.
  2. Select Security → scroll to Use secure DNS.
  3. Enable secure DNS and choose Custom provider.
  4. Paste the DoH URL (e.g. https://1.1.1.1/dns-query).

Public DNS Benchmark Observatory

Continuous real-world probe results from our global network nodes

Past 7 days, queried from Jena, targets cached domain (example.com)

Provider UDP 53 DoT (853) DoH (443) DNSSEC
114dns 8.6825 ms (100%) - - Insufficient data
360dns 247.922 ms (68%) - - No
adguard 8.6545 ms (100%) 8.4615 ms (100%) 8.578 ms (100%) Yes
ahadns - - - Insufficient data
alidns 26.812 ms (100%) 47.2525 ms (100%) - No
appliedprivacydns - 20.389 ms (100%) 23.943 ms (93%) Insufficient data
baidudns 260.948 ms (50%) - - No
bebasdnsbybebasid - 168.7285 ms (100%) 168.3 ms (93%) Insufficient data
cira 96.222 ms (100%) - 97.011 ms (96%) Yes
cisco_opendns 8.204 ms (100%) - - Yes
cleanbrowsing 254.133 ms (88%) 172.081 ms (93%) 165.308 ms (93%) Insufficient data
cloudflare 9.0295 ms (100%) 9.203 ms (100%) 10.905 ms (100%) Yes
cnnic 220.955 ms (96%) - - No
comodo 8.7445 ms (100%) - - Insufficient data
controld 9.8855 ms (100%) - - Yes
decloudusdns - 11.6115 ms (100%) 11.745 ms (100%) Insufficient data
digitale_gesellschaft - 14.2955 ms (100%) 14.635 ms (100%) Insufficient data
dnsforge 13.79 ms (100%) 13.804 ms (100%) 14.402 ms (100%) Yes
dnspod 157.944 ms (40%) - 158.273 ms (90%) Insufficient data
dnssb 8.63 ms (100%) 8.694 ms (100%) 8.966 ms (100%) Yes
dnswatch 8.5455 ms (71%) - - Yes
google 11.6505 ms (100%) 9.347 ms (100%) 10.7515 ms (100%) Yes
he 8.156 ms (89%) - 8.4475 ms (100%) Yes
iij.jpdns - 23.821 ms (100%) 24.2845 ms (100%) Insufficient data
level3 8.3225 ms (100%) - - No
libredns - 11.746 ms (100%) 12.2495 ms (100%) Insufficient data
mullvad - 25.592 ms (100%) 23.4545 ms (100%) Insufficient data
neustar 8.6285 ms (98%) - - Yes
nextdns 8.547 ms (95%) - 8.754 ms (100%) Yes
onedns 251.513 ms (63%) - - No
privacy-firstdns 184.282 ms (100%) 162.3915 ms (100%) - Yes
quad101 - - - Insufficient data
quad9 14.0655 ms (100%) 8.398 ms (100%) 8.752 ms (100%) Yes
restena - - 15.0425 ms (100%) Insufficient data
surfsharkdns 8.6035 ms (50%) - - No
switch - - 17.103 ms (50%) Insufficient data
uncensoreddns - 63.414 ms (100%) 63.653 ms (100%) Insufficient data
verisign 11.2065 ms (96%) - - Yes
yandex 61.1095 ms (96%) 58.1965 ms (100%) - No
Loading weekly benchmark dataset...

Provider Vantage Coverage Cold RTT (First Median)

Frequently Asked Questions

A DNS leak occurs when DNS requests travel outside your VPN or encrypted proxy tunnel directly to your ISP or unauthorized DNS servers, exposing every domain you visit.

ECS sends a truncated portion of your IP address (e.g. /24 prefix) to upstream authoritative nameservers to optimize CDN routing. While it may speed up local CDN resolution, it discloses your network location to the websites and nameservers you query.

DNSSEC protects against DNS spoofing and cache poisoning by cryptographically signing records. Our benchmark probes each provider with intentionally broken signatures (dnssec-failed.org with DO=1); resolvers that strictly validate return SERVFAIL, while resolvers that do not validate return NOERROR.

Standard UDP port 53 transmits queries in plaintext, vulnerable to eavesdropping and ISP tampering. DNS over HTTPS (DoH) encrypts queries over HTTPS (port 443), blending with regular web traffic. DNS over TLS (DoT) encrypts queries over dedicated TLS (port 853).

For raw speed, pick unfiltered providers with the lowest latency from your vantage. For maximum privacy, choose resolvers with ECS disabled and verified no-logging policies using DoH/DoT. For proxy users in mainland China, use split routing where mainland domains resolve via local fast DNS and overseas domains route via encrypted proxy DNS.