Verify your encrypted DNS configuration (DoH/DoT/DoQ) is working correctly. See which DNS resolvers are handling your requests.
✓ Expected: DNS queries are encrypted via DoH, DoT, or DoQ. Your ISP only sees encrypted traffic and cannot log which sites you visit.
✗ Problem: DNS queries are sent unencrypted to your ISP's resolver. They can log every website you visit and potentially inject ads or block content.
DNS client not set as system resolver.
IPv4 DNS encrypted but IPv6 bypasses it.
ISP intercepts DNS at network level.
Browser's DoH using different resolver.
Compare this with your DNS results below.
Sends 6 unique DNS queries to detect all resolvers.
Click "Run Extended Test" to discover which DNS servers are handling your requests.
Initializing...
An error occurred. Please try again.
Many privacy DNS providers use cloud hosting infrastructure to run their servers globally. This means the organization name shown may be a hosting company, not your DNS service. This is completely normal and doesn't indicate a leak. The key is that the resolver is not your ISP.
Configure encrypted DNS (DoH/DoT/DoQ) at the system level using tools like dnscrypt-proxy, stubby, or your OS's native settings.
systemctl status dnscrypt-proxy
127.0.0.1 where your client listens.
/etc/resolv.conf isn't overwritten by NetworkManager.
dnsdoh.art
abc123.leak.dnsdoh.art) that have never been queried before. Your browser must perform a fresh DNS lookup, which our authoritative nameserver logs. We then show you which DNS resolvers made the query on your behalf.