VPN technology hub

Updated 21 September 2026 · How we research

A VPN is not one technology. It is a stack: a tunnelling protocol that moves your packets, a cipher suite that protects them, a key exchange that authenticates both ends, and a set of operating-system controls that decide what happens when any of those fail. This hub explains each layer and shows where ZoogVPN's implementation sits within it.

How a ZoogVPN connection works

Encryption protects the path to the VPN server; the server then forwards traffic to its destination.

  1. Your device

    Original IP and traffic

  2. ENCRYPTED
  3. ZoogVPN server

    Tunnel endpoint and IP exit

  4. FORWARDED
  5. Internet

    Sites see the server IP

Important

A VPN protects network traffic in transit; it does not replace device security, strong passwords or account protection.

The path a packet takes once a VPN tunnel is established. Each stage is covered in detail on the linked pages below.

The four layers that matter

Tunnelling

How packets are wrapped and moved. See how a VPN works and the protocol comparison.

Encryption and authentication

Which ciphers protect the payload and how each end proves its identity. See VPN encryption.

Failure handling

What happens when the tunnel drops. See kill switches and leak protection.

Routing policy

Which traffic uses the tunnel at all. See split tunneling and router setup.

Traffic visibility

Whether a network can tell you are using a VPN. See obfuscation.

What is recorded

Connection, activity and diagnostic logs are different things. See logging explained.

Choosing a protocol

Most connection problems people blame on a VPN are protocol mismatches. A UDP protocol on a network that throttles UDP will feel broken. A TCP protocol on a long-haul route will feel slow. The decision tree below reflects the trade-offs explained across this cluster.

Choose a ZoogVPN protocol by priority

Availability can vary by platform. Confirm the current app before publishing platform-specific claims.

What matters most for this connection?

Start with the user's network, device and threat model—not a universal “best” protocol.

Source basis: ZoogVPN Help Center protocol guide. Treat performance labels as vendor guidance until independently tested.

A protocol decision tree. Start with the network you are on, not the speed you want.

Protocols ZoogVPN publishes in its help centre, retrieved 21 September 2026. Availability is stated by the vendor and may change.

ProtocolPlatforms (per ZoogVPN)ZoogVPN's stated use case
WireGuardWindows, macOS, iOS, Android, Linux, routersSpeed and modern use cases such as streaming and gaming
IKEv2/IPsecWindows, macOS, iOS, Android, LinuxMobile users and keeping a connection alive while switching networks
OpenVPN (UDP)Windows, macOS, iOS, Android, Linux, routersBalanced speed and security; torrenting and streaming
OpenVPN (TCP)Windows, macOS, iOS, Android, Linux, routersStable connections in firewalled environments
ShadowWindows, macOS, iOS, AndroidBypassing censorship in highly restricted regions
ZoogTLSWindows onlyAccessing restricted content in heavily filtered networks such as Iran

According to ZoogVPN

ZoogVPN lists six protocols across its apps, including two proprietary options: Shadow, for restricted regions, and ZoogTLS, which the help centre describes as Windows-only. We have not independently verified platform availability or performance.

Where to go next