---
title: "Bitwarden: which servers the Mac app talks to, which ports it needs, and whether to block it · Kilobat"
url: "https://kilobat.app/processes/bitwarden"
description: "The Bitwarden desktop app syncs an encrypted vault with Bitwarden's cloud or your own server over HTTPS and WebSockets. The addresses it lists, and what breaks."
---

# What is Bitwarden?

Bitwarden is a password manager. The desktop app keeps an encrypted vault on your Mac and syncs it with a server. Bitwarden documents the addresses and network rules.

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

I want to know what Bitwarden is doing on my Mac and whether its network use is normal. Read https://kilobat.app/processes/bitwarden.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: `Bitwarden` · Made by Bitwarden · Applies to: The Bitwarden desktop app on macOS 14 Sonoma and later. Checked on 8 November 2026 against Bitwarden's help centre. · Checked: 8 November 2026

## Short answer

The Bitwarden password manager app. It syncs your encrypted vault with Bitwarden's cloud or your own server over HTTPS, and needs WebSocket connections.

Block with care

Blocking Bitwarden's servers stops the app from syncing your vault. Block them only on a network where you do not use Bitwarden.

Path

`~/Library/Application Support/Bitwarden` `~/Library/Containers/com.bitwarden.desktop/Data/Library/Application Support/Bitwarden`

Signing identifier

`com.bitwarden.desktop`

## What it is

Bitwarden publishes a page of official addresses called "Bitwarden Domains, Endpoints, & URLs". It says that the addresses use content delivery networks, so the IP addresses may change.

The application endpoints on that page include `api.bitwarden.com`, `identity.bitwarden.com`, `events.bitwarden.com`, `push.bitwarden.com`, `notifications.bitwarden.com` and `icons.bitwarden.net`. The EU cloud uses the `.eu` versions of most of them.

The web vault is at `vault.bitwarden.com` or `vault.bitwarden.eu`.

Bitwarden's networking article says that the clients need WebSocket (`wss://`) connectivity to the server. It says that Bitwarden does not support environments where WebSocket connections are blocked.

The same article says that Bitwarden does not support environments that restrict or whitelist HTTP verbs.

A self-hosted server needs two open ports. One is for HTTP, by default `80`. The other is for HTTPS, by default `443`.

Bitwarden says that its servers store only encrypted data. The desktop app decrypts data in memory only after you unlock the vault.

On a Mac, Bitwarden's data storage article gives the vault location `~/Library/Application Support/Bitwarden`. For the Mac App Store version, it gives a path inside `~/Library/Containers/com.bitwarden.desktop`.

## Why it uses the network

- **Vault sync.** Bitwarden says that changes you make push to the server at once. Apps sync on login and regularly while unlocked. You can also use **File › Sync vault** in the menu bar.
- **Sign-in.** Bitwarden lists `identity.bitwarden.com` as an application endpoint. Its page does not say which endpoint handles which request.
- **Notifications from the server.** Bitwarden lists `push.bitwarden.com` and `notifications.bitwarden.com` as endpoints. Its networking article says that WebSocket connections are required.
- **Website icons.** Bitwarden lists `icons.bitwarden.net` as an endpoint. Its address page does not say what each endpoint carries.

## How much is normal

Bitwarden does not publish figures for idle traffic. A vault is a set of encrypted items, so you should expect small transfers.

Bitwarden says that items owned by an organisation sync across users and apps every 30 minutes. Your own items sync on login and regularly while the vault is unlocked.

With a self-hosted server, the app talks to that server instead of Bitwarden's cloud. The address you enter must include `https://`.

## When it uses a lot, and why

- **Attachments.** Attached files add to the data that a sync moves. Bitwarden does not give sizes.
- **A blocked WebSocket.** Bitwarden says that WebSocket connections are required. It does not say what happens in the app when a proxy blocks them.
- **A TLS-inspecting proxy.** Bitwarden warns that man-in-the-middle proxies can be dangerous. It says that logging full Bitwarden traffic should be off on such a connection.

## Is it safe to block?

Block with care

Blocking Bitwarden's servers stops the app from syncing your vault. Block them only on a network where you do not use Bitwarden.

What breaks if you block it

- Sync stops, and Bitwarden lists the identity and API endpoints that the apps need.
- Changes do not sync to your other devices or to the web vault.
- Blocked WebSocket connections break a setup that Bitwarden says it does not support.
- On a company network, blocking the API stops the whole team's vaults from updating.

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. On a restricted network, allow the addresses on Bitwarden's address page, not just `bitwarden.com`.
2. Do not block WebSocket connections or restrict HTTP verbs. Bitwarden does not support either.
3. If a security product flags Bitwarden, check it for false positives. Bitwarden says not to disable such products unless its support advises it.
4. Open **Bitwarden › Settings** to set the session timeout and timeout action.

## See how much it uses

1. Open Activity Monitor and search for Bitwarden. 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 `Bitwarden`. Its helper processes group under the app.
2. Ask the same question in Terminal.

   ```
   kilobat explain Bitwarden
   ```

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

Bitwarden's pages do not name the macOS process names or the install path for the desktop app.

Bitwarden does not say which endpoint serves each request. It does not give figures for idle traffic.

## Questions

**Which addresses does Bitwarden use?**

Bitwarden lists `api.bitwarden.com`, `identity.bitwarden.com`, `events.bitwarden.com`, `push.bitwarden.com` and others. The full list is on its address page.

**Does Bitwarden work with WebSockets blocked?**

No. Bitwarden says that it does not support environments where WebSocket connections are blocked.

**Where does the Mac app keep its data?**

Bitwarden gives `~/Library/Application Support/Bitwarden` for a standard install. Vault data stays encrypted there.

## Sources

- [Bitwarden Help: Bitwarden Domains, Endpoints, & URLs](https://bitwarden.com/help/bitwarden-addresses/)
- [Bitwarden Help: Networking Requirements](https://bitwarden.com/help/networking-requirements/)
- [Bitwarden Help: Data Storage](https://bitwarden.com/help/data-storage/)
- [Bitwarden Help: Sync your Vault](https://bitwarden.com/help/vault-sync/)

Checked on 8 November 2026.

## Related

- [1Password](https://kilobat.app/processes/1password): The 1Password desktop app. 1Password lists port 443 and the domains it uses for the core service, user content, updates, icons and Watchtower.
