Questions, corrections and test requests all go through the form below. It reaches one person and is answered by one person.
Worth writing about
- Corrections. A protocol default changed, a provider was acquired, an audit was superseded — tell us and the article is updated and dated. This is the most useful mail we get.
- “It leaks and I cannot work out why.” Send your platform, protocol and what the leak test showed. These questions usually become guides.
- Self-hosting problems. WireGuard and OpenVPN configs that almost work are a speciality here.
- Provider test requests. Tell us which one and why; reader demand decides most of the testing queue.
- Vendors submitting a service for testing, or disputing a published result with evidence.
Please do not send
- Credentials. Never send passwords, private keys, config files containing keys, or account details. If a config must be shared, strip every key first.
- Personal data belonging to other people. We do not want it and will delete it.
- Requests for legal advice. We cannot tell you whether a VPN is legal where you are, or what to do about a legal notice.
- Guest posts with a link. Nothing on this site is for sale, including links.
If you need to reach us privately
The form is fine for almost everything. For a genuinely sensitive report — a vulnerability in something we published, or a security concern about a provider — say so briefly in the form without details, and we will reply with an encrypted channel to continue on.
Reply time
Usually within two working days. Corrections are handled first and often the same day.
Send a message
Only the name, email and message you type are stored, and only until the exchange is finished. See the privacy policy — on a site about privacy, we would look ridiculous doing anything else.