Test for DNS leaks that could expose your browsing activity when using a VPN or proxy service.
DNS Leak Tester reveals which recursive DNS resolvers are visible while your browser uses its current network path. Running the test causes lookups for test-specific hostnames, allowing the resolvers requesting those names to be identified. Compare the reported addresses and operators with the DNS service you expect your VPN, proxy, browser, or operating system to use. The common surprise is that several resolver addresses do not automatically mean a leak. A leak is a mismatch with the routing and resolver policy you intended.
Each test lookup uses a hostname controlled for the test, so the authoritative DNS side can observe which recursive resolver requests that hostname. The reported resolver IP address is the network-facing address seen for the query. It may be a shared address operated by a VPN, internet provider, enterprise, or public DNS service rather than an address assigned directly to your device.
Establish which resolver or provider your VPN or proxy is supposed to use, then run the test while that service is connected. Resolver addresses belonging to an unexpected ISP or local network can indicate DNS bypass. Repeat after disconnecting for comparison. The expected set depends on split tunneling, browser secure DNS settings, corporate policy, and whether the proxy is designed to carry DNS requests.
DNS services commonly use pools of recursive resolvers for capacity, reliability, and geographic distribution. A VPN may therefore produce several legitimate addresses during one test. Multiple rows are not themselves a failure. They matter when an address belongs to a network or operator that should not receive DNS requests under your chosen VPN or proxy configuration.
No. It can reveal which resolvers handled the test's DNS lookups and help identify unexpected DNS routing. It cannot verify all traffic encryption, detect every IP or WebRTC exposure, assess resolver logging, or describe the behavior of other applications. Test again after changing networks, VPN servers, browser DNS settings, or split-tunneling rules.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Generate strong, random passwords with customizable length, character sets, and complexity requirements.
Analyze password strength with entropy scoring, crack-time estimates, and improvement suggestions.
Create cryptographically random strings for API keys, tokens, salts, and unique identifiers.
Create QR codes for URLs, text, Wi-Fi credentials, vCards, and more with customizable size and colors.
Scan and decode QR codes from uploaded images or your device camera to extract embedded data.
Compute MD5, SHA-1, SHA-256, and SHA-512 checksums to verify file integrity and detect tampering.