DNS leak test for VPN users

Quick browser checks

DNS leak checklist

• Connect to the VPN, then verify that your visible IP changed.
• Check your operating system DNS servers. They should be VPN DNS or a resolver you trust.
• Disable browser WebRTC if your browser exposes local network addresses.
• Avoid public VPNs for sensitive accounts unless you trust the operator.

What a DNS leak means for VPN users

DNS is the system that turns domain names into IP addresses. If your VPN changes the visible IP but DNS requests still go to your internet provider, office network or another resolver outside the tunnel, those lookups can reveal which domains you are opening even when the page content is encrypted with HTTPS.

OpenVPN profiles can handle DNS in different ways. Some servers push DNS settings, some rely on your operating system, and some configs only route traffic without changing name resolution. That is why DNS behavior should be checked separately from the public IP address.

How to reduce leak risk

• Prefer recently checked VPN profiles with a clear remote host, protocol and port.
• Review the config for DNS-related directives before connecting.
• After connecting, confirm that your public IP changed and that DNS uses a resolver you expect.
• Disable browser features or extensions that bypass proxy and VPN settings if your threat model requires it.
• Use public VPN servers for testing and low-risk browsing, not for sensitive accounts or private work.