Home/Answers/Wi-Fi security

Wi-Fi security · Plain-English answer

Is online banking safe on hotel Wi-Fi?

Mostly, yes, in the sense that matters most: your bank's HTTPS connection encrypts your login, balance and transactions the same way it does at home, so hotel Wi-Fi does not hand your password to anyone casually watching the network. What it does not hide is which bank you use, your DNS lookups, or whether the network itself has been tampered with, and that gap is what a VPN closes. Neither HTTPS nor a VPN does anything about phishing, a bank app with its own flaws, or a device that is already compromised.

What HTTPS on your bank's site already protects

Every mainstream bank forces HTTPS on its website and apps, which means the entire content of your session, your password as you type it, your account numbers, your balance, and any transfer you authorise, is encrypted between your device and the bank's servers. This is strong, well-tested cryptography. A hotel network operator, another guest on the same Wi-Fi, or someone running packet-capture software in the lobby cannot read any of that traffic, whether you are at home or three time zones away. This part of the picture has not changed in years, and it is the main reason online banking abroad is far safer than its reputation suggests.

What HTTPS does not hide is the metadata around that encrypted session. The server name you are connecting to is visible in the TLS handshake unless the network specifically supports encrypting it, so a hotel router can typically tell that you connected to your bank's domain, even though it cannot see what you did there. Before that handshake even happens, your device usually asks the hotel's own DNS resolver to look up the bank's address in plain text, which reveals the same thing a step earlier and a little more clearly, since DNS queries are rarely encrypted on a hotel network by default. A captive portal, the login page hotels use before granting internet access, sits in front of all of this and can redirect or inspect unencrypted traffic, though it cannot read inside an HTTPS session once it is running. An evil-twin hotspot, a fake access point broadcasting a name copied from the real one, controls DNS entirely and can try to steer you toward a convincing fake login page, hoping you do not notice a mismatched address or a missing padlock. Mobile banking apps that use certificate pinning, where the app refuses to trust any certificate except the bank's own even if the device's wider trust store has been tricked, close off one more version of that trick that a browser visiting the bank's website in a tab does not automatically get.

What a VPN adds on a shared network

A VPN wraps everything your device sends into one encrypted tunnel to a server you choose, before any of it reaches the hotel's router. On a shared network that changes the picture in a few concrete ways. The hotel or airport operator, and anyone else on the same Wi-Fi, no longer sees which bank's domain you are contacting, only that you are connected to a VPN server. Your DNS lookups travel inside that same tunnel instead of going to the hotel's resolver in plain text, so the quiet way of noting "the guest in room 412 banks with a particular provider" disappears. An evil-twin hotspot loses most of its leverage too: even if you connect to a fake access point by mistake, the VPN tunnel is authenticated against your real VPN server, not the local network, so a fake hotspot operator cannot read your traffic or swap in a different certificate to intercept it.

None of this duplicates what a VPN does on hotel or airport Wi-Fi generally, since the risks of a shared, badly managed network are the same whether you are checking a bank balance or reading email. For the wider picture of what those networks get wrong and how to connect to them safely, see is hotel and airport Wi-Fi safe; what changes here is specifically what is at stake when the site in question is your bank, and what the VPN still leaves for you to handle yourself before and after that handshake, such as the captive portal step itself, which usually has to be completed before the VPN tunnel can start.

What a VPN does not protect against

This is the part worth being honest about, because it is easy to treat a VPN as a complete answer to online safety when it only ever secures the network journey, not what happens at either end of it.

  • Phishing. A VPN encrypts the connection to whatever site you visit, including a convincing fake one. If an email, text, or fake hotel portal link leads you to a lookalike banking page and you type your details in, the VPN protects that journey just as faithfully as it would the real site.
  • A device that is already compromised. Spyware or a keylogger running on your phone or laptop captures what you type before it ever reaches the VPN tunnel, so encrypting the network afterwards changes nothing.
  • A bank app or site that is itself insecure. If the bank's own servers are breached, or its app has a coding flaw that exposes data after you have logged in, that is a problem on the bank's side of the connection, entirely outside anything a VPN reaches.
  • SMS one-time code interception. Codes sent by text travel over the mobile phone network, not Wi-Fi, so a VPN has no visibility into them at all. SIM-swap fraud and malware that reads text messages on a compromised phone both bypass a VPN completely, which is why an authenticator app is worth switching to if your bank offers one.
  • Card skimming. A tampered card reader or cash machine abroad is a physical attack on the card itself, with no network component for a VPN, or any software, to intervene in.

None of this is a reason to skip the VPN on hotel Wi-Fi. It is a reason to treat it as the layer that closes the network gap, alongside habits that cover what it cannot reach.

Before you log in abroad: a checklist

  • Confirm the exact Wi-Fi network name with hotel staff rather than picking the strongest signal in the list.
  • Connect your VPN before opening your banking app or any browser tab involving money.
  • Prefer your bank's dedicated app over its website in a hotel browser; most banking apps pin their certificate, which a browser tab does not.
  • Turn on login and transaction alerts so unusual activity reaches you immediately rather than at your next statement.
  • Switch one-time codes from SMS to an authenticator app before you travel, if your bank supports it.
  • Avoid typing card or banking details on a shared computer in a hotel business centre or lounge.
  • Check a card reader or cash machine for loose or added parts before inserting a card, especially somewhere unfamiliar.
  • Keep your phone's operating system and your banking app updated before you leave, since patches close the flaws attackers rely on.

Related questions

Can hotel Wi-Fi see my banking passwords?
No, not the password itself, because HTTPS encrypts it before it leaves your device. The hotel's network and anyone sharing it can usually still see that you connected to a particular bank's servers, through the DNS lookup and the server name in the connection, unless a VPN hides that too.
Does a VPN protect online banking from fraud?
Not from fraud itself. A VPN encrypts the network journey between your device and its server, which stops a hotel network or an evil-twin hotspot from reading or tampering with your connection. It does nothing against phishing pages, a bank app with its own flaws, SMS codes intercepted off the phone network, or a card skimmer at a cash machine.

Keep reading

More from the ROOT VPN answers hub.

Private in one tap.

ROOT VPN is free to start with unlimited data, no card needed, and no activity logs.

Get ROOT VPN, free