VPN guides, checked against our own server
Every guide here answers one question people ask about VPNs. Where a claim can be tested, we tested it on our own server and give the date. Where it cannot, we say so. Each guide is numbered, and each cover is drawn for that guide alone.
- Guides
- 5
- Built from
- Published standards, makers' help pages, our own tests
- Written for
- Anyone, no background needed
- Last checked
- 15 November 2026
What is a VPN?
The plain meaning of the word, the three kinds of VPN people mean by it, what one changes for you and the four things it never touches.
Read the guide How it works 002What does a VPN do, and how does it work?
One page load followed through our New York server: a 148 byte hello, a 92 byte answer and 30 sealed packets. Each step, in the order it happens.
Read the guide Tested on our server 003What does a VPN hide?
We loaded one page through our New York server and recorded both sides of the tunnel. What each party could read, and what no VPN can cover.
Read the guide Tracking and the law 004Can a VPN be tracked?
Four parties, four different views. What each one can see, what a US subpoena can demand from a provider, and what a VPN can hand over if it kept nothing.
Read the guide Setup 005How to get a VPN and use it
Choose, install, connect, check. The exact menus on Windows and Android, how iPhone handles a VPN app, and the settings worth turning on first.
Read the guideTested first, written second.
A guide starts with the question and the first hand sources that answer it: the published standard, the law's own text, the maker's own help page. Where our own server can show the answer, we run the test and write down the date, the method and the numbers.
We sell a VPN, and that is a reason to be careful. So the guides say what a VPN cannot do as plainly as what it can, and none of them ends by telling you to buy anything.
The full method is on how we check. If you find a mistake, write to info@vetovpn.com and we correct it and change the date.