Source: https://swgbar.com/en/guides/multi-domain-sso-api-cdn-swg-bypass/
Language: en

# Bypass SWG for multi-domain web apps, SSO, CDNs & APIs on Mac

Why bypassing a single root domain is not enough for modern apps—discover login, CDN, and API hostnames in SWG bar and reset keep-alive connections cleanly.

SWG bar · Updated November 18, 2026

A common surprise when enabling **Bypass SWG** on macOS is seeing the main webpage reload while sign-in redirects, images, package downloads, or API calls still hit HTTPS inspection or fail. Because SWG bar applies bypass rules **per exact hostname**, multi-domain web apps and developer tools often depend on several separate hosts.

## Why single-hostname bypass does not cover subdomains

Enabling bypass on `app.example.com` routes **only** `app.example.com`. It does not automatically bypass:

*   **Single sign-on (SSO) & OAuth providers**: `login.example.com`, `auth.example.com`, `sso.company.com`, or third-party identity hosts (`accounts.google.com`, `login.microsoftonline.com`).
*   **API & AI endpoints**: `api.example.com`, `graphql.example.com`, or separate telemetry/streaming subdomains.
*   **Static assets & registries**: `cdn.example.net`, `assets.example.com`, or object storage buckets (`*.s3.amazonaws.com`, `objects.githubusercontent.com`).

Note that **unidentifiable or encrypted SNI/ECH hostnames** cannot be matched for per-domain bypass.

## Find every inspected hostname used by an app

1.  Open the website or run the failing developer workflow once while SWG bar is monitoring.
2.  In **SWG bar → Domains**, sort or filter by **Confirmed** / **Suspected** and search by keyword (for example `example` or `auth`), or query via the [CLI](<https://swgbar.com/en/cli/>):

```
swgbar domains list --status confirmed --search example
swgbar domains list --bypass active
```

3.  For each inspected hostname required by the workflow, open its details and enable **Bypass SWG** (or run `swgbar bypass enable <hostname>`).
4.  Remember that bypassing one authentication or API domain on an authorized network does not mean every unrelated domain needs bypass—keep rules scoped strictly to the specific hosts that require it.

## Close keep-alive connections and check Chrome status

Even after **Bypassing** appears, browsers and background daemons reuse existing HTTP/2, HTTP/3, or TLS keep-alive sockets over the old inspected path:

*   **Web browsers**: Reload the affected tab (`Cmd + Shift + R`), or close and reopen the browser window if the site uses long-lived WebSocket or HTTP/3 connections. Use the [Chrome companion extension](<https://swgbar.com/en/chrome-extension/>) to check the active hostname shown for the current tab—though remember the extension displays recorded SWG bar observations rather than inspecting Chrome’s live socket.
*   **Terminal & IDEs**: Restart long-running processes (`npm`, `Claude Code` daemon, IDE language servers, or `git` credential helpers) so they open fresh TCP/TLS connections over the physical interface.

## Verify each hostname separately

After updating rules, open **Domains** (or run `swgbar domains detail <hostname>`) and verify fresh probes confirm public trust for **each** hostname in the workflow—not just the top-level URL shown in the browser address bar. If an organization-wide SaaS or SSO domain affects everyone on the team, compare whether an administrator policy exception is better suited in [SWG bypass vs. TLS inspection exception](<https://swgbar.com/en/guides/swg-bypass-vs-tls-exception/>).

## 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/>)
*   [Zscaler SSL Inspection on Mac: How to Check & Bypass per Domain](<https://swgbar.com/en/guides/zscaler-ssl-inspection-bypass-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/>)
*   [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/>)
