Core principles
| Principle | What it means in practice |
|---|
| Reference first | We compare normal network state with VPN-on state instead of treating one isolated number as truth. |
| Layer separation | We separate IP route, DNS resolver, IPv6, WebRTC, latency, jitter, device and account context. |
| Repeatability | Readers should be able to repeat the same check from the same browser and see whether the result is stable. |
| Legal caution | We explain diagnostics, not evasion. Platforms, employers and schools may set their own permitted-use rules. |
Leak testing
The leak test checks public IP, DNS resolver exposure and browser WebRTC candidates where available. A likely leak means the VPN-on state still exposes part of the normal network route or that the apparent public route did not change as expected.
Interpretation: a clean result is a useful signal, not a legal or security guarantee.
Speed testing
Speed checks focus on practical connection quality: ping, jitter, download, upload and consistency. A high headline download number is less useful if jitter is unstable or upload collapses during video calls, gaming or live streams.
Streaming diagnostics
Streaming failures are evaluated through platform, device, route and account context. We do not claim guaranteed access. We help identify whether a problem looks like DNS inconsistency, app cache, endpoint reputation, live-event load, local Wi-Fi or account/device mismatch.
Limitations
Browser tests cannot see every router, ISP or app-layer decision. Smart TV apps, mobile apps and streaming platforms can use signals unavailable to a normal web page. That is why each guide combines lab signals with practical step-by-step checks.
Editorial process
Guides are updated in batches when pages move from draft to production. We sync UK and Spanish publication dates where they represent the same release wave, but each local article is adapted for its market, operators, legal wording and reader intent.