Maintaining Claude Code Domain Lists and Proxy Split Rules
Illustrative check sequence; verify against actual results.

Verify Core Claude Domains First

claude.ai, api.anthropic.com, platform.claude.com, and claude.com must route through a consistent exit so login, token exchange, and API calls do not split across countries.

Understand Optional Connector, Bridge, and Telemetry Hosts

bridge.claudeusercontent.com and mcp-proxy.anthropic.com support browser bridging and MCP connectors, while Datadog intake hosts handle optional telemetry.

Rule Snippets Are Building Blocks, Not a Complete Config

Place the generated Clash, Surge, or sing-box domain rules above generic GEOIP/match rules and ensure the outbound policy name matches your proxy group.

Keep Domain Rules Updated as Products Evolve

Check the official Claude Code network configuration documentation whenever new features or connectors are introduced.

Common Real-World Scenario

For example, if web chat works but Chrome extension bridging fails, check whether claudeusercontent.com is included in your proxy rule group.

Maintain a domain list that can be reviewed

Start with the current official Claude Code networking documentation. Record each domain's purpose, source URL, and review date. Separate authentication, API, updates, and optional features, and keep reference sites distinct from product endpoints. This tool's fixed probe list describes its browser measurements, not every service that may be added later.

Before importing rules, verify syntax, matching order, and policy names for the client version in use. Mihomo, Surge, and sing-box use different formats. A preceding direct or reject rule may take precedence over a later proxy rule. A domain merely appearing somewhere in a configuration does not establish which policy handled its request.

After an update, check the real Claude Code connection and existing client connection records for the destination and selected policy. Redact credentials in saved evidence. A failed browser trace is supplemental evidence, not a reason to remove a domain still required by official documentation. Retain the prior rule version so a regression can be isolated.

References & Freshness

The above is independent diagnostic guidance with no access to Anthropic internal risk controls. Policies, UIs, and support workflows may change—always verify against official effective dates and your account portal.