Skip to main content
Some security teams need to whitelist Dust’s outbound IP addresses in their firewall, for example to let Dust reach a remote MCP server or a Snowflake instance behind a network policy.

​
When Dust uses static IPs

Dust routes outbound traffic through static egress IPs in these cases:
  • Remote MCP servers hosted on a domain verified for your workspace (Admin > Organization > Security > Domains & SSO > Verified domains). The MCP server hostname must belong to the verified domain itself, for example mcp.acme.com under a verified acme.com. A host on a different domain, including a vendor’s domain, is not covered. Without a verified domain, MCP traffic uses dynamic cloud IPs like everything else below.
  • Snowflake connections, unconditionally, regardless of domain verification.
  • BigQuery connections, the same way as Snowflake.
  • The official BigQuery MCP server (bigquery.googleapis.com), even without a verified domain.
All other outbound traffic, including other data warehouse connections, web search, browsing, and other tools and connections, uses dynamic cloud IPs that can change at any time. Do not whitelist those.

​
The IP addresses

Allow the IP that matches your workspace’s region, which you can tell from the address you use to open Dust. If you allow only the other region’s IP, Dust can’t connect.
These IPs are shared by all Dust workspaces. A firewall rule that allows them does not identify your workspace. Never rely on source IP alone to authenticate requests: keep authentication (bearer token or OAuth) enabled on your MCP server. IP whitelisting is a network-level restriction, not an identity guarantee.