Where facts come from
We use only first hand sources: the people or the machine that the fact is about. Never a review site, a summary written by someone else, or an AI answer.
| Kind of fact | Source we use | Example on this site |
|---|---|---|
| How the New York server behaves | Tests we run on the server, with the date and the method | The ten checks on the home page |
| How fast a Pro city is | Our own download test, with the date and the method | The eight cities on the servers page |
| What a protocol or standard says | The standard's own published text | WireGuard's protocol page, RFC 1035, RFC 6066 |
| What a law says | The law's own published text | 18 U.S.C. 2703, from the US Government Publishing Office |
| What another VPN offers | That provider's own page, read on a stated date | The table on Best free VPN |
| How a device's settings work | The maker's own help page | Microsoft's and Google's VPN help pages |
| Veto's own plans and prices | The decisions of the company that runs Veto | The pricing page |
Each page has a source file kept with the site's code. It holds the address of each source, the date it was read and the exact words, and a dated copy of every page we relied on. The source files are not published, because they hold copies of other people's pages.
The tests we run ourselves
Three scripts run on the New York server. All three are part of the site's code, and all three were last run on 15 November 2026.
The behaviour check
A test device connects from a separate network space on the server itself, with its own key and its own tunnel. From inside the tunnel it tries each rule the site describes.
| What is tried | What must happen |
|---|---|
| Ask a public service which IPv4 address it sees | The exit address, never the entry address |
| The same over IPv6 | The exit address |
| Look up a site name | Answered by our resolver inside the tunnel |
| Look up a name known for malware | Refused |
| Open a web connection on port 443 | Goes through |
| Open a mail connection on port 25 | Blocked |
| Open Windows file sharing on port 445 | Blocked |
| Reach the server itself from inside the tunnel | Blocked |
| Reach a private address | Blocked |
| Read the server's handshake record | The test device completed a handshake |
The two view capture
The same test device loads one page while the server records two views: between the device and the server, where an internet provider sits, and between the server and the site. A short program then counts packets, sizes and addresses, and searches every packet for the site's name. The results are in our guide What does a VPN hide?. Both recordings are deleted at the end of the run.
The configuration reads
For the no logs claims, we read the server's settings directly: the full firewall rule set, the resolver's logging settings, and what the tunnel software holds about each device. The no logs page gives what we found.
The Pro city test
From the New York server, a test connects to one Pro city at a time in a separate network space. It asks our own site where the connection appears to be, looks up a name, and downloads a 40 MB test file to measure speed. Eight cities were tested on 15 November 2026. The results are on the servers page.
The checks every page passes before it goes live
Before a change to this site goes live, it is built on the server and checked by a script. A page that fails is not published.
- The title and the description are counted by code, within fixed lengths.
- Every page has exactly one main heading, and every image has a text description.
- Every link inside the site leads to a page that exists.
- Every question and answer in the page's structured data matches the visible text word for word.
- No page loads a script, style, font or image from another host.
- No banned phrase and no dash appears in the text a visitor reads.
What checked means, and what it does not
Checked means we read the fact against its source, or ran the test again, on the date shown. It does not mean the fact cannot change the next day. Free plans change, laws change and servers change.
Tested by us means the test was run by Veto, with the method written on the page. It does not mean anyone outside has repeated it.
What we do not check
- Speed on your line. Our speed figures come from one run per city from New York. They show what we measured that day, not what your connection will get.
- Other services' claims. When a provider says it keeps no logs, we can report that it says so. We cannot test it.
- Every country's law. Where a guide touches the law, it names the law it read and says that it is not legal advice.
How mistakes are fixed
- Write to info@vetovpn.com with the page and the line.
- We read the source again, or run the test again.
- If the line is wrong, we correct it and change the page's date. If it turns out to be false, we remove it.
- Changes to the privacy policy and the terms are listed on those pages with their dates.
Questions about our checks
What does Last checked mean on a page?
The UTC date on which the facts on that page were last read against their sources or tested again. It is set by hand. It is never the date the site was built.
Do you test other VPNs?
No. Facts about other providers come only from their own pages, with the date we read them. Where a page does not state something, we say so rather than guess.
Has anyone outside checked Veto?
No. No outside audit has been done. Every check on this page is ours, and we say so wherever it matters.
How do I report a mistake?
Write to info@vetovpn.com with the page and the line. If it is wrong, we correct it and change the date. If a line turns out to be false, we remove it.