DNS leak test
See which DNS servers handle your browser’s requests. Free, with no account needed.
Your public IP address
216.73.216.174
DNS check
If you are checking a VPN, connect before starting. Your result will appear here.
Take control of your connection with Kryon VPN
Connect through a VPN server, then check your public IP and DNS settings in this browser.
What is a DNS leak?
A DNS leak can happen when requests to look up website names go outside the DNS path you intended to use with your VPN. Your public IP can change while your original DNS provider still handles these requests.
The test sends new DNS requests and shows which servers handled them. Their addresses may differ from the ones in your settings, such as 1.1.1.1 or 8.8.8.8. The result applies to this browser.
An expected DNS route through a VPN
Your browser
VPN tunnel
DNS resolver
Website address
How to check for DNS leaks
For a useful comparison, test in the same browser before and after connecting. Only disconnect your VPN for a baseline if doing so is safe for you.
Run a baseline test
With the VPN off, run the test and choose “Compare before and after VPN”. This keeps the first result in the current tab.
Connect to your VPN
Wait for the app to confirm the connection. Keep the same browser, network and DNS settings so the comparison is meaningful.
Check and compare
Run the comparison. Check whether the IP changed and whether DNS from the original network is still listed. Compare the provider with your VPN’s documented DNS setup.
How to read your DNS result
The provider and intended settings matter more than the number of addresses or the country shown.
Expected DNS network
If the detected DNS belongs to your VPN’s documented configuration, the result is consistent with that setup. A VPN can use partner infrastructure, so the company name may differ from the VPN brand.
Original ISP DNS remains
If the public IP changes but DNS from your original connection remains, investigate a possible leak. Review the VPN’s DNS settings and check whether this browser is excluded from the tunnel.
Cloudflare, Google or several addresses
Public DNS can be selected in your browser, device or VPN. Providers also use pools and anycast routing. These results alone do not show that requests escaped a VPN tunnel.
Check your connection with Kryon VPN
Choose a plan, connect in the app and run the test again to compare your results.
Common causes and how to fix them
Start with the VPN’s recommended settings. Change one setting at a time and test again, so you can see what made the difference.
VPN or manual DNS settings
Use the VPN app’s recommended DNS configuration. Check manual DNS entries on your device or router against your VPN provider’s instructions. Avoid combining conflicting DNS tools.
Secure DNS in the browser
The browser’s DNS over HTTPS (DoH) can use its own DNS provider instead of the system resolver. These requests can still travel through the VPN; a different provider alone does not mean a leak. Check that the selected DNS matches the configuration you want.
IPv6 and split tunneling
Check that the VPN supports or handles IPv6 safely and includes this browser in the tunnel. An IPv6 resolver address itself does not establish an IPv6 leak.
Reconnects and network changes
Repeat the check after switching Wi-Fi, mobile networks or VPN servers. Use a kill switch if your VPN supports it, and keep the app and router software updated.
What a DNS test cannot confirm
The result shows the DNS servers detected in this browser. The test does not check other apps, the full path of requests or DNS encryption.
DNS leak test: common questions
Practical answers about VPNs, DNS providers and unexpected results.
No. A VPN exit and a DNS resolver can use different addresses, hosting providers and countries. Geolocation is approximate, especially for anycast. Compare the DNS network with your intended settings and your VPN provider’s guidance.