How WrapVPN works
How WrapVPN works, from the WireGuard tunnel and the configuration your device receives to DNS filtering and what happens when the tunnel stops.
This page explains how WrapVPN works: the tunnel, the configuration your device receives, the exit server, how a server location is chosen, how DNS and Clean Web work, and what happens when the tunnel stops. Each section also states the limits of the part it describes.
01 · The tunnel
The WireGuard tunnel and its handshake
Your traffic travels through a WireGuard tunnel between your device and the exit server you select, which is the WrapVPN server that forwards your traffic to the internet. WireGuard encrypts traffic with ChaCha20-Poly1305 and uses Curve25519 for key exchange. On Android, a setting can switch the connection to AmneziaWG, an obfuscated variant of WireGuard for networks that block WireGuard.
WireGuard consists of a few thousand lines of code, whereas older VPN protocols are many times larger. A smaller code base is easier to review in full, although its size alone does not make it more secure.
A WireGuard handshake completes in a single round trip, whereas older protocols need several. This matters most on phones, which change networks often, for example from Wi-Fi to mobile data or from one access point to another. The tunnel continues across these changes, and when a new handshake is needed, it takes one round trip.
02 · The configuration
What your device receives when it connects
Each time you connect, the app requests a tunnel configuration from our server for the exit server you selected. The configuration contains a tunnel address, the server's endpoint and the keys, including your private key. The app sets the DNS resolver, and there are no files or keys to import.
The design involves a trade-off: there is nothing to copy between devices, keep in sync or configure incorrectly, but our servers generate and hold the configuration, including the private key. A design in which your device generated its own keys and sent us only the public key would give you more control over them, and WrapVPN does not use that design.
03 · The exit server
What the exit server sees
Your traffic leaves the tunnel at the exit server and continues to the internet from there. Websites and services that you reach see the exit server's IP address instead of the one your network assigned to you.
The exit server forwards your packets, so it knows the addresses they are sent to. It cannot read the content of HTTPS traffic, which covers most traffic from current applications and browsers, but traffic that is not encrypted can be read on the server. A VPN therefore changes who can observe your connections: the local network, such as a café, hotel or airport network, no longer can, and the exit server can.
04 · Server location
How a server location is chosen
When the app starts, it measures the latency to each server location, and the server list shows that figure beside each location. On Android and Windows, you can let the app choose the fastest server; on iPhone, iPad and Mac, the app pre-selects the fastest location when it opens, unless you are already connected or have chosen a location. You can always choose a location yourself from the server list, and changing location closes the tunnel and opens a new one.
Distance on the network is not the same as distance on a map. Routes run through the places where networks exchange traffic directly, so a well-connected city further away often performs better than a poorly connected one nearby. Distance also sets a physical limit: light travels roughly 200 kilometres per millisecond in optical fibre, and a round trip covers the distance twice, so a server on the other side of the world always responds more slowly, whatever the protocol.
05 · DNS
DNS resolution and Clean Web
When Clean Web is on, your device's DNS queries are answered by a resolver on the exit server. The resolver refuses to answer for domains on an advertising and tracking blocklist, so the device receives no address to connect to. It also enforces SafeSearch on Google, Bing, DuckDuckGo, Ecosia, Yandex, Pixabay and YouTube, and forwards other queries to Cloudflare (1.1.1.1) or Google Public DNS (8.8.8.8). When Clean Web is off, DNS queries go through the tunnel to Cloudflare or Google Public DNS. In both cases, those resolvers see the exit server's IP address, not yours.
Because the lookup is refused, nothing is downloaded from a blocked domain, which also reduces data use. An app that uses its own DNS service, such as DNS over HTTPS, bypasses Clean Web. Clean Web is on by default on Android and off by default on iPhone, iPad, Mac and Windows. It is a switch in Settings, except on Windows, where it is on the main screen; the app remembers your choice, and Clean Web works only while you are connected.
Because Clean Web blocks by domain name, a tracker served from the same domain as the content you want is not blocked. It is not antivirus software, it does not block malware or phishing sites, and apart from SafeSearch it does not filter content. The counter in the app shows refused lookups, not advertisements you would otherwise have seen.
06 · When the tunnel stops
Traffic outside the tunnel
The tunnel is maintained by the operating system's VPN service, or on Windows by a background service, so closing the app does not end it. On Windows, closing the window keeps the app running in the notification area. The tunnel ends when you disconnect, when you turn the VPN off in the system settings, or when another VPN app takes over the connection.
Changing network, for example from Wi-Fi to mobile data, does not stop the tunnel. Traffic can travel outside the tunnel while the tunnel is not running: before you connect, while the connection is paused, during a change of server location, after you disconnect, and for about two seconds when the Android or Windows app restarts the tunnel after a long interruption. On iPhone, iPad and Mac, a connection that an app opened before the tunnel started can also continue outside it until that connection closes, and Auto-Connect brings the tunnel up shortly after the device joins a Wi-Fi network, not before.
On Windows, a firewall rule blocks traffic outside the tunnel while the tunnel is running; the rule does not apply while the tunnel is stopped. WrapVPN has no kill-switch setting on any platform. To have the tunnel running when your device joins a network, connect before you switch to it, for example while you are still on mobile data. On a network with a sign-in page, complete the sign-in first, because no traffic can pass through the tunnel until the network admits you.
Limitations
A VPN changes who can observe your connections, but it does not make you anonymous: signed-in services, cookies and what you type still identify you. It does not protect a device that is already compromised, and it cannot pass traffic on a network that has not yet admitted you, because nothing can travel through the tunnel until the network's sign-in page, known as a captive portal, has been accepted. The features page lists the other limitations.
View all limitationsStart with the free plan
The free plan includes three one-hour sessions a week, with the same features as the paid plans. No card is required.