---
title: "Surfshark: which ports it uses on a Mac, which protocols it offers, and what breaks if you block it · Kilobat"
url: "https://kilobat.app/processes/surfshark"
description: "Surfshark tunnels traffic with WireGuard, OpenVPN, IKEv2 or Dausos. The default ports its blog lists, the protocol choices on a Mac, and what breaks if blocked."
---

# What is Surfshark?

Surfshark sends your traffic through an encrypted tunnel to a Surfshark server. The ports depend on the protocol, and Surfshark's blog lists the defaults.

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

I want to know what Surfshark is doing on my Mac and whether its network use is normal. Read https://kilobat.app/processes/surfshark.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: `Surfshark` · Also seen as: `Surfshark VPN`, `Dausos` · Made by Surfshark · Applies to: The Surfshark app on macOS 14 Sonoma and later. Checked on 8 November 2026 against Surfshark's support pages and blog. · Checked: 8 November 2026

## Short answer

Surfshark's VPN app. It tunnels your traffic with WireGuard, OpenVPN, IKEv2 or Dausos. Surfshark's blog lists a default port for each protocol.

Block with care

Blocking Surfshark's ports stops the tunnel from connecting. Block them only on a network where you do not use Surfshark.

Path

`/Applications/Surfshark.app`

## What it is

Surfshark's blog article on VPN ports says that the ports depend on the protocol. It lists WireGuard, OpenVPN and IKEv2.

The article gives these defaults. WireGuard uses UDP port `51820`. OpenVPN uses UDP port `1194` and TCP port `443`. IKEv2 uses UDP ports `500` and `4500`.

Surfshark's support article on protocols names OpenVPN, WireGuard and IKEv2. It says that the Surfshark app has two OpenVPN options, UDP and TCP.

It describes Dausos as Surfshark's own protocol. It says that Dausos is currently available in the Mac App Store version of the app.

The support article on connection problems says that different networks can have restrictions that stop a VPN connection. It tells you to try another protocol under **Settings › VPN Settings › Protocol**.

The blog article says that Surfshark does not offer port forwarding.

## Why it uses the network

- **The VPN tunnel.** The app sends your traffic to a Surfshark server over the protocol that you choose.
- **Protocol choice.** Surfshark says that UDP is faster and that TCP is more stable but may be slower.
- **Kill Switch.** Surfshark says that Kill Switch cuts off your internet connection if the VPN connection drops, until you reconnect. You turn it on in **Settings › VPN Settings**.
- **Post-quantum protection.** Surfshark says that the WireGuard option has post-quantum protection in the app. It says that manual configurations do not support it yet.

## How much is normal

Surfshark does not publish figures for idle traffic. While connected, the traffic that you route through the tunnel moves through the VPN server.

Surfshark says that it does not support IPv6. It advises you to turn IPv6 off when you troubleshoot on a Mac.

Surfshark's support article suggests that you try several countries if one server fails. This tells you whether the problem is one server or the app.

## When it uses a lot, and why

- **Everything you do online.** The tunnel carries your browsing, downloads and calls.
- **Repeated connection attempts.** Surfshark says that an app stuck on the Connecting status can point to a network restriction. Its steps start with a different server and a different protocol.
- **Antivirus or another VPN.** Surfshark says that an antivirus program or another VPN app can block the connection.

## Is it safe to block?

Block with care

Blocking Surfshark's ports stops the tunnel from connecting. Block them only on a network where you do not use Surfshark.

What breaks if you block it

- The tunnel fails when the port for the chosen protocol is blocked. Another protocol may still connect.
- The app stays on the Connecting status or shows an error notification.
- With Kill Switch on, a dropped tunnel cuts off your internet connection until you reconnect.
- A rule that blocks the app on an antivirus or firewall stops the connection.

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 a server fails, try a server in another country.
2. If the connection fails, change the protocol under **Settings › VPN Settings › Protocol**.
3. Add Surfshark to your antivirus exclusion list. Surfshark gives this advice.
4. Update the app. If the App Store version fails, Surfshark suggests the version from its own website, and the other way round.

## See how much it uses

1. Open Activity Monitor and search for Surfshark. Open the Network tab to see the bytes that the app and its helpers moved.

## With Kilobat

1. In the Kilobat app list, search for `Surfshark`.
2. Ask the same question in Terminal.

   ```
   kilobat explain Surfshark
   ```

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

Surfshark's pages that this entry uses do not give the bundle ID, the install path or the process names for the Mac app.

The port defaults come from a blog article, not from a firewall guide. Surfshark's support pages that this entry uses do not list ports.

Surfshark's pages do not give a port for Dausos. They do not give figures for idle traffic.

## Questions

**Which ports does Surfshark use?**

Surfshark's blog says that WireGuard uses UDP 51820, OpenVPN uses UDP 1194 and TCP 443, and IKEv2 uses UDP 500 and 4500. These are the defaults.

**Does Surfshark support port forwarding?**

No. Surfshark's blog says that it does not offer a port forwarding feature.

**Why can't Surfshark connect on my network?**

Surfshark says that some networks restrict VPN connections. It advises you to try another server, another protocol, and to check your antivirus.

## Sources

- [Surfshark blog: VPN ports explained](https://surfshark.com/blog/vpn-port)
- [Surfshark Support: What protocols can I use with Surfshark?](https://support.surfshark.com/hc/en-us/articles/360010324739)
- [Surfshark Support: How to fix unable to connect issues on macOS](https://support.surfshark.com/hc/en-us/articles/360021563580-How-to-fix-unable-to-connect-issues-on-macOS)
- [Surfshark Support: How to use Kill Switch](https://support.surfshark.com/hc/en-us/articles/360016978413-How-to-use-Kill-Switch)

Checked on 8 November 2026.

## Related

- [NordVPN](https://kilobat.app/processes/nordvpn): NordVPN's VPN client. Nord lists the outbound ports for each protocol, such as UDP 51820 for NordLynx and TCP 443 or UDP 1194 for OpenVPN.
- [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.
- [Surfshark on Mac: check the VPN and fix connection problems](https://kilobat.app/guides/surfshark-vpn-mac)
