Skip to content

Free slots reset daily at 00:00 & 12:00 (GMT+0)

Getting started

What is an SSH tunnel? A plain-English guide

How an SSH tunnel encrypts the traffic between your device and a server, what your local network and the server can still see, and when a tunnel helps.

7 min read · Updated 17 Nov 20267 min readUpdated 17 November 2026
Concrete tunnel lined with warm white LED frames that spiral toward a bright opening, reflected in still water
Photo: Liuuu _61 on Pexels

By LitronSSHPublished 24 October 2026Updated 17 November 2026How we write and check our guides

SSH stands for Secure Shell. It was created so that people could log in to remote computers without sending passwords across the network in readable form. The same encrypted connection can also carry other traffic, and that is what an SSH tunnel is: your apps' data travels inside an encrypted SSH connection to a server, and the server passes it on to the internet.

This guide explains how that works, what a tunnel hides and what it doesn't, how it differs from a full VPN, and when it is genuinely useful. No technical background needed.

How an SSH tunnel works

Think of a sealed pipe between two points: your device at one end and an SSH server at the other. Whatever goes in at your end comes out at the server, and nobody along the way can read it. Here is what happens when you tap connect:

  1. Your app opens an ordinary network connection to the server's address, on a port from your account details. Depending on the server, the details can list several ports, for example WebSocket and Dropbear ports.
  2. The two sides agree on fresh encryption keys for this session through a key exchange. The keys themselves never cross the network, so someone watching the connection cannot work them out.
  3. The server proves who it is with its host key. Then your app logs in with your username and password, which already travel encrypted.
  4. From then on, your traffic is wrapped in encrypted SSH packets. The server unwraps it, forwards it to the website or app you wanted, and sends the replies back through the same pipe.

On Android, tunnelling apps such as HTTP Custom and HTTP Injector use the phone's built-in VPN feature to steer your apps' traffic into the SSH connection, which is why Android asks you to allow a VPN connection the first time. On a computer the mechanism is easier to see: the command ssh -D 1080 user@host opens a small SOCKS proxy on your machine, and any browser you point at that proxy sends its traffic through the tunnel.

Desktop clients such as PuTTY and Bitvise SSH Client show the server's host key the first time you connect, ask you to accept it and remember it. That check stops another machine from pretending to be your server, so if the app later warns that the key has changed, double-check the host before continuing.

Who can see what

A tunnel doesn't make your traffic disappear; it moves the point where it becomes readable from the network you are on to the server. Here is what each party sees.

  • Your local network (the café Wi-Fi, the hotel router, the mobile network you are on) sees that your device is connected to one server address, when, and roughly how much data moves. It cannot read the contents or see which websites you open inside the tunnel.
  • The tunnel server removes the SSH layer, so it can see which addresses your traffic is going to. When a website uses HTTPS (the padlock in your browser), the page itself stays encrypted between you and that website, even at the server.
  • The websites you visit see the server's IP address instead of yours. You can check this with Check My IP: with the tunnel on, it shows the server's address.

Our privacy policy says we do not record which websites you visit or what you send through our servers; the servers keep only what they need to run, such as whether an account is active. Even so, keep using HTTPS sites with any tunnel, so your most sensitive data is protected end to end no matter who runs the server.

One detail is easy to miss: DNS lookups, the step where your device turns a name like example.com into an address. If an app makes its lookups outside the tunnel, the local network can still see which site names it looks up. The privacy basics guide covers more habits like this.

SSH tunnel or full VPN?

On a phone the two feel the same: you tap connect, a key or VPN icon appears in the status bar, and your apps go through the server. Under the hood there are real differences.

SSH tunnelFull VPN (for example WireGuard or OpenVPN)
Carries TCP connections, which most web pages and apps use, inside one encrypted SSH sessionCarries whole network packets, whatever kind they are
UDP traffic, used by many games and voice calls, needs extra support in the app or may not workUDP traffic works natively
Logs in with a username and password in widely used appsUsually needs a configuration file or key imported into a dedicated app
On a patchy signal, one lost packet holds up everything inside the tunnelUsually copes better with lost packets

The last row needs a word of explanation. Because everything inside an SSH tunnel shares one TCP connection, a single lost packet makes every app wait until it is sent again. On a stable line you won't notice; on weak mobile coverage the connection can feel sluggish, which is why UDP-based protocols such as Hysteria 2 exist. The protocol guide compares the options.

When an SSH tunnel is useful

  • Public Wi-Fi. In cafés, hotels, airports and stations you share the network with strangers and can't know how it is run. With a tunnel, anyone running or watching that network only sees encrypted traffic to one server.
  • Keeping your browsing private from the local network. On any shared connection, such as a guest network or a flat's shared router, the tunnel keeps the list of sites you visit away from the other people on it.
  • A consistent address. As long as you stay on the same server, websites see the same IP address, even when your phone switches between Wi-Fi and mobile data.
  • Learning how networks work. SSH is one of the most widely used tools in computing, and setting up a tunnel, reading the connection log and comparing your IP address before and after is a hands-on way to understand encryption, ports and proxies.

Whatever your reason, use a tunnel on networks where that is allowed, follow the network's terms and the law, and keep to our acceptable use policy. A tunnel changes how your traffic travels; it does not make anything acceptable that otherwise isn't.

What a tunnel does not do

  • It doesn't make you anonymous. Websites still recognise you when you log in, and cookies work exactly as before.
  • It doesn't protect you from malware or phishing. A fake login page is just as dangerous through a tunnel.
  • It doesn't encrypt beyond the server. Between the server and a website, only HTTPS protects your data, so the padlock still matters.
  • It isn't automatically faster. Your traffic takes a detour through the server. A nearby server keeps that detour short; see choosing a server location.

Try it yourself

  1. Open Check My IP and note the address and provider it shows.
  2. Choose SSH from the list of services, pick a country and a server near you, and create an account. Copy the details straight away: they are shown only once.
  3. Enter the host, port, username and password in your tunnelling app and connect. The HTTP Custom guide walks through this step by step.
  4. Reload Check My IP. It should now show the server's address and a note that you are browsing through one of our servers.
  5. Disconnect when you are done. The account keeps working until it expires, and My accounts in this browser shows how much time it has left.

Try it with a free account

Choose a protocol, then a server near you. Your details are shown once, so save them before you leave the page.

Questions

Is an SSH tunnel safe to use on public Wi-Fi?
Yes, that is one of its best uses. The Wi-Fi network only sees encrypted traffic going to one server. Keep using HTTPS sites as well, so your data stays protected after it leaves the server.
Can I use the same account on my phone and my laptop?
Please don't. One account is meant for one device: a second login usually disconnects the first, and the server may block the account. Create a separate account for each device instead.
Can this site see the websites I visit?
Our privacy policy says we do not record which websites you visit or what you send through our servers. Technically, any tunnel server handles your traffic on its way out, which is why HTTPS still matters.