---
title: "Mullvad VPN: which ports it uses on a Mac, and what breaks if you block it · Kilobat"
url: "https://kilobat.app/processes/mullvad-vpn"
description: "Mullvad VPN uses WireGuard on UDP, with port options and anti-censorship modes. Which ports the app can use, which it blocks, and what breaks if you block it."
---

# What is Mullvad VPN?

Mullvad VPN sends your traffic through a WireGuard tunnel to a Mullvad server. Its settings let you pick the port, and wrap the tunnel for networks that block VPNs.

**Fix this with your agent**Copies a prompt for Claude Code, Codex or any agent that can use Terminal.

I want to know what Mullvad VPN is doing on my Mac and whether its network use is normal. Read https://kilobat.app/processes/mullvad-vpn.md and work through it with me. Install the Kilobat CLI if it’s missing: brew install seifip/kilobat/kilobat. Run the guide’s Terminal and kilobat checks yourself and tell me what you find. List the steps only I can do. Ask before you change any setting.

Process: `Mullvad VPN` · Also seen as: `Mullvad` · Made by Mullvad VPN · Applies to: Mullvad VPN desktop app on macOS 14 Sonoma and later. Checked on 8 November 2026 against Mullvad's help. · Checked: 8 November 2026

## Short answer

Mullvad's VPN app. It tunnels your traffic with WireGuard over UDP and can disguise it with LWO, QUIC, Shadowsocks or UDP-over-TCP on other ports.

Block with care

Blocking Mullvad stops the tunnel. Its kill switch is always on, so the app can leave this Mac without internet while the tunnel is down.

Path

`/Applications/Mullvad VPN.app`

## What it is

Mullvad removed OpenVPN from its desktop app in version 2025.14. Its post says that anyone who used OpenVPN moves to WireGuard automatically.

In the app, the WireGuard port can be set to 51820, to 53, or to a custom port such as 123. Mullvad's guide says that this method does not hide the traffic, but it helps against firewalls that only block certain ports.

Mullvad lists four wrappers under Settings › VPN settings › Anti-censorship. LWO uses a random port by default, and you can enter a custom port such as 53. QUIC uses UDP port 443.

Shadowsocks uses a random port, often between 51900 and 51949, when set to Automatic. You can enter 443 as a custom port. UDP-over-TCP runs WireGuard over TCP, and you can choose port 80, 443 or 5001.

Mullvad says that its bridge servers help the app reach the website, the API and the WireGuard servers where access is blocked. Settings › API access lets you test the methods that the app uses.

Mullvad says that its servers block outbound traffic to port 25, to ports 137, 138, 139 and 445, and to ports 1900 and 2869. These are rules on Mullvad's side.

## Why it uses the network

- **The tunnel.** The app sends your traffic to the Mullvad server that you pick, inside WireGuard.
- **Account and server list.** The app talks to Mullvad's API to log in and get server information. Mullvad's guide describes the API as something that can be blocked, so the app has API access methods.
- **Kill switch.** Mullvad's FAQ says that the app has a kill switch that is on by default and cannot be turned off. It protects your traffic if the tunnel fails.
- **Local network sharing.** Mullvad's FAQ says that you can turn on Local network sharing in the app's preferences if local shares and printers stop working while connected.

## How much is normal

While connected, almost all of this Mac's internet traffic goes through the tunnel. Its size is the size of what your apps send, plus overhead.

Mullvad's pages give no figure for the overhead or for idle traffic.

The destination of your traffic is a Mullvad server address. Your own destinations are inside the tunnel.

## When it uses a lot, and why

- **Downloads and streaming.** Anything that your apps transfer while connected goes through the tunnel.
- **Multihop.** Mullvad's guide describes Multihop, where you pick an entry and an exit server. It does not state the overhead.
- **Wrapped tunnels.** Shadowsocks, QUIC, LWO and UDP-over-TCP add a layer to every packet. Mullvad does not state how much.

## Is it safe to block?

Block with care

Blocking Mullvad stops the tunnel. Its kill switch is always on, so the app can leave this Mac without internet while the tunnel is down.

What breaks if you block it

- The tunnel cannot form, so the VPN does not connect.
- The kill switch blocks other traffic while the app is on and the tunnel is down.
- Login and server updates that use Mullvad's API fail, unless a bridge method works.

Blocking means a firewall rule that refuses its connections. Don’t quit or disable a macOS process to save data: macOS starts it again, and other features depend on it.

## Reduce its use

1. If the tunnel does not connect on a network, open Settings › VPN settings › Anti-censorship. Try a WireGuard port, then LWO, QUIC, Shadowsocks and UDP-over-TCP in turn.
2. Mullvad suggests Shadowsocks on port 443 for networks that block the default ports.
3. If local shares and printers stop working, open Settings › Preferences and turn on Local network sharing.

## See how much it uses

1. Open Activity Monitor and search for `Mullvad`. The Network tab shows the bytes that the app sent and received.

## With Kilobat

1. In the Kilobat app list, search for `Mullvad`. Its row shows the live rate and the hosts that it talks to.
2. Ask the same question in Terminal.

   ```
   kilobat explain Mullvad
   ```

The live view and the explanations are free. History in the app needs Kilobat Pro. Blocking needs Pro and the network filter: see the [network filter](https://kilobat.app/docs/blocking#filtering), [Protection](https://kilobat.app/docs/blocking#protection) and the [hotspot data saver](https://kilobat.app/save-hotspot-data).

## What isn’t documented

Mullvad's pages do not name the processes or the extension that the Mac app shows in Activity Monitor or nettop. The app path here is the usual install name, not a path from Mullvad's pages.

The pages in use do not give an outbound firewall allow list with server addresses. They list the ports that the app can use, not a single required set.

## Questions

**Which port does Mullvad use by default?**

Mullvad's guide lists 51820 and 53 as WireGuard port choices. It does not name a default in the pages used here.

**Is OpenVPN still available?**

No. Mullvad removed OpenVPN from its desktop app in version 2025.14.

**Can I turn the kill switch off?**

No. Mullvad's FAQ says that the kill switch is built in, on by default, and cannot be disabled.

## Sources

- [Mullvad Help: Using Mullvad VPN in restrictive locations](https://mullvad.net/en/help/connecting-to-mullvad-vpn-from-restrictive-locations)
- [Mullvad Blog: Removing OpenVPN from the Mullvad VPN app](https://mullvad.net/en/blog/removing-openvpn-from-the-mullvad-vpn-app)
- [Mullvad: Why Mullvad VPN?](https://mullvad.net/en/why-mullvad-vpn)
- [Mullvad Help: FAQ](https://mullvad.net/en/help/faq)

Checked on 8 November 2026.

## Related

- [nesessionmanager](https://kilobat.app/processes/nesessionmanager): Part of macOS. They run Network Extension sessions, such as VPNs and content filters, and host their plug-ins, so VPN traffic can show under them.
- [Tailscale](https://kilobat.app/processes/tailscale): Tailscale's VPN client. It talks to Tailscale's coordination servers over HTTPS, relays over TCP 443, and sends WireGuard traffic to your other devices over UDP.
