DNS leak test and resolver check
See which DNS resolver networks MyLeaks observes
See which resolver networks handle DNS requests during this visit and compare them with the current public network.
Live result
Current authoritative DNS observation
JavaScript is required to trigger one-use DNS names and poll the live result.
No observation is reported as unavailable, not as “no leak.”
- Resolver-egress addresses
- JavaScript required
- Resolver networks
- JavaScript required
- Observed probes
- JavaScript required
- DNS fallback
- JavaScript required
JavaScript is required to observe resolver infrastructure.
What this test measures
MyLeaks observes the resolver-egress IPs that query its test names. The observed address normally represents a recursive resolver or egress node and may differ from both the configured DNS address and the visitor’s public IP.
How it works
MyLeaks asks the browser to resolve several unique test names, records which resolver networks reach them, and displays the result after a short wait.
What the result means
An observed IP, ASN, organization, or country describes a recursive resolver or resolver-egress network visible to MyLeaks. Multiple addresses or networks can be normal. Unavailable means the test produced no usable observation.
Why DNS may differ from your public IP
Public and anycast resolvers, browser or operating-system DNS selection, VPN-provided DNS, enterprise gateways, and other intermediaries can resolve names from a network different from the HTTPS connection.
Limitations
- Browser and network settings can suppress some test requests.
- Shared and intermediary resolvers can affect which addresses are observed.
- The result may not be the exact resolver configured on the device.
- This test does not identify DoH or DoT settings and is not a dedicated IPv6 DNS test.