---
title: "What is captiveagent on a Mac? Why it uses the network and whether to block it · Kilobat"
url: "https://kilobat.app/processes/captiveagent"
description: "captiveagent checks for captive Wi-Fi portals on macOS and can sign in to them. What it requests, and what breaks if you block it."
---

# What is captiveagent?

`captiveagent` is the macOS daemon that detects and processes captive networks. Its man page says it issues HTTP requests to see if a network has a captive web portal.

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

I want to know what captiveagent is doing on my Mac and whether its network use is normal. Read https://kilobat.app/processes/captiveagent.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: `captiveagent` · Made by Apple · Applies to: Checked on macOS 27.2. · Checked: 7 November 2026

## Short answer

Part of macOS. Its man page says it sends HTTP requests to find captive web portals and can log in to them over HTTPS.

Don’t block

Do not block it. Public Wi-Fi sign-in pages may not open and the network may look offline.

Path

`/usr/libexec/captiveagent`

launchd label

`com.apple.captiveagent`

Signing identifier

`com.apple.captiveagent`

## What it is

The program is `/usr/libexec/captiveagent`, signed by Apple. Its launchd label is `com.apple.captiveagent`. It is a system daemon that runs as the user `_captiveagent`.

The man page says it may also run HTTPS transactions to log in to and out of the portal.

Apple's host list names `captive.apple.com` on ports 443 and 80 under Device setup. See [`captive.apple.com`](https://kilobat.app/hosts/captive-apple-com).

Apple does not say that this host is the one `captiveagent` requests. The man page does not name a host.

A captive portal is a login page on public Wi-Fi, such as a hotel or airport. See [Wi-Fi login page does not appear on a Mac](https://kilobat.app/guides/captive-portal-not-appearing) if the page does not open.

## Why it uses the network

- **Portal checks.** On joining a network, the daemon requests a page over HTTP to see if a portal intercepts it.
- **Portal log-in and log-out.** The man page says it may use HTTPS to log in or out.
- **Rechecks.** Apple does not say how often it checks again.

## How much is normal

A few small requests each time you join a network are normal.

Apple gives no figure.

Constant requests are not described by Apple.

## When it uses a lot, and why

- **Moving between networks.** Each join starts a check.
- **A flaky network.** Repeated joins repeat checks.

## Is it safe to block?

Don’t block

Do not block it. Public Wi-Fi sign-in pages may not open and the network may look offline.

What breaks if you block it

- Captive portal pages do not appear on hotel and airport Wi-Fi.
- Wi-Fi may say it has no internet.
- Log-in and log-out with a portal fail.

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 portal page does not open, follow [Wi-Fi login page does not appear on a Mac](https://kilobat.app/guides/captive-portal-not-appearing).
2. Forget and rejoin the network in System Settings › Wi-Fi.
3. On a hotspot or a capped plan, turn on Low Data Mode. Choose Apple menu › System Settings › Wi-Fi. Click Details next to the network, then turn on Low Data Mode.
4. Do not quit `captiveagent` in Activity Monitor. macOS starts it again.

## See how much it uses

1. Open Activity Monitor from Applications › Utilities. Click Network.
2. Type `captiveagent` in the search field. The Sent Bytes and Rcvd Bytes columns show what it moved since it started.
3. In Terminal, watch only this process. Press d to show the change per second, and q to quit.

   ```
   nettop -p 'captiveagent' -P
   ```

## With Kilobat

1. In the Kilobat app list, search for `captiveagent`. Its row shows the live rate and what it moved today.
2. In Connections, click the ⓘ button on one of its rows. The popover shows this page’s short answer, without going online.
3. In Terminal, ask the same question. Add `--json` for scripts and agents.

   ```
   kilobat explain 'captiveagent'
   ```
4. Show its traffic over one day.

   ```
   kilobat bandwidth 'captiveagent' day
   ```
5. Through MCP, an AI agent asks `explain_connection` with the process name. It gets the same facts.

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).

## Hosts it contacts

Apple and the maker document these hosts for this feature. A process can also contact others; Kilobat’s Connections tab shows what it actually opens on your Mac.

- [captive.apple.com](https://kilobat.app/hosts/captive-apple-com): Apple's internet connectivity check for networks with sign-in pages (captive portals). Kilobat uses it too.

## What isn’t documented

Apple does not say which host `captiveagent` contacts on a given network.

Apple does not say how often it rechecks.

Apple does not say whether it handles every kind of portal.

## Questions

**Why does captiveagent make HTTP requests?**

Its man page says it checks whether the network has a captive web portal.

**Is captive.apple.com safe?**

Apple lists it in its host list for Device setup.

**Is captiveagent a virus?**

No. It is signed by Apple and has a man page.

## Sources

- captiveagent(8), man page installed with macOS 27.2
- launchd property list com.apple.captiveagent, macOS 27.2
- [Apple Support: Use Apple products on enterprise networks](https://support.apple.com/en-us/101555)

Checked on 7 November 2026.

## Related

- [configd](https://kilobat.app/processes/configd): Part of macOS. It keeps the Mac's network configuration and gets its IP addresses with DHCP, so it sends small amounts of traffic to the router.
- [airportd](https://kilobat.app/processes/airportd): Part of macOS. airportd manages the Wi-Fi interface, and WiFiAgent does Wi-Fi tasks for it in your session. They run Wi-Fi itself, not internet traffic.
- [networkserviceproxy](https://kilobat.app/processes/networkserviceproxy): Part of macOS. It is the transparent proxy for Apple system services and can carry iCloud Private Relay traffic, so other apps' browsing can show under it.
- [Wi-Fi login page does not appear on a Mac](https://kilobat.app/guides/captive-portal-not-appearing)
- [Hotel Wi-Fi on a Mac: sign-ins, device limits and lag](https://kilobat.app/guides/hotel-wifi-mac)
