Cloudflare WARP & Zero Trust TLS Inspection on Mac: Detect & Bypass

Tell whether Cloudflare WARP Zero Trust (or Palo Alto GlobalProtect) is decrypting HTTPS on macOS, and compare per-domain SWG bypass, Do Not Inspect rules, and CA bundles.

SWG bar · Updated

To check whether Cloudflare WARP (Cloudflare Zero Trust Gateway) is actively decrypting HTTPS traffic on your Mac—or only tunneling encrypted packets—open SWG bar → Overview (or run swgbar overview) and check whether the Domain interception ratio is above 0% with a Cloudflare Gateway or corporate root CA under MITM certificates. When a specific domain breaks under TLS decryption on an authorized Mac, open SWG bar → Domains and click Enable next to Bypass SWG (or run swgbar bypass enable <domain>).

Enterprise Macs running Cloudflare WARP (or Palo Alto GlobalProtect with SSL Forward Proxy) route connections through a macOS utun virtual interface. Just seeing a utun tunnel does not automatically mean HTTPS is being decrypted: a gateway may forward encrypted TLS untouched for some domains while applying break-and-inspect TLS decryption to others.

1. Distinguish WARP tunneling from active TLS decryption

Because Cloudflare Zero Trust lets IT combine Split Tunnels with per-policy TLS Decryption (Inspect vs. Do Not Inspect), two websites on the exact same Mac can behave completely differently:

  1. Install SWG bar (macOS 14+ Apple silicon, 14-use-day free trial) and visit the affected website or run the failing command.
  2. Open SWG bar → Domains (or run swgbar domains detail <domain>) and compare two separate signals:
    • Egress interface (Virtual vs. Hardware): Shows whether traffic left over a utun tunnel (such as WARP or GlobalProtect) or a physical interface (en0 / en7). See macOS VPN virtual interfaces vs. SWG inspection.
    • Certificate trust verdict (Confirmed / Suspected vs. Public trust path): Confirms whether Cloudflare Gateway Root CA (or a Palo Alto / corporate SSL Forward Proxy CA) actually terminated and re-signed the TLS certificate.
  3. To double-check a single endpoint from Terminal, run:
openssl s_client -connect github.com:443 -servername github.com </dev/null 2>/dev/null | openssl x509 -noout -issuer -subject

If issuer= lists Gateway CA / Cloudflare (as an intercepting corporate CA) or your organization’s Palo Alto CA instead of the site’s expected public issuer, TLS decryption is active for that domain.

2. Compare your 3 options on a managed Mac

On MDM-locked Macs, toggling WARP Off in the menu bar—or unloading GlobalProtect LaunchAgents—is commonly disabled or breaks access to private corporate services. Choose the option that fits your authorization and network policy:

Approach Stops TLS decryption? Requires Zero Trust / Firewall Admin? Best when
Per-domain SWG bypass (SWG bar) Yes, for chosen hostnames over physical Hardware IPv4 No (local hostname control on authorized Mac) Specific APIs, certificate-pinned apps, or WebSockets break under WARP/GlobalProtect decryption and direct IPv4 reachability is allowed (How to bypass SWG on a Mac)
Gateway Do Not Inspect or Split Tunnel Exclude Yes (policy-controlled) Yes (Cloudflare Zero Trust Gateway → Firewall policies → HTTP → Do Not Inspect or Split Tunnels → Exclude; Palo Alto Objects → Decryption Exclusions) Shared engineering tools, pinned macOS apps, or internal endpoints fail across the team (SWG bypass vs. TLS exception)
Trust the Cloudflare / Corporate Root CA in CLI runtimes No (traffic remains inspected) No Policy requires inspected WARP/GlobalProtect routing and Node.js, Python, Homebrew, Docker, Claude Code, or Cursor reject the custom CA

3. Bypass a broken domain or configure CLI CA trust

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

  1. Open SWG bar → Domains, locate every inspected hostname used by your app (auth, API, and CDN hosts are separate rules), and click Enable beside Bypass SWG—or run swgbar bypass enable <domain>.
  2. Wait for Bypassing, then reload the site or restart the CLI/IDE so existing pooled sockets reconnect over your Mac’s physical Hardware IPv4 interface.
  3. Run swgbar probe <domain> to verify the origin server’s public certificate chain is returned. If your corporate firewall blocks direct outbound connections, disable the rule (swgbar bypass disable <domain>) to return to normal WARP or GlobalProtect routing.

Option B: Point CLI tools to the Cloudflare Gateway Root CA

If your organization requires TLS decryption to stay enabled, place the Cloudflare Gateway root certificate PEM (exported from Keychain Access or supplied by IT) in ~/.certs/cloudflare-gateway-ca.pem and add to ~/.zshrc:

export NODE_EXTRA_CA_CERTS="$HOME/.certs/cloudflare-gateway-ca.pem"
export SSL_CERT_FILE="$HOME/.certs/cloudflare-gateway-ca.pem"
export REQUESTS_CA_BUNDLE="$HOME/.certs/cloudflare-gateway-ca.pem"
export CURL_CA_BUNDLE="$HOME/.certs/cloudflare-gateway-ca.pem"

For full Homebrew, Docker Desktop, Python, Node.js, and AI coding client setups, read Configure CA trust for Homebrew, Docker, Python, and Node.js and Fix Claude Code & Cursor certificate errors on macOS.