VPN DNS Leak Basic Checklist
By Omellody Editorial Team · Updated 2026-05-29
Plan a local VPN DNS leak check for public Wi-Fi or travel: IP visibility, DNS resolver, WebRTC, kill switch and repeat-test checklist. Inputs stay in your browser. Use this as a cautious checklist, then verify current official terms before changing accounts, moving money, or relying on a security setting.
Tool
Direct answer: what counts as a DNS leak?
A likely DNS leak exists when the VPN is connected but DNS queries still resolve through your ISP, workplace, school or another network resolver instead of the VPN provider or your intended private resolver. This checklist helps you plan the test sequence; it does not run a live network scan.
| Check | Expected VPN state | If it fails |
|---|---|---|
| Public IP | Shows VPN location, not local ISP location. | Reconnect, change protocol or contact provider support. |
| DNS resolver | Resolver aligns with VPN/private DNS choice. | Disable ISP DNS override and retest. |
| WebRTC | No local/private IP exposed to websites. | Change browser settings or use hardened profile. |
| Kill switch | Traffic stops when VPN drops. | Enable kill switch before using risky networks. |
Source snapshot: the tool uses local checklist state only. For actual results, compare a reputable IP/DNS leak test before connecting, while connected and after changing VPN servers.
Three-step repeatable test flow
- Record baseline IP and DNS resolver on your normal network.
- Connect the VPN, refresh tests in a private window and compare location/resolver changes.
- Disconnect or force a network switch to confirm the kill switch behavior before browsing sensitive accounts.
Official verification checklist
- Open the official issuer, bank, VPN or password-manager support page in a new tab.
- Save the exact fee, deadline, recovery or safety language that applies to your account.
- Do not rely on screenshots, social posts or old summaries when official terms differ.
- Keep a reversible rollback path before changing security or financial settings.
Repeat the same checks on each device and browser you use while traveling, because DNS, WebRTC and kill-switch behavior can differ between desktop, mobile and browser profiles.
Related Omellody tool
Continue with this related planning tool for a second check before taking action.
Important disclaimer
This page is general education only and is not financial, tax, legal, credit, cybersecurity, identity-theft recovery or travel advice. Provider terms and official support instructions control.
FAQ
Does this page use live third-party metrics?
No. It is a local planning tool and does not claim live rankings, scores, search volume, APY, KD, PSI or provider test results.
What should I verify officially?
Verify current fees, terms, account settings, eligibility rules and support instructions on the official provider, issuer or bank site before acting.
Is this advice?
No. It is general educational organization, not financial, legal, tax, credit, security or travel advice.