Browser leak tests can't see your torrent client. Add the magnet or tracker link below to your BitTorrent app; when it announces, we'll show the IP it exposed so you can confirm your VPN covers P2P.
Add it to your BitTorrent client (qBittorrent, Transmission, etc.).
Wait a few seconds for it to announce, then watch for the IP your client exposed.
Compare it to your VPN exit IP — if it's your real address, your torrent traffic is leaking.
How this works
The magnet above points at a one-time tracker on vpn.golf. When your BitTorrent client adds it, the client announces to that tracker — and the tracker sees the IP address your client is connecting from, exactly as any real peer or tracker in a swarm would. That's the address that matters for privacy: your browser and your torrent client can use different network paths, so a VPN that covers your browser may still leak your real IP for P2P (split tunneling, an interface binding, or a fallback when the tunnel drops). If the IP shown is your real one, fix the routing — bind your client to the VPN interface — before downloading anything. We record only the announcing IP for this test, briefly; there's no download, no content, and nothing tied to you.
Frequently asked questions
We give you a magnet link or tracker URL pointing at vpn.golf's measurement tracker. When your torrent client announces to it, we capture the source IP it connects from, then show it here so you can compare it to your VPN exit.
Your torrent client and browser can take different network paths. Split tunneling, an interface binding, or an app-specific route can send P2P traffic outside the VPN even when your browser is tunneled — so they reveal different addresses.
Browser-based leak tests only measure what your browser exposes. Your BitTorrent client is a separate application with its own networking, so the only reliable way to know what peers see is to make the client itself announce and capture that IP.
Your torrent traffic is bypassing the VPN. Peers and trackers — and anyone monitoring a swarm — can see your real address. Fix the routing before downloading anything you don't want tied to your connection.
Most clients (qBittorrent, Transmission, Deluge) have a setting to bind to a specific network interface or IP. Set it to your VPN's adapter so the client refuses to send traffic if the tunnel drops, then re-run this test to confirm.
P2P opens many connections and listens for incoming ones, and clients sometimes bind to the default interface or fall back to it when the tunnel hiccups. That fallback is exactly what exposes your real IP to a swarm.
Yes. BitTorrent is peer-to-peer, so every peer you connect to sees the IP you announce. That's why a leaking torrent client is more exposing than a leaking browser — strangers and monitors collect it directly.
It helps. A kill switch blocks all traffic if the tunnel fails, so your client can't fall back to your real connection mid-download. Binding the client to the VPN interface achieves the same for that one app.
No. We capture only the source IP your client announces with, briefly, so we can show it to you. There's no content, no torrent contents, and no download history — consistent with vpn.golf's no-logs posture.
It may not have announced yet, the tracker may be blocked by a firewall, or your client filters non-standard trackers. Give the announce a moment, make sure the magnet/tracker is added, and check your client allows it.
Some overhead is normal, but a well-provisioned exit usually keeps speeds high. The privacy trade-off is worth it for P2P, where your real IP would otherwise be public to every peer in the swarm.
When your device routes fully through a hole, your torrent client announces with the exit IP, not yours, and the in-tunnel resolver keeps lookups private. We keep no logs of your activity — only the announcing IP for this test, briefly.