How to report a flaw
Write to security@vetovpn.com. Tell us what you found, how to see it again and what it could allow. Please give us a chance to fix it before you tell anyone else.
- Test only against what you own or against the parts listed in scope below.
- Do not read, change or delete data that is not yours, such as another person's account.
- Do not degrade the service for others: no floods, no load tests.
- Do not use social tricks on anyone working on Veto.
We answer every report, say what we did about it, and credit you on this page if you want to be named. There is no paid reward today.
What is in scope
| Part | In scope | Status |
|---|---|---|
| vetovpn.com | Yes | Live |
| The account panel and the account system | Yes | Live |
| The VPN servers | Yes, the behaviour of the service | Live |
| The Veto app for Windows | Yes | Version 1.0.1 |
| Services we use, such as the delivery network and mail provider | No. Report to them | Run by those companies |
How the website is protected
Each of these was read from the live site's own answers on 15 November 2026.
| Protection | What it does |
|---|---|
| HTTPS only, with a long HSTS period | Browsers refuse to load the site without encryption |
| A content policy | Browsers refuse scripts, styles, fonts and images from any other host |
| No framing | The site cannot be placed inside another site's page |
| No content type guessing | Browsers treat each file only as what the server says it is |
| A strict referrer policy | Other sites learn at most the domain a visitor came from |
| Camera, microphone, location and payment features turned off | No page can ask for them |
| No cookies and no third party scripts | Nothing to steal from a session, and nothing loaded from elsewhere |
| A guessing limit on the account panel | 10 tries in 10 minutes from one address |
| Limits on every account action | New numbers, devices, payment pages, renewals and deletions, each limited per address |
How the New York server is protected
- Login by key only. Password logins to the server are switched off.
- Separate entry and exit addresses. The address a site sees is never the address apps connect to.
- The tunnel listens on the entry address only. The WireGuard port is open on that address and nowhere else.
- Users cannot reach the server or each other from inside the tunnel. Both were tried in our behaviour check and both were blocked.
- WireGuard's handshake has a defence against floods, which lets a busy server answer with a small cookie before doing any costly work.
The tests behind these lines are on how we check.
What has not been done
- No outside security audit of the website, the server or the apps.
- No published app code. The app's code is not public.
- No paid reward programme.
If any of these changes, this page will say so, with the date.