How to Bypass Corporate Proxy & SWG SSL Inspection on a Mac

Why turning off macOS System Settings Proxies or running networksetup fails against transparent SWG proxies, and how to bypass per domain or fix CLI certificate errors.

SWG bar · Updated

If turning off Wi-Fi proxy toggles in System Settings → Network → Proxies—or adding domains via networksetup -setproxybypassdomains—still leaves your Mac behind corporate proxy SSL inspection, your device is using a transparent Secure Web Gateway (SWG) agent (NetworkExtension or utun tunnel) rather than a plain explicit HTTP proxy. To bypass SWG inspection for a specific hostname on an authorized Mac, open SWG bar → Domains, select the hostname, and enable Bypass SWG (or run swgbar bypass enable <domain>).

Most macOS proxy tutorials blur two completely different corporate architectures together: legacy explicit proxies / PAC files and modern transparent SWG agents (such as Cisco Umbrella / Cisco Secure Client, Broadcom Cloud SWG, Zscaler, Netskope, or Cloudflare Gateway). Knowing which one your Mac uses immediately explains why standard proxy tweaks do nothing—and which fix actually works.

1. Check whether your Mac uses an explicit proxy or a transparent SWG

Run two quick checks to see how traffic is being steered on macOS:

  1. Inspect explicit system proxy settings:
scutil --proxy

Look for HTTPEnable : 1, HTTPSEnable : 1, or ProxyAutoConfigURLString (a .pac URL). 2. Inspect actual HTTPS certificate interception: Open SWG bar → Overview (or run swgbar overview / swgbar domains list --status confirmed).

  • If scutil --proxy is empty, yet SWG bar reports a Domain interception ratio > 0% (with Confirmed or Suspected domains and MITM certificates), your Mac is behind a transparent SWG agent (NetworkExtension / utun) that captures packets below macOS System Proxy settings.
  • If scutil --proxy lists a corporate proxy/PAC and SWG bar shows a corporate MITM root CA, traffic is routed through an explicit/PAC intercepting proxy.

2. Explicit proxy vs. transparent SWG proxy on macOS

Architecture Where macOS intercepts traffic Does System Settings → Proxies / networksetup bypass it? What works on an authorized Mac
Explicit HTTP/HTTPS or PAC proxy (unmanaged) macOS System Configuration proxy fields Yes, if not locked by MDM (Bypass proxy settings for these hosts & domains) macOS Proxy Bypass list, or per-domain routing verification
MDM-locked explicit proxy or transparent SWG (NetworkExtension / utun) Kernel / NetworkExtension socket & IP filter below browser proxy toggles No — settings are locked, overwritten, or completely ignored by the SWG tunnel Per-domain physical Hardware IPv4 bypass via SWG bar (How to bypass SWG on a Mac), IT gateway External Domains / Do Not Decrypt exclusions, or CLI CA bundle config

3. Bypass SWG proxy SSL inspection for a specific domain on macOS

When a specific web app, API endpoint, or certificate-pinned desktop client fails behind a corporate SWG proxy on a network you administer or are authorized to configure:

  1. Install and open SWG bar (macOS 14+ on Apple silicon, 14-use-day free trial) and reproduce the request so the exact hostname appears in Domains.
  2. Open the hostname’s details and click Enable in the Bypass SWG row—or run:
swgbar bypass enable <domain>
swgbar bypass status
  1. Wait for Bypassing, then reload the webpage or restart the terminal/desktop client so existing keep-alive sockets reopen over your Mac’s physical Hardware IPv4 interface (en0 / en7).
  2. Verify with swgbar probe <domain> that the origin’s public certificate chain is presented cleanly. Note that if an application hardcodes its own explicit proxy setting (for example HTTP_PROXY / HTTPS_PROXY in ~/.zshrc, ~/.npmrc, or ~/.gitconfig), unset those proxy variables for that host so the app does not force traffic back to the explicit proxy port.

4. When you cannot bypass the proxy: IT exclusions & CLI CA bundles

If your corporate firewall blocks all direct outbound IPv4 traffic that does not transit the SWG proxy (a fail-closed perimeter):

  • Disable per-domain bypass (swgbar bypass disable <domain>) so the hostname immediately returns to normal proxy routing.
  • Configure CLI tools to trust the corporate proxy CA: Point git, curl, npm, Python, Homebrew, Claude Code, and Cursor to your exported corporate CA PEM file (SSL_CERT_FILE, NODE_EXTRA_CA_CERTS, REQUESTS_CA_BUNDLE, git http.sslCAInfo) instead of insecurely turning off SSL verification. See Fix SWG TLS & SSL certificate errors in CLI and AI tools.
  • Request an IT gateway bypass / decryption exception: Provide IT with the exact failing hostnames (including login and CDN domains) and certificate evidence from SWG bar so they can add a central Do Not Decrypt or External Domains List rule. Compare both layers in SWG bypass vs. TLS inspection exception.