Double VPN

A double VPN, sometimes called multi-hop, chains two VPN servers so your traffic is encrypted, sent to the first server, then re-routed to a second before reaching the internet. The point is that the first server sees your real IP but not your destination, while the second sees your destination but not your real IP — no single hop links both ends. It is the VPN equivalent of a proxy chain, trading speed for an extra layer of separation.

In a multi-hop design, traffic reaches an entry and then an exit; the destination sees the exit IP. Additional hops can add latency and limit throughput, but the effect depends on routing and capacity. Two servers operated by one provider do not create two independent trust domains. A no-logs policy is a separate claim, not proof that multi-hop prevents correlation.

Selectable exits do not constitute a built-in multi-hop chain. Additional hops need explicit routing and testing; they do not guarantee anonymity. s4m supports WireGuard and OpenVPN profiles. The issued profile and client routing determine the exit and which traffic follows the tunnel. Consult the published privacy policy and technical descriptions for their scope; IP assignment alone does not establish a no-logs or anonymity guarantee. Related topics: WireGuard, OpenVPN, no-logs, RAM-first, proxy.