Source: https://swgbar.com/en/guides/confirmed-vs-suspected-https-inspection/
Language: en

# Confirmed vs. Suspected HTTPS inspection in SWG bar

Understand how SWG bar classifies domains as Confirmed, Suspected, Public trust path, Intranet, or Unknown—and how those counts drive Overview's interception ratio.

SWG bar · Updated November 18, 2026

When you open **SWG bar → Overview** or **Domains**, each probed hostname receives one of five status labels: **Confirmed**, **Suspected**, **Public trust path** (`Public`), **Intranet**, or **Unknown**. Together, **Confirmed** and **Suspected** determine the **Domain interception ratio** percentage at the top of Overview.

## How SWG bar compares macOS trust with public roots

For every probed hostname, SWG bar opens an independent outbound IPv4 TLS connection and evaluates the presented certificate chain against two trust baselines:

1.  **macOS System Trust**: Evaluates whether macOS trusts the chain—including any root CAs installed via enterprise mobile device management (MDM) or local user keychains.
2.  **Public CA validation (Mozilla Root Store / Apple public system roots)**: Checks whether the exact same certificate chain is accepted solely by public certificate authorities without extra locally added roots.

When **macOS System Trust** passes but **Public CA validation** fails, macOS is trusting the site through an extra local root anchor rather than a standard public CA.

## What each classification label means

| Status | Meaning | Why it appears |
| --- | --- | --- |
| **Confirmed** | High-confidence HTTPS interception. | Public CA validation failed and macOS trusted a locally added root CA that either matches a known/registered inspection rule or has signed certificates across **16 or more distinct domains**. |
| **Suspected** | Local root CA observed, below confirmation threshold. | Public CA validation failed and macOS trusted a locally added root CA seen across **1 to 15 distinct public domains** (for example, an SWG encountered early in browsing or a local lab/dev proxy CA). |
| **Public trust path** | Verified against public roots. | The probed connection presented a certificate chain trusted by public CAs, without relying on a local inspection root—though an SWG may still forward encrypted traffic or apply a [TLS inspection exception](<https://swgbar.com/en/guides/swg-bypass-vs-tls-exception/>). |
| **Intranet** | Internal network destination. | The target resolves to a private or reserved IP address range (such as RFC 1918) or an `.internal` hostname rather than a public internet domain. |
| **Unknown** | No conclusive trust result yet. | The domain has not finished probing, timed out, failed TLS verification in macOS, or could not be reached over IPv4. |

![SWG bar Domains view showing Confirmed, Public, and Suspected domain badges alongside certificate names; illustrative preview.](<https://swgbar.com/optimized/panel-native-domains-four-tabs-720.webp>)

_Illustrative Domains preview: domains classified as Confirmed or Suspected contribute to Overview’s Domain interception ratio._

## Why a domain moves from Suspected to Confirmed

When you first install SWG bar on a Mac behind a corporate gateway, an unfamiliar enterprise root CA can initially appear as **Suspected** while only a few hostnames have been probed. As you visit more HTTPS websites and SWG bar sees that same local root CA re-signing certificates across **16 or more distinct domains**, domains signed by that root cluster automatically upgrade to **Confirmed**, and the **Bypass SWG** action becomes available on those domain detail screens.

You can check the current distribution from Terminal anytime using the [CLI](<https://swgbar.com/en/cli/>):

```
swgbar overview
swgbar domains list --status confirmed --page 1 --page-size 20
swgbar domains list --status suspected --page 1 --page-size 20
```

## How to verify before acting

A **Confirmed** or **Suspected** badge is evidence about the probed TLS connection, not an automatic indication of unwanted tampering—company gateways and local debugging proxies legitimately use locally trusted CAs. Before enabling [per-domain SWG bypass](<https://swgbar.com/en/guides/how-to-bypass-swg/>), open the **Certificates** tab to [inspect the MITM root certificate details](<https://swgbar.com/en/guides/inspect-mitm-root-certificates-macos/>) and confirm the issuer matches your organization’s gateway or local proxy.

## 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/>)
*   [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/>)
