Pro free for a week: code NETMUTE
NetMute

Two ways to get NetMute

Both are free to download and contain the same features. They differ in how you buy Pro.

Mac App Store

The simple route

  • Pro is bought in the app with your Apple Account
  • No licence key to keep
  • Apple handles payment and refunds
Open the App Store

Direct download

Version 2.3.10 · 13 MB

  • Invoice with VAT ID, ready for expenses
  • 5- and 10-seat licences for teams
  • Unlocked with a licence key
Download the .dmg

The direct build is signed with a Developer ID, notarised by Apple and updates itself. Pro does not carry over between the two: a licence key works only in the direct build, an App Store purchase only in the App Store version.

Hotel Wi-Fi security on a Mac: what actually matters

Hotel Wi-Fi is reasonably safe for everyday use on an up-to-date Mac: HTTPS keeps the content of your traffic private. What it does not hide is which services you use and when, and a hotel is the one public network you live on for days. You join it in the lobby, your Mac remembers it, and for the next four nights it reconnects every time you open the lid, while you are at dinner, while you sleep, while the laptop sits in the safe. So the useful question is what your Mac does on a stranger's network for ninety hours at a stretch. This article covers what is different about hotel networks, what HTTPS already handles, and the short list of settings worth changing before you connect.

9 min readUpdated

Is hotel Wi-Fi safe? The short answer

Hotel Wi-Fi is reasonably safe for everyday use on an up-to-date Mac, and safer than its reputation. The classic warning, that someone two rooms away reads your passwords out of the air, is close to obsolete: almost everything that matters is encrypted in transit (HTTPS/TLS) before it leaves your Mac, and macOS and a current browser handle that without you doing anything.

The nuance is that encryption protects content, not context. Nobody on the hotel network reads your email, but the network can still see that your Mac contacted a particular mail provider, a particular cloud drive and a particular company VPN at 6:40 every morning for five days. Over a long stay that adds up to a record of your routine, and none of it required breaking a single connection.

Two things separate a hotel from a café. The first is identity: the login page usually asks for your surname and room number, so the operator can link every device and connection to a named guest rather than an anonymous person with a coffee. The second is duration: a café visit lasts forty minutes, a hotel stay means days of automatic reconnection and background sync while you are nowhere near the machine.

So the realistic risks are three: a Mac exposed for days to a network full of strangers, a detailed traffic timeline attached to your name, and the chance of joining a network that only looks like the hotel's. All three have straightforward answers.

What makes a hotel network different from other public Wi-Fi

Everyone in the building is on one network. Hotel guest Wi-Fi is often set up without client isolation, which puts the guest in room 412 and the guest in 118 on the same local network as you. Your Mac announces itself over Bonjour with whatever name you gave it, often your first name and the model, and any sharing service left on from an old project is reachable by everyone else. Some chains isolate guests properly, but you cannot tell from the outside, so assume they do not.

The login page ties traffic to a guest identity. Room number and surname, sometimes a loyalty number or an email address for the faster tier. That is not sinister; it is how the hotel enforces one account per room, and in some countries operators must keep connection logs anyway. It does mean "anonymous public network" does not apply here. Whatever the network records, it records against your name.

The equipment is often old and rarely touched. Hotel Wi-Fi is usually installed once by a contractor, managed remotely and left alone for years because it works. Access points and gateways go unpatched and default settings survive. That is not an attack in itself, but the network's own protections, including the isolation the brochure promised, may be misconfigured.

Login pages interfere with DNS by design. For the login page to appear, the gateway has to intercept your first requests and redirect them, which means intercepting DNS. Some keep doing it after you have signed in. That is also why encrypted DNS causes trouble in hotels: if your Mac uses a custom resolver or an encrypted DNS profile, the portal often cannot redirect you and the login page never loads, the most common hotel Wi-Fi complaint of all.

And then you stay. Auto-join means the Mac reconnects every time you open the lid. Multiply the normal background activity of macOS and a dozen apps by four or five days, and you are not on an untrusted network for one session but living on it.

What HTTPS already covers, and the metadata it does not

Start with the good news, because it is substantial. HTTPS encrypts the content of a connection: page contents, form fields, passwords, messages, app data. Browsers use HTTPS by default and warn before falling back to an insecure connection, TLS 1.3 is common, and the large majority of Mac apps encrypt their own traffic. Someone on the hotel network with a packet capture sees ciphertext. Harvesting logins from an open network stopped working years ago.

What encryption does not hide is that each connection happens, and its shape. The destination IP address is always visible, because packets have to be routed. DNS lookups are visible unless you use encrypted DNS, which portals often break. The server name at the start of a TLS connection is visible on most connections today, because Encrypted Client Hello is far from universal. And timing, size and frequency are visible to anyone on the path, however strong the encryption.

