Short answer: An IPv6 leak means IPv6 traffic or browser-visible IPv6 signals remain reachable outside the route you expected. This often matters on dual-stack home networks, mobile networks, iPhones, routers, or VPNs that tunnel IPv4 but block or mishandle IPv6.
Use this hub when a VPN looks fine on IPv4, but IPv6, AAAA DNS routes, mobile data, router settings, or device network behavior still need a focused check.
Quick answer
- Start with IPv6 Leak Test because it is the main tool for this topic.
- Compare the result with adjacent signals instead of treating one test as a full privacy guarantee.
- Use the guide list below to move from diagnosis to the next practical fix.
- Use Safe Copy after testing so you can compare before and after without sharing sensitive raw details.
IPv6 Leak at a glance
| Signal | What it means | Best next step |
|---|---|---|
| Visible IPv6 | The browser can reach an IPv6 path from the current network. | Run IPv6 Leak Test and compare with VPN state. |
| Dual-stack | IPv4 and IPv6 may work side by side. | Check both What Is My IP and IPv6 Leak Test. |
| VPN IPv6 handling | Some VPNs tunnel IPv6, some block it, and some support IPv4 only. | Use the provider's documented IPv6 behavior as the baseline. |
| Mobile/iPhone | Mobile networks often handle IPv6 differently from Wi-Fi. | Run the iPhone IPv6 leak test on Wi-Fi and mobile data. |
| DNS AAAA | Sites can load through IPv6 when AAAA records are reachable. | Pair IPv6 checks with DNS Leak Test. |
| Receipt | A receipt captures the current browser/session state for comparison. | Use Safe Copy after retesting. |
Limits and methodology
MyIPScan topic hubs organize practical checks around observable browser and network signals. Results are snapshots for this browser, device, network, and time. They do not prove full anonymity, do not replace provider documentation, and do not test every app on the device.
For transparent limits, see the MyIPScan methodology, editorial policy, and author profile.