Source: https://swgbar.com/en/guides/zscaler-ssl-inspection-bypass-mac/
Language: en

# Zscaler SSL Inspection on Mac: How to Check & Bypass per Domain

Check whether Zscaler Client Connector is decrypting HTTPS on your Mac, why killing ZCC fails under Tamper Protection, and how to bypass per domain or fix CLI CA trust.

SWG bar · Updated November 19, 2026

To check whether **Zscaler (ZIA / Zscaler Client Connector)** is decrypting HTTPS traffic on your Mac, open **SWG bar → Overview** (or run `swgbar overview`) and look for a **Domain interception ratio** above `0%` with a **Zscaler Root CA** or corporate intermediate CA listed under **MITM certificates**. To bypass Zscaler SSL inspection for a single broken hostname on an authorized Mac, open **SWG bar → Domains**, select the hostname, and enable **Bypass SWG** (or run `swgbar bypass enable <domain>`).

Most online guides for bypassing Zscaler assume you have login access to the **Zscaler Admin Portal** (ZIA). On a company MacBook managed via Jamf, Kandji, or Intune, developers and employees rarely have portal access—yet Zscaler’s **Z-Tunnel 2.0** (`NetworkExtension` / `utun` tunnel) and **Zscaler Root CA** routinely break certificate-pinned apps, `Homebrew`, `npm`, `git`, `Python`, `Docker`, `Claude Code`, and `Cursor`.

## 1\. Check if Zscaler is actively inspecting HTTPS on your Mac

Because MDM pre-installs and trusts the **Zscaler Root CA** in macOS Keychain, Safari and Chrome show a normal padlock even while Zscaler performs HTTPS break-and-inspect. Verify per-domain decryption using either method:

