---
title: "Jamf on a Mac: which ports it uses, how it checks in, and whether to block it · Kilobat"
url: "https://kilobat.app/processes/jamf"
description: "The Jamf agent on a managed Mac connects to the Jamf Pro server on 8443 or 443 and listens for Apple push on 5223 or 443. Ports and what breaks."
---

# What is Jamf?

Jamf Pro is device management software. If your organisation uses it, your Mac runs the jamf agent. Jamf documents the ports that managed Macs use.

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

I want to know what Jamf is doing on my Mac and whether its network use is normal. Read https://kilobat.app/processes/jamf.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: `Jamf` · Also seen as: `jamf`, `JamfDaemon`, `Jamf Pro`, `Jamf Self Service` · Made by Jamf · Applies to: Jamf Pro-managed Macs on macOS 14 Sonoma and later. Checked on 8 November 2026 against the Jamf Learning Hub. · Checked: 8 November 2026

## Short answer

The Jamf management agent on a managed Mac. It checks in with the Jamf Pro server over HTTPS and receives MDM pushes through Apple on 5223 or 443.

Don’t block

Your organisation manages this agent. Blocking it can stop policies, software installs and remote management from reaching the Mac.

Path

`/usr/local/jamf/bin/jamf`

## What it is

Jamf's article "Network Ports Used by Jamf Pro" lists the connections from managed Mac computers. It says that all port numbers are TCP unless it says UDP.

Managed Macs connect to the Jamf Pro server over HTTPS on 8443 or 443. Jamf says that on-premise servers use 8443 by default and Jamf Cloud servers use 443.

Macs connect when they enrol, run the jamf agent, run Self Service for macOS, or respond to an MDM push notification.

Macs keep a persistent connection to Apple Push Notification service. Jamf says that devices use port 5223 by default and fail over to 443 on Wi-Fi.

Jamf says to allow outbound connections to Apple's 17.0.0.0/8 block on TCP 5223 or 443 from all client networks.

Jamf says that HTTPS interception, also called SSL inspection, is not supported for connections to Jamf Pro. A proxy must disable it for those connections.

Jamf lists several package sources. A cloud distribution point uses 443. An HTTP or HTTPS server uses 80 or 443. AFP uses 548, and SMB uses 445 and 137 to 139.

Jamf's component article says that `/usr/local/jamf/bin/jamf` is the binary for most tasks. JamfDaemon.app contains the jamf launch daemon.

## Why it uses the network

- **Check-in and policies.** The agent connects to the Jamf Pro server to run policies and report inventory.
- **MDM commands.** Jamf Pro tells Apple's push service to wake the Mac. The Mac then connects to the server.
- **Package downloads.** Policies can install software from the distribution points that your administrator sets up.
- **Self Service.** Self Service for macOS connects to the Jamf Pro server.

## How much is normal

Jamf does not publish figures for idle traffic. A persistent connection to Apple's push service is normal.

Check-ins are short exchanges with your server.

Larger traffic appears when a policy installs or updates software.

## When it uses a lot, and why

- **Software installs.** A policy that installs a large package downloads it from a distribution point.
- **Inventory and policy runs.** A scheduled check-in sends inventory data and runs policies.
- **First enrolment.** A new Mac enrols and downloads its configuration.

## Is it safe to block?

Don’t block

Your organisation manages this agent. Blocking it can stop policies, software installs and remote management from reaching the Mac.

What breaks if you block it

- The Mac cannot check in with the Jamf Pro server.
- MDM pushes through Apple's service stop arriving.
- Policies and Self Service software installs 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. Do not change this agent yourself. Ask your administrator when its traffic is a problem.
2. Administrators can schedule large package installs for off hours in Jamf Pro.
3. If a proxy inspects HTTPS, ask the network team to exempt connections to Jamf Pro.

## See how much it uses

1. Open Activity Monitor and search for jamf. Open the Network tab to see which Jamf processes moved data.

## With Kilobat

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

   ```
   kilobat explain jamf
   ```

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

Jamf's port article does not give check-in schedules, which your administrator sets. It does not give data volumes.

It does not name the process that holds the APNs connection on a Mac.

Your server's host name is set by your organisation. Jamf's page cannot name it.

## Questions

**Which ports does a Jamf-managed Mac use?**

Jamf lists 8443 or 443 for the Jamf Pro server, and 5223 or 443 for Apple's push service. Distribution points can use other ports.

**Can a proxy inspect HTTPS to Jamf Pro?**

Jamf says that HTTPS interception is not supported for connections to Jamf Pro.

## Sources

- [Jamf Learning Hub: Network Ports Used by Jamf Pro](https://learn.jamf.com/r/en-US/technical-articles/Network_Ports_Used_by_Jamf_Pro)
- [Jamf Learning Hub: Components Installed on Managed Computers](https://learn.jamf.com/r/en-US/jamf-pro-documentation-current/Components_Installed_on_Managed_Computers)

Checked on 8 November 2026.

## Related

- [mdmclient](https://kilobat.app/processes/mdmclient): Part of macOS. Its man page says it talks to a Mobile Device Management server. It works for an organisation that manages the Mac.
- [apsd](https://kilobat.app/processes/apsd): Part of macOS. It keeps one connection open to Apple's push notification service, so apps and iCloud can tell the Mac that something changed.
