DNS Leak Test (Lite)

Does this DNS Leak Test upload my IP or data to any server?

No. The tool performs all tests directly in your browser. It fetches your public IP from ipify and geolocation details from ipapi, but no logs, history, or identifiers are stored. None of your DNS results or WebRTC IPs are uploaded or saved anywhere.

How does this test detect DNS leaks?

This tool runs three independent checks: (1) your public IP via ipify, (2) your DNS resolver using a Cloudflare DNS-over-HTTPS query, and (3) WebRTC local IP detection with a STUNless peer connection. If DNS queries or local IPs do not match your VPN expectations, it may indicate a leak.

What does it mean if I see local IPs under WebRTC?

WebRTC may expose your LAN or internal network IPs unless your browser blocks it. Seeing private IPs like 192.168.x.x is normal. However, if a public IP appears here that does not match your VPN, this may indicate a WebRTC leak.

Why does the DNS resolver show 'Cloudflare/DoH'?

This lite test queries Cloudflare's DNS-over-HTTPS endpoint (cloudflare-dns.com). The resolver field indicates the DNS server responding to the query. If it shows Cloudflare or your VPN’s DNS, you're safe. If it shows your ISP or another unexpected resolver, you may have a DNS leak.

Is this test accurate if I am using a VPN?

Yes, for most cases. Your VPN should mask your public IP and route DNS through its own secure resolvers. If the test shows your ISP’s DNS or your real IP, that indicates a leak. However, some VPNs use split-tunneling or custom DNS rules that can affect results.

Why does the test say 'Suspicious' under DNS status?

The DNS Status field is based on the response code from the DNS-over-HTTPS query. Anything other than Status=0 may indicate unexpected resolver behavior or DNS interception. This does not guarantee a leak, but it suggests checking your VPN configuration.

What does it mean if DNS or WebRTC test shows 'failed'?

Failure usually means your browser blocked the request, your network restricted DoH queries, or you are on a restrictive connection such as corporate WiFi. The tool cannot complete the leak test without DNS and WebRTC support.

Is this test enough for a full DNS leak analysis?

This Lite version provides a quick check but is not a full multi-server test. It is ideal for fast verification. For deep scans across multiple DNS endpoints, you would need a full version that queries additional hostnames and resolvers.