Supported formats

# Local development
localhost
127.0.0.1

# Enterprise domains
*.company.example  # Includes the root domain

# Private networks
10.0.0.0/8
[::1]/128

Use one rule per line. ProxyFox supports domains, wildcard domains, IPv4, CIDR, IPv6, and full-line or inline comments beginning with #.

What a wildcard means

*.example.com is normalized to a Chrome-compatible bypass rule and also covers example.com. Do not include a path, query string, or protocol: the bypass list matches hosts, not URL routes.

Global and per-profile scope

Use the global list for targets that should bypass every applicable proxy, such as local development and internal services. Per-profile rules belong to one proxy. When “Use global whitelist” is enabled, the two lists are merged.

Maintenance practices

  • Use comments to explain the business reason for a rule.
  • Prefer the narrowest necessary scope.
  • Test at least one profile after changing global rules.
  • If a site unexpectedly connects directly, search both rule lists.
  • Keep credential-free exports for review and backup.

Not automatic proxy selection

A ProxyFox bypass rule decides which hosts avoid the active proxy. It does not select different proxy profiles by website. Use a PAC- or rule-routing tool when automatic selection is the requirement.