This test forces your browser to resolve several unique subdomains, revealing
the DNS resolvers your system actually uses. Use it to identify unexpected
resolver operators while a VPN or Tor is active. Resolver identity alone does
not prove whether the upstream transport used DNSCrypt or another encryption method.
Resolver locations
Your connection IP and each DNS resolver that answered your queries, placed by
country. Hover a marker to see the IPs, hostnames and country.
Your connection IP DNS resolver
IP Address
Hostname/Type
Precise Hostname
Note: The first row tagged YOUR CONNECTION IP is your public IP
address (your ISP when no VPN/Tor is active), shown for reference; it is
not a DNS resolver or a leak. The rows under
"DNS resolvers your system actually used" are the resolvers that answered
your queries. Multiple entries are normal. A likely leak is present when a resolver
belongs to your real ISP while a VPN or Tor is active. This browser test identifies
resolver endpoints; it cannot verify the encryption protocol used upstream.
No reverse DNS (PTR) in the Precise Hostname column means that IP
publishes no reverse DNS name, or its owner's reverse zone does not answer. That is
normal for many resolvers (Cloudflare's anycast resolvers have none); the
Hostname/Type column and the country under each IP still identify it.
Lookup failed means our own lookup did not complete; run the test again.
Kodachi's own leak test
Looks up six random names under leak.kodachi.cloud and asks this site's own nameserver which resolvers asked for them. Your browser sends the test names only to the resolvers it already uses; on their way here a resolver may also ask Porkbun's nameservers, which hold kodachi.cloud. This site names each resolver's network through RIPE NCC.