DoubleVPN

A standard VPN connection runs through one server. That server knows both who you are (your real IP address) and where you are going (the sites you visit). Double VPN, often called multi-hop, adds a second server to the chain so that no single server holds both pieces of information. Websites see only the IP address of the last server.

How it works

The most common design nests one encrypted tunnel inside another, built on your device:

1. Your app encrypts the traffic for the exit server, then wraps that in a second layer of encryption for the entry server.
2. The entry server removes the outer layer. It sees your real IP and that you are talking to the exit server, but the contents and final destination stay encrypted.
3. The exit server removes the inner layer and sends the traffic to the website. It sees the destination but only knows the request came from the entry server.

Some providers use a different setup: the first server decrypts your traffic and re-encrypts it toward the second server, or the first hop is a proxy and not a full VPN tunnel. These still change your visible IP twice, but the entry server may see more than in the nested design. Provider documentation usually says which method it uses.

Entry and exit servers are often in different countries. Some services only offer fixed pairs, others let you pick both hops.

When it helps

• Splitting trust between servers. If one server is seized, monitored or misconfigured, it doesn't reveal both your identity and your activity.
• High-risk work. Journalists, researchers and activists facing well-resourced adversaries get an extra step that makes tracing harder.
• Hostile networks or jurisdictions. Routing first through a server in a privacy-friendly country, as some "secure core" designs do, keeps the first point of contact away from local surveillance.

For everyday browsing, streaming, gaming or torrenting, a single well-configured VPN with a solid no-logs policy is usually enough.

Limits and risks

• Speed. Two hops add latency and extra processing. Expect slower speeds and higher ping, especially when the servers are far apart.
• One provider runs both hops. If the same company operates both servers, a provider that logs or is forced to cooperate could still link entry and exit traffic. Double VPN spreads risk across servers, not across organisations.
• Encryption strength barely changes. One layer of AES-256 or ChaCha20 is already not practically breakable. The second layer is there to separate metadata, not to make the content harder to crack.
• It does not bypass censorship by itself. Deep packet inspection can still spot VPN traffic. For blocked networks you need obfuscated servers or stealth protocols.
• It does not anonymise you. Logged-in accounts, cookies, browser fingerprinting and DNS or WebRTC leaks can still identify you. A kill switch and leak protection matter just as much.
• Limited choice. Multi-hop is often limited to certain servers, countries or protocols, and is sometimes only on paid or higher plans.

Double VPN vs Tor and VPN chaining

Chaining two providers removes the single-company risk but is harder to set up. Tor spreads trust across independent relays but is much slower and blocked by many sites.

What to check when comparing tools

• Implementation: nested tunnels built on your device, or decrypt and re-encrypt on the first server.
• Server control: can you pick both entry and exit, or only fixed pairs?
• Entry server security: owned or rented hardware, RAM-only servers, location of entry points.
• Protocol support: whether multi-hop works with WireGuard, OpenVPN or only one of them.
• Audits: an independently audited no-logs policy matters more with multi-hop, since the provider sees both ends.
• Plan and platforms: whether the feature is on your plan and on every app you use.
• Speed: test a nearby pair and a distant pair before you commit.