Private route diagnostic

Torrent IP Leak Test

Compare the route visible to this browser with the address your torrent client uses for a private HTTP tracker announce.

Torrent IP leak guide

How to compare your browser and torrent-client routes

Create one private session, open the magnet link or downloaded torrent in the exact client you want to test, and wait for its HTTP tracker announce. The session contains no downloadable content and returns no peers.

How to use the result

  1. Record the browser baseline shown when the private session is created.
  2. Open the generated test in the intended torrent client without adding unrelated torrents.
  3. Wait for a valid announce, then compare the observed address and address family with the browser baseline.

What it means

A different same-family address shows that this HTTP tracker announce used a different public route than the browser request. A matching address covers only this test and should not be generalized to DHT, UDP trackers, peers, DNS, or later connections.

Important limits

  • The test observes a private HTTP tracker announce only.
  • IPv4 and IPv6 must be compared as separate address families.
  • The capability-protected result expires automatically after 15 minutes.
Useful next checks Review the browser routeResearch VPN privacy

Common questions

Does the test join a torrent swarm?

No. The generated torrent has no downloadable content, the tracker returns no peers, and the session is private and short-lived.

Why might the torrent address differ from the browser?

The torrent client may bypass a browser-only proxy or VPN rule, use another address family, or follow different split-tunneling settings.