IPv6 leak test — dual-stack exposure
On dual-stack networks your browser may reach sites over IPv6 while the proxy exits via IPv4 — or WebRTC may reveal an IPv6 path. Compare IPv4 vs IPv6 visibility for your current session.
Uses browser-side IP discovery plus CheckProxy.org geo lookup. Pair with WebRTC leak test and antidetect health check.
IPv6 leak status
—
| Connection IPv4 (site sees) | — |
|---|---|
| Connection IPv6 (site sees) | — |
| Browser IPv4 (direct fetch) | — |
| Browser IPv6 (direct fetch) | — |
FAQ — IPv6 leak test
Why IPv6 matters when you use proxies or antidetect browsers.
An IPv6 leak is when IPv6 traffic or addresses are visible while you expect only IPv4 through a proxy or VPN profile.
Dual-stack OS and browsers can use different paths per protocol. Your proxy checker may show IPv4 while WebRTC or direct fetches expose IPv6.
Disabling IPv6 at OS level can help, but antidetect profiles, extensions, and WebRTC settings also matter. Test after each profile change.
WebRTC focuses on ICE candidates. This page compares protocol-level IPv4/IPv6 visibility for the same browser session.
Results depend on network, browser, and proxy type. Use as a quick health signal alongside the antidetect dashboard.