Method v1.0

VPN protocol

What we will measure when a VPN product test is run: leaks, setup, and behavior on the networks people actually use.

Published 2026-11-17 · All protocols

Steps

  1. Record the date, software version, device, operating system, network type (home fiber, hotel Wi-Fi, Starlink, phone hotspot, Fire TV, or travel router) and method version in a test log.
  2. Before connecting: note the public IP, DNS resolvers, and WebRTC candidates using our leak-test tool.
  3. Connect to a named server or city, then repeat the leak-test tool. A leak is any candidate IP or DNS resolver that still belongs to the local network or ISP rather than the VPN.
  4. Check IPv6 and DNS separately. A product can hide IPv4 and still leak IPv6 or DNS.
  5. For kill-switch behavior: drop the VPN process or unplug the WAN for a short, documented interval and see whether traffic continues outside the tunnel. Log what we did, not a slogan.
  6. For router and Fire TV setups: log the exact app or firmware version and whether the tunnel comes up with WireGuard, OpenVPN, or another documented protocol.
  7. Publish the raw log under /data/ and link it from the page. No ranking claim that depends on a measurement ships without that file.

Limits

  • We will not invent throughput numbers, “unblocking” success rates, or server counts. Vendor-stated figures stay labeled as vendor-stated.
  • A leak-test tool used by a reader is not the same thing as a Privacy Proven product log.

When a log exists for this protocol, it will be listed on raw data and linked from the relevant guide.