Reporting a security problem
If you have found something, we want to hear it, and we will not make you regret telling us.
How to reach us
Where to send it
Include enough to reproduce it. If you would rather encrypt the report, ask us for a key first.
What we will do
Acknowledge within one working day, tell you our assessment within five, and keep you updated until it is fixed. If we disagree that it is a vulnerability we will explain why rather than going quiet.
Our commitment to you
We will not take legal action against you, or ask anyone else to, for research carried out in good faith under the terms below. We will credit you publicly if you want the credit, and stay quiet if you do not.
Bounties
We do not run a paid bounty programme yet. Saying so up front seems better than letting you assume there is money in it.
Testing we welcome
- This website and our account system.
- Our VPN servers and DNS resolvers, from an account you control.
- The configuration files we generate, and how we generate them.
Please don’t
- Access, modify or delete data belonging to another customer. If you find you can, stop and tell us.
- Run denial-of-service or volumetric tests against production.
- Use social engineering against our staff or our suppliers.
- Publish before we have had a reasonable chance to fix it. Ninety days is our default and we will usually be much faster; if we are dragging, say so and we will agree a date.
Out of scope
- Findings from automated scanners with no demonstrated impact.
- Missing headers or cookie flags with no exploitable consequence.
- Issues in the WireGuard client itself — those belong with the WireGuard project, not us.
- Reports that a VPN does not provide anonymity. We agree, and we say so on our own site.
Machine-readable
The same contact details are published at /.well-known/security.txt.