---
title: "Tailscale: what it connects to on a Mac, which ports it uses, and whether to block it · Kilobat"
url: "https://kilobat.app/processes/tailscale"
description: "Tailscale builds a private network between your devices. Which servers and ports it uses on a Mac, and what breaks if you block them."
---

# What is Tailscale?

Tailscale connects your devices into one private network. On a Mac its traffic is small control messages to Tailscale's servers, plus the data that you send to your own devices.

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

I want to know what Tailscale is doing on my Mac and whether its network use is normal. Read https://kilobat.app/processes/tailscale.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: `Tailscale` · Also seen as: `IPNExtension`, `tailscaled` · Made by Tailscale · Applies to: Tailscale on macOS 14 Sonoma and later. Checked on 7 November 2026 against Tailscale's documentation. · Checked: 7 November 2026

## Short answer

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.

Block with care

Blocking Tailscale's hosts stops sign-in and device discovery, and the tunnel may drop. Block it only if you do not use it.

Path

`/Applications/Tailscale.app/Contents/MacOS/Tailscale`

## What it is

Tailscale's firewall article lists the traffic that a client needs. It is outbound TCP 443, UDP from source port 41641, UDP 3478 and, optionally, TCP 80.

TCP 443 goes to the coordination server, other backend systems and DERP relay servers. Tailscale advises against limiting it to chosen destinations.

The coordination servers are `controlplane.tailscale.com`, `login.tailscale.com`, `log.tailscale.com` and `console.tailscale.com`. The DERP relays are named `derpN-all.tailscale.com`.

Tailscale says that direct WireGuard traffic between devices uses UDP, with 41641 as the default port. Clients send STUN on UDP 3478, only to DERP servers, to learn their NAT type.

Tailscale's macOS page describes three variants. The Mac App Store variant uses a Network Extension. The standalone variant uses a system extension. The open source `tailscaled` has no app and uses the `utun` interface.

## Why it uses the network

- **Coordination.** The client signs in and gets the list of your devices and their keys from the coordination server over HTTPS.
- **Direct device traffic.** When two of your devices can reach each other, Tailscale sends WireGuard packets between them over UDP.
- **Relayed traffic.** When a direct path fails, traffic goes through a DERP relay over TCP 443. Tailscale says that clients use TCP 80 for captive portal checks on relays.
- **Logging.** Tailscale's page lists `log.tailscale.com` among the hosts that a client needs. It does not describe the content.

## How much is normal

With no traffic between your devices, Tailscale's traffic should be small. Expect short exchanges with the coordination servers.

Traffic between your devices is the data of the apps that use the tunnel. Its size is about the size of that data, with some overhead.

Connections to DERP relays are normal when a direct path is not possible. Relayed traffic is usually slower than a direct path.

## When it uses a lot, and why

- **Large transfers between devices.** Copying files or backups to another device on your tailnet sends them through the tunnel.
- **An exit node.** When you route all traffic through another device, everything that this Mac sends goes through Tailscale first.
- **Relayed paths.** If direct UDP is blocked by a network, heavy traffic goes through DERP relays over TCP 443.

## Is it safe to block?

Block with care

Blocking Tailscale's hosts stops sign-in and device discovery, and the tunnel may drop. Block it only if you do not use it.

What breaks if you block it

- The client cannot reach the coordination server, so it cannot update the list of your devices.
- Direct device traffic needs UDP, and blocking it forces relays or breaks connections.
- Blocking TCP 443 to DERP relays removes the fallback path.
- Remote access to this Mac over your tailnet stops.

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. To pause the tunnel, click the Tailscale icon in the menu bar and turn Tailscale off.
2. If you use an exit node, choose None in the same menu when you do not need it.
3. On a hotspot, large transfers between devices still use data. Schedule them for another network.

## See how much it uses

1. Open Activity Monitor and search for Tailscale. Open the Network tab to see the bytes that it sent and received.

## With Kilobat

1. In the Kilobat app list, search for `Tailscale`. Its row shows the live rate and what it moved today.
2. Ask the same question in Terminal.

   ```
   kilobat explain Tailscale
   ```

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

Tailscale's firewall article does not name the processes that a Mac shows. The process name in Activity Monitor depends on the variant. Tailscale does not document it in the pages used here.

Tailscale does not state in these pages how often the client contacts its servers, or what the logging traffic contains.

## Questions

**Why does Tailscale use UDP port 41641?**

Tailscale says that 41641 is the default source port for direct WireGuard traffic between devices. You can change it per platform.

**Which Tailscale variant does my Mac use?**

Tailscale describes three. The App Store variant uses a Network Extension. The standalone variant uses a system extension. The open source one uses `utun`.

## Sources

- [Tailscale Docs: What firewall ports should I open to use Tailscale?](https://tailscale.com/kb/1082/firewall-ports)
- [Tailscale Docs: Tailscale on macOS: Which variant is right for me?](https://tailscale.com/kb/1065/macos-variants)

Checked on 7 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.
