Working From Public Wi-Fi as a Developer - What a VPN Covers and What It Does Not
Short answer: on cafe, hotel or co-working Wi-Fi, HTTPS, SSH and git-over-SSH already encrypt your content. What leaks is metadata: which hosts you connect to, your DNS lookups, and anything a tool sends in clear text. A
Short answer: on cafe, hotel or co-working Wi-Fi, HTTPS, SSH and git-over-SSH already encrypt your content. What leaks is metadata: which hosts you connect to, your DNS lookups, and anything a tool sends in clear text. A VPN closes those gaps on the local network. It does not fix a phishing page, a leaked token or a compromised laptop.
Disclosure: I work on CasperVPN, a VPN app. The checks below work with any reputable VPN.
Checked on 18 November 2026.
What the Wi-Fi operator (or anyone on the network) can see
| Traffic | Without a VPN | With a VPN |
|---|---|---|
| HTTPS sites and APIs | The host names (SNI, DNS), timing, volume | Only that you talk to the VPN server |
ssh, git over SSH |
The server address and port | Only the VPN server |
| DNS lookups | Every name you resolve, unless your OS uses encrypted DNS | Inside the tunnel |
Plain HTTP, old internal tools, local dev servers on 0.0.0.0
|
Content too | Content leaves the laptop encrypted; the local dev server is still exposed to the LAN |
Five checks before you work on shared Wi-Fi
-
Bind dev servers to localhost.
npm run dev -- --host 127.0.0.1(or your framework's flag). A VPN does not stop another guest on the same Wi-Fi from reaching a port you opened to the LAN. - Turn on the firewall (macOS: System Settings > Network > Firewall; Windows: mark the network as Public).
- Check the network name with staff. A fake hotspot can serve you a fake login page; HTTPS warnings are your signal, never click through one.
- Connect the VPN after the captive portal. The hotel or cafe login page has to load first, then turn the VPN on and leave it on. A kill switch stops traffic if the tunnel drops when the Wi-Fi reconnects.
- If the VPN will not connect, change protocol. Some guest networks only allow ordinary web traffic; OpenVPN over TCP often still connects when other protocols do not.
What a VPN does not do
- It does not protect a token you paste into the wrong page.
- It does not hide you from the services you log in to.
- It does not replace your company's own VPN for reaching internal systems; that one is for access, a personal VPN is for the local network.
How to verify your VPN is actually working (2 minutes)
- Check your public IP before and after connecting (any "what is my IP" page).
- Run a DNS leak test; the resolvers shown should belong to the VPN, not the cafe's ISP.
- Turn Wi-Fi off and on with the VPN connected and watch whether traffic stops (kill switch) or leaks.
About the author
I work on CasperVPN, an iPhone, iPad and Android VPN (Mac app coming) with WireGuard, OpenVPN (UDP and TCP), IKEv2 (iPhone and iPad) and CasperCloak, our own protocol. Free plan: 0.5 GB a month, no card. Premium adds unlimited data, every location, kill switch and Double VPN, with a 7-day free trial on the App Store and Google Play. Longer guide: https://caspervpn.com/guides/vpn-public-wifi
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.