Collected over several nights, that metadata reveals more than people expect: which services you use, when you woke up, when you left the building and came back, how long your video calls ran and which employer's network you dialled into. A mail client checking every five minutes is a precise presence signal. None of that requires reading a single message. On a hotel network, metadata is the real exposure.

Some traffic is not protected at all. Local network discovery is unencrypted by nature, so mDNS and Bonjour announce your device name and its services to the whole guest network. Printer discovery, media sharing and anything built for a trusted home network behaves exactly the same in a hotel, because your Mac does not know the network has changed character. A few older apps also still check for updates over plain HTTP.

HTTPS only really fails when a person overrides it. If a certificate warning appears, do not click through it. If a network asks you to install a profile or a root certificate before you can go online, decline and use your phone's hotspot instead. A hotel needs your room number to let you online. It does not need the ability to issue certificates your Mac will trust.

What to actually do, in order of effect

Keep the Mac's firewall on and stop sharing anything. This is the most valuable step because it deals with the shared network directly. Turn the firewall on under System Settings > Network > Firewall, and in its Options turn on stealth mode so the Mac stops answering unsolicited probes. Then open System Settings > General > Sharing and check that File Sharing, Screen Sharing, Printer Sharing, Remote Login and Remote Management are off, and set AirDrop to Contacts Only. Know what the macOS firewall does not do: it filters incoming connections only and does not restrict what your own apps send out.

Cut background sync for the length of the stay. Turn on Low Data Mode for the hotel network under System Settings > Wi-Fi > Details next to the network. It reliably holds back Apple's own background work, such as software update downloads, App Store downloads and iCloud Photos. For other apps it is only an advisory flag that many developers never implemented, so also quit or pause your cloud sync clients and set Time Machine to back up manually. Less background traffic means less metadata and fewer surprises if the hotel limits or throttles the connection.

Use a VPN for the protection HTTPS does not give you. A VPN wraps everything, including DNS, in one tunnel to one address, so the detailed timeline collapses into a single encrypted connection. Two honest caveats: you move your trust from the hotel to the VPN provider, so choose one whose logging policy you have actually read, and a VPN does not stop any app from connecting. It changes the route, and every app still talks. Connect it after you have passed the login page, and turn on the kill switch if the app offers one.

Decide which apps may reach the network at all. This is the part a VPN cannot do. On a network you will use for days, most of your apps have no reason to talk: a browser, a mail app and the VPN usually cover everything you intend to do. Everything else can stay offline until you check out, which shrinks the metadata trail and the number of processes exposed to whatever else is on that network.

Join the right network, and leave it properly. Ask reception for the exact network name rather than guessing from the list, because a fake access point with a plausible hotel name costs almost nothing to set up and is one of the few genuinely common attacks left. A login page that asks for card details although reception said Wi-Fi is free is a reason to stop. If the hotel offers a network protected with WPA2 or WPA3, prefer it over a fully open one. At checkout, open System Settings > Wi-Fi > Details and choose Forget This Network, otherwise your Mac will rejoin any network with that name anywhere in the world.

Controlling what your Mac does while you sleep

A closed lid does not mean offline. Depending on its settings, macOS wakes for network access, runs scheduled maintenance, checks for updates and lets apps refresh in the background. Over four nights that can add up to hundreds of connections you never started, made while you were asleep or out, on a network you would call untrusted if anyone asked. None of it is malicious. macOS simply treats every Wi-Fi network as your own, which is right at home and wrong in room 412.

That is why this problem calls for per-app control. A VPN encrypts the route but every app still talks, and Low Data Mode asks politely while many apps ignore it. What actually reduces the exposure is deciding which handful of apps may go online, and having that decision applied automatically instead of remembered every evening.

NetMute is built for exactly this. The free version shows which apps are online on the hotel network, with their traffic in real time and the domains they contact, and takes any app offline with one switch. Temporary rules expire on their own, so letting an updater out for ten minutes does not leave a permanent hole, and allow-list mode reverses the default: nothing reaches the network except what you named.

With Pro, it happens on its own. Hotspot protection notices that you have joined an unknown network and applies a strict profile immediately, and it lets the hotel login page through instead of blocking it along with everything else. Network profiles belong to the network, so the hotel profile returns by itself the next time you join that network, and your home profile is back the moment you get home. If the hotel limits or throttles its connection, data limits per app stop the biggest consumers early.

The part people find most useful after a trip is the evidence. The traffic monitor and the per-domain log answer the question this article circles around: what exactly talked while you slept. It is worth checking once, because the list is usually longer than anyone expects, and it makes the profile for your next stay easy to write.

Frequently asked questions

Set it once, before you check in

NetMute shows which apps talk on the hotel network, even overnight, and takes any of them offline with one switch, for free. With Pro, a strict profile applies on unknown networks and the hotel login page still works.

Free on the Mac App Store

Free with no time limit · Pro $12.99 one-time

Download free