*   **Continuous check with SWG bar**: [Install SWG bar](<https://swgbar.com/en/install/>) (macOS 14+ Apple silicon, 14-use-day free trial) and visit the target sites. Open **SWG bar → Domains** or **Certificates**—or run `swgbar probe <domain>`—to see whether the domain is **Confirmed** intercepted by `Zscaler Root CA` (or your company’s Zscaler intermediate CA) vs. passing through with a **Public trust path**.
*   **Spot-check one domain in Terminal**:

```
openssl s_client -connect api.github.com:443 -servername api.github.com </dev/null 2>/dev/null | openssl x509 -noout -issuer -subject
```

If `issuer=` shows `Zscaler` or your organization’s custom Zscaler intermediate CA instead of a public CA (such as DigiCert, Let’s Encrypt, or Google Trust Services), Zscaler SSL inspection is active for that hostname. See [Verify TLS certificates with OpenSSL and security verify-cert](<https://swgbar.com/en/guides/verify-tls-certificates-openssl-security-verify-cert-macos/>) to cross-check SHA-256 fingerprints.

## 2\. Why logging out or unloading Zscaler Client Connector fails

Trying to disable Zscaler globally on a managed Mac almost always backfires:

*   **Tamper Protection**: Most corporate ZCC App Profiles require a one-time IT password to log out or disable Internet Security (`ZIA`), and `sudo launchctl bootout system /Library/LaunchDaemons/com.zscaler.*` is blocked or immediately respawned.
*   **Z-Tunnel 2.0 bypasses System Proxy settings**: Turning off Wi-Fi HTTP/HTTPS proxy toggles in macOS System Settings has no effect on Z-Tunnel 2.0 packet steering.
*   **Broken corporate access**: Even if ZCC stops, ZPA (Zscaler Private Access) internal apps and device-posture-gated SSO (`Okta`, `Entra ID`) stop working.

## 3\. Three practical ways to handle Zscaler SSL inspection on macOS

| Approach | Who controls it | Keeps ZCC & corporate SSO running? | Best use case |
| --- | --- | --- | --- |
| **Per-domain SWG bypass (`SWG bar`)** | Local Mac user (on authorized networks) | Yes — routes only the selected hostname over your Mac’s physical `Hardware` IPv4 interface | Immediate hostname-level relief for pinned apps, WebSockets, or broken developer APIs without disabling ZCC ([How to bypass SWG on a Mac](<https://swgbar.com/en/guides/how-to-bypass-swg/>)) |
| **Zscaler Admin Portal exclusion (`Do Not Inspect` / App Profile)** | Enterprise IT / Security team | Yes | Permanent organization-wide exemption under **Policy → SSL Inspection → Do Not Inspect** or macOS **App Profiles → Hostname/IP Bypass** ([SWG bypass vs. TLS exception](<https://swgbar.com/en/guides/swg-bypass-vs-tls-exception/>)) |
| **Export & trust Zscaler Root CA in CLI tools** | Local developer | Yes (traffic stays inspected) | Corporate policy requires decrypted routing and `git`, `npm`, `brew`, `Python`, `Claude Code`, or `Cursor` fail with `unable to get local issuer certificate` |

## 4\. Enable per-domain bypass or configure Zscaler Root CA for CLI tools

### Option A: Per-domain bypass with SWG bar (when authorized)

1.  Open **SWG bar → Domains**, find the exact failing hostname (note that login, API, and CDN domains are separate hostnames—see [multi-domain SSO, API, and CDN bypass](<https://swgbar.com/en/guides/multi-domain-sso-api-cdn-swg-bypass/>)), and click **Enable** next to **Bypass SWG**—or run `swgbar bypass enable <domain>`.
2.  Wait for **Bypassing**, then restart the browser tab, IDE, or CLI session so pooled connections reopen on the direct `Hardware` IPv4 route.
3.  Verify with `swgbar probe <domain>` that the origin server’s public certificate chain is now returned. If a firewall blocks direct outbound connections, run `swgbar bypass disable <domain>` to restore normal Zscaler routing immediately.

### Option B: Configure CLI & AI tools to trust Zscaler Root CA

If your network policy requires traffic to stay decrypted by Zscaler, export your Zscaler Root CA PEM bundle from Keychain Access (or request the PEM file from IT) and configure your runtimes instead of disabling SSL verification:

```
# Node.js, npm, Claude Code, Cursor
export NODE_EXTRA_CA_CERTS="$HOME/.certs/zscaler-root.pem"

# Python (pip, requests), OpenSSL, Homebrew curl
export SSL_CERT_FILE="$HOME/.certs/zscaler-root.pem"
export REQUESTS_CA_BUNDLE="$HOME/.certs/zscaler-root.pem"
export CURL_CA_BUNDLE="$HOME/.certs/zscaler-root.pem"

# Git
git config --global http.sslCAInfo "$HOME/.certs/zscaler-root.pem"
```

For full runtime instructions covering Homebrew, Docker Desktop, Python, Node.js, Claude Code, and Cursor, read [Configure CA trust for Homebrew, Docker, Python, and Node.js](<https://swgbar.com/en/guides/homebrew-docker-python-node-ca-trust-swg-macos/>) and [Fix Claude Code & Cursor certificate errors on macOS](<https://swgbar.com/en/guides/ai-coding-agents-claude-code-cursor-swg-macos/>).

## Keep reading

*   [How to Bypass SWG on a Mac (One-Click Domain Bypass & CLI)](<https://swgbar.com/en/guides/how-to-bypass-swg/>)
*   [How to Bypass SSL Inspection on a Mac (Corporate SWG & Per-Domain Fix)](<https://swgbar.com/en/guides/bypass-ssl-inspection-mac/>)
*   [How to Bypass HTTPS & TLS Inspection on macOS (Break-and-Inspect Guide)](<https://swgbar.com/en/guides/bypass-https-tls-inspection-mac/>)
*   [How to Bypass Corporate Proxy & SWG SSL Inspection on a Mac](<https://swgbar.com/en/guides/bypass-corporate-proxy-ssl-inspection-mac/>)
*   [How to tell if your Mac is intercepted by an SWG (HTTPS & SSL inspection)](<https://swgbar.com/en/guides/detect-https-inspection/>)
*   [How to Check if Your Employer or Work Mac Is Intercepting HTTPS (SSL Inspection)](<https://swgbar.com/en/guides/check-if-work-mac-intercepting-https/>)
*   [SSL Inspection Checker for Mac: Menu Bar Tool to Detect HTTPS Interception](<https://swgbar.com/en/guides/ssl-inspection-checker-mac/>)
*   [Netskope SSL Inspection on Mac: Check Decryption & Bypass per Domain](<https://swgbar.com/en/guides/netskope-ssl-inspection-bypass-mac/>)
*   [Cloudflare WARP & Zero Trust TLS Inspection on Mac: Detect & Bypass](<https://swgbar.com/en/guides/cloudflare-warp-tls-inspection-mac/>)
*   [Confirmed vs. Suspected HTTPS inspection in SWG bar](<https://swgbar.com/en/guides/confirmed-vs-suspected-https-inspection/>)
*   [Inspect MITM root certificates & issuers in SWG bar](<https://swgbar.com/en/guides/inspect-mitm-root-certificates-macos/>)
*   [Enterprise SWG & MDM HTTPS inspection on a Mac](<https://swgbar.com/en/guides/enterprise-swg-https-inspection-macos/>)
*   [SWG bypass vs. TLS inspection exception (break and inspect)](<https://swgbar.com/en/guides/swg-bypass-vs-tls-exception/>)
*   [Bypass SWG for multi-domain web apps, SSO, CDNs & APIs on Mac](<https://swgbar.com/en/guides/multi-domain-sso-api-cdn-swg-bypass/>)
*   [Fix SWG bypass Recovering, Paused & connection errors on Mac](<https://swgbar.com/en/guides/troubleshoot-swg-bypass-recovering-paused-macos/>)
*   [macOS VPN virtual interfaces vs. SWG HTTPS inspection](<https://swgbar.com/en/guides/macos-vpn-virtual-interface-vs-swg-inspection/>)
*   [Why certificate-pinned apps & mTLS break under SWG inspection](<https://swgbar.com/en/guides/certificate-pinning-mtls-swg-inspection-macos/>)
*   [Fix SWG TLS & SSL certificate errors in CLI and AI tools on a Mac](<https://swgbar.com/en/guides/swg-tls-certificate-errors-macos/>)
*   [Homebrew, Docker, Python & Node.js CA trust behind an SWG on Mac](<https://swgbar.com/en/guides/homebrew-docker-python-node-ca-trust-swg-macos/>)
*   [Fix Claude Code & Cursor 'unable to get local issuer certificate' on Mac (SWG & MCP)](<https://swgbar.com/en/guides/ai-coding-agents-claude-code-cursor-swg-macos/>)
*   [Verify TLS certificates with openssl & security verify-cert on Mac](<https://swgbar.com/en/guides/verify-tls-certificates-openssl-security-verify-cert-macos/>)
*   [SWG bar permissions, local privacy & TLS probe limits](<https://swgbar.com/en/guides/macos-network-extension-privacy-probe-limits/>)
*   [How SWG bar checks HTTPS inspection](<https://swgbar.com/en/how-it-works/>)
*   [Download & install SWG bar for Mac (macOS 14+)](<https://swgbar.com/en/install/>)
*   [Chrome Extension to Detect SSL & HTTPS Inspection (SWG Bar Companion)](<https://swgbar.com/en/chrome-extension/>)
*   [SWG bar CLI Guide](<https://swgbar.com/en/cli/>)
*   [SWG bar MCP Guide](<https://swgbar.com/en/mcp/>)
*   [SWG bar release information](<https://swgbar.com/en/releases/>)
*   [About SWG bar](<https://swgbar.com/en/about/>)
