Skip to navigation

Cloudflare dedicated egress IP

Use a Gateway egress policy to send Chainalysis traffic out your dedicated IPs

You can register a limited number of individual IP addresses rather than large ranges. Shared egress addresses used by many organizations, such as a security cloud’s default pool or a cloud provider’s ephemeral IPs, cannot be added to your allowlist.

Cloudflare Gateway normally sends traffic out from shared Cloudflare addresses. Dedicated egress IPs are static addresses assigned only to your account. An egress policy lets you send just Chainalysis traffic through them.

How it works

StageWhat happensWhere it’s configured
1. UserThe Cloudflare One Client (WARP) sends traffic to Gateway.Device enrollment and client mode.
2. Egress policyGateway matches requests for Chainalysis domains.Egress policy (step 4).
3. Dedicated egress IPMatching traffic leaves from your dedicated address.Dedicated egress IPs (step 1).
4. ChainalysisThe request arrives from your registered IP and is accepted.Chainalysis allowlist.

Before you begin

To follow this guide, you’ll need:

  • A Zero Trust Enterprise plan with the dedicated egress IP add-on.
  • Admin access to the Cloudflare dashboard.
  • The Cloudflare One Client on user devices in Traffic and DNS mode.
  • Your Chainalysis CSM contact in order to register your IPs.

Chainalysis domains to route

Wherever your platform lets you target destinations, use these domains.

DomainWhat it’s used forNotes
*.chainalysis.comAll Chainalysis products, sign-in, and APIs.We recommend routing through this domain. It covers sign-in and every Chainalysis product, including any you add later.
kyt.chainalysis.comThe KYT user interface.This domain is the minimum required to access KYT. If you use this, you must also route api.chainalysis.com.
api.chainalysis.comThe KYT API and other Chainalysis APIs.This domain is the minimum required to access KYT. If you use this, you must also route kyt.chainalysis.com.

Caution: Ensure that you route by domain, not by IP address. Chainalysis IP addresses change, so rules built on them will break.

Configuration steps

1

Get dedicated egress IPs

Ask your Cloudflare account team for dedicated egress IPs. Cloudflare provisions at least two, in two different cities. You will find them under Address space > Leased IPs. You can also bring your own IPs (BYOIP).

2

Let Gateway proxy traffic

Go to Zero Trust > Traffic policies > Traffic settings, turn on Allow Secure Web Gateway to proxy traffic and select TCP.

3

Turn on host selectors

In the same Traffic settings page, under Policy settings, turn on Allow egress policy host selectors. This lets an egress policy match on domain names instead of only IP addresses.

Host selectors need the Cloudflare One Client in Traffic and DNS mode and a recent client version.

4

Create an egress policy for Chainalysis

  1. Create a new egress policy, for example Chainalysis via dedicated IP.
  2. Match the Chainalysis domains listed in the Chainalysis domains to route section using the Domain or Host selector.
  3. Set the egress method to Use dedicated egress IPs (Cloudflare or BYOIP), choose your primary IPv4 address, and set a secondary IPv4 in a different location.
  4. Save the policy.

Note: Cloudflare recommends a fallback egress IP for every policy. For Chainalysis, set the fallback to another of your dedicated IPs, not the shared pool, so traffic never leaves from an unregistered address.

5

Register your IPs with Chainalysis

Send the following to your Chainalysis CSM or Chainalysis Support, using the IP submission template:

  • Your dedicated egress IP addresses: IPv4 addresses and, if your network uses IPv6, your IPv6 /64 range.
  • Your organization name and, if you have more than one, the Chainalysis account or organization each IP should apply to.
  • Any other fixed addresses that call Chainalysis outside this platform, such as servers or integrations that use the API.
  • All of your dedicated egress addresses, including the secondary and fallback: each IPv4 address and its IPv6 /64.

Your allowlist can contain up to 50 IP addresses. If your number of IPs exceeds 50, you can request an exception through your CSM or Chainalysis Support.

The following table details the types of IPs we support.

What we acceptNotes
Public IPv4 addressesIndividual addresses or small CIDR ranges. Every address in a range counts toward your limit of 50, so a /27 (32 addresses) fits but a /24 (256) does not. If your network needs more, your CSM can discuss an exception.
IPv6 rangesSend your network’s /64 range rather than single addresses. Each /64 counts as one entry. Ranges broader than /64 are subject to approval.
Fixed egress onlyThis includes corporate VPNs, proxies, office gateways, dedicated security-cloud IPs, and cloud NAT addresses.

At this time, we do not accept private addresses (10.x, 172.16-31.x, 192.168.x, 100.64.x), home internet connections, shared or commercial VPN services, shared security-cloud egress pools, or broad ISP ranges.

Your CSM will tell you when the allowlist is live. Do not switch traffic over until they have confirmed.

6

Confirm your connection

  1. On a device running the Cloudflare One Client, sign in to KYT.
  2. Check the Gateway activity logs for Chainalysis requests and confirm they matched your egress policy.
  3. Run a test API call from every system that uses the Chainalysis API.
  4. Repeat the sign-in test with a remote user who is off your corporate network.

When you confirm your connection, we recommend resetting your password (if your organization uses SSO, you can skip this). To reset your password, log out and go to app.chainalysis.com. Enter your email address, click Continue, select Reset password, and follow the on-screen instructions.

We also recommend rotating your API key by following the steps on this page.

If you have issues, please contact support@chainalysis.com.

Common issues

  • Likely cause: Your IPs are not on the Chainalysis allowlist yet, or a different IP was registered.
  • How to resolve: Check with your CSM that the exact egress IPs are registered and active.
  • Likely cause:
    • API calls come from servers that don’t route through this platform.
    • The API key doesn’t have the right permissions or the API key must be rotated, even though the IP is allowed.
  • How to resolve:
    • Route those servers through it, or register their fixed egress IPs as well (see the Cloud NAT guide).
    • Check the API key’s permissions in your Chainalysis account, or create a new key.
      • API keys created before November 2, 2026 no longer work. To replace one, follow the key rotation steps.
  • Likely cause: Your network is dual-stack and the browser or client is connecting over IPv6.
  • How to resolve: Send your IPv6 /64 range to your CSM or Chainalysis Support. As a quick test, disable IPv6 on the device and retry.
  • Likely cause: Host selectors are off, or the client is not in Traffic and DNS mode.
  • How to resolve: Turn on host selectors and check the client mode and version.
  • Likely cause: Each dedicated egress IP includes an IPv6 range and the device prefers IPv6.
  • How to resolve: Register the IPv6 /64 of each dedicated egress IP as well as the IPv4 address.
  • Likely cause: A Split Tunnels or DNS override rule bypasses Gateway.
  • How to resolve: Remove chainalysis.com from Split Tunnel exclusions and DNS overrides.

Additional support

We’re here to help. For questions, contact your Chainalysis CSM or Chainalysis Support.