Torrent leak test (browser IP + WebRTC check)
BitTorrent clients talk to many peers. If the VPN covers the torrent app but the browser or WebRTC still publishes your real IP, trackers and web UIs can see a different address than the swarm. This torrent leak test uses the same IP and WebRTC checks you would run before seeding.
Use it when you route torrents through a VPN and want to know whether this browser still exposes a public IP or WebRTC candidate outside that tunnel. It does not connect to a BitTorrent swarm, and it cannot see the IP your torrent client announces to trackers or peers.
How do I check for a torrent IP leak?
With your VPN on, run this browser test: your public IP and any WebRTC public candidate should both belong to the VPN. Then run the DNS leak test. This checks the browser only; it doesn't see the IP your torrent client announces, so also bind the client to the VPN interface.
No torrent traffic is started. The page only runs the on-site IP lookup and WebRTC candidate collection in your browser.
How to use this tool
- Turn on the VPN that the torrent client is supposed to use.
- Check the public IPv4 and IPv6 on this site and confirm both match the VPN. If the VPN only tunnels IPv4, your IPv6 address may still be your ISP’s.
- Run the WebRTC test. An extra public candidate is the leak to fix before you open a torrent client in the same session.
- Optionally continue with the DNS leak test, then bind the torrent client itself to the VPN interface (see the qBittorrent guide).
Run the WebRTC leak check
What this test can and can't see
This page is honest about scope: it is a browser check, not a BitTorrent swarm probe.
Can see
- The browser’s current public IPv4 and IPv6 from the on-site IP lookup.
- Public WebRTC ICE candidates this browser gathers over STUN.
- With the linked DNS leak test, which resolvers answer name lookups for this browser.
Can't see
- The IP a torrent client (qBittorrent and others) announces to trackers, DHT, or peers.
- How the client behaves when the VPN drops, unless you test that inside the client.
- Proxy or split-tunnel rules that apply only inside the torrent app.
To confirm the torrent client itself stays on the VPN, bind it to the VPN network interface (see the qBittorrent IP leak check guide) or use a third-party magnet-based IP check that makes the client contact a test tracker. ipdet does not run that magnet step.
Frequently asked questions
Does this send data to a torrent tracker?
No. It is a browser IP and WebRTC leak test aimed at the same failure mode people mean by “torrent leak test”.
Should DNS match the VPN too?
Yes. After the IP and WebRTC checks, run the DNS leak test so name lookups are not still going to the ISP.
Can a browser test see my torrent client's IP?
No. It sees the browser's public IP and WebRTC candidates. Your client's announced IP can only be seen by a tracker or peer, e.g. via a magnet-based check.
What counts as a leak?
Any public IPv4/IPv6 address or WebRTC candidate that belongs to your ISP instead of the VPN.
Do I need to test IPv6?
Yes. If the VPN only tunnels IPv4, your IPv6 address may still be your ISP's.
How do I stop qBittorrent leaking when the VPN drops?
Bind it to the VPN network interface and enable the VPN kill switch. See the qBittorrent guide.
Related tools
