Dedicated Zscaler IP
You can register a limited number of individual IP addresses rather than large ranges. If your organization reaches the internet through Zscaler, your traffic normally leaves from shared Zscaler addresses that many other Zscaler customers also use, so those addresses cannot be allowlisted.
A Zscaler dedicated IP solves this. It gives your organization a small, fixed set of egress addresses that only you use. With one Forwarding Control rule, you can send all Chainalysis traffic out through those addresses, and register just those addresses with us.
How it works
Before you begin
To follow this guide, you’ll need:
- An administrator account in the Zscaler Internet Access (ZIA) Admin Portal that can manage gateways and Forwarding Control policies.
- A dedicated IP allocation from Zscaler (see step 1 below).
- Your Chainalysis CSM contact in order to register your IPs.
Chainalysis domains to route
Caution: Ensure that you route by domain, not by IP address. Chainalysis IP addresses change, so rules built on them will break.
Configuration steps
Request a dedicated IP from Zscaler
Ask your Zscaler account team or Zscaler Support for a dedicated IP allocation. Licenses normally include five dedicated IP sets; confirm your exact entitlement with Zscaler.
Write down the addresses Zscaler assigns. You’ll use them in step 2 and send them to Chainalysis afterwards (see Register your IPs with Chainalysis).
Create a gateway for the dedicated IP
In the ZIA Admin Portal, create a new gateway (the default gateway type used by Forwarding Control).
- Give it a clear name, for example
Dedicated IP - Chainalysis. - Set the server location to the dedicated IP range Zscaler assigned in step 1.
- Save the gateway.
Create a Forwarding Control policy rule
Go to the Forwarding Control policy and add a new rule (for example, Chainalysis via dedicated IP). Place it above any broader rule that could match Chainalysis traffic first.
You can limit the rule to specific users or groups, for instance a SAML group from your identity provider. Note that this is optional; applying the rule to everyone is usually easier because every request to Chainalysis has to come from a registered IP anyway.
Match Chainalysis domains and forward to the dedicated IP
- In the rule criteria, add the Chainalysis domains listed in the Chainalysis domains to route section as destination FQDNs.
- In the rule action on the right-hand side, set the forwarding method to forward to a dedicated IP.
Select the gateway, save, and activate
- When prompted, choose the gateway you created in step 2 from the drop-down list.
- Save the rule.
- Activate your pending changes. ZIA changes don’t take effect until they are activated.
Note: Once the rule is active, all traffic from your Zscaler-connected users to Chainalysis leaves through your dedicated IP egress.
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
/64range. - Your organization name and the Chainalysis account or organization each IP applies to.
- Any other fixed addresses that call Chainalysis without going through Zscaler, such as servers or integrations that use the API.
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.
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.
Confirm your connection
- On a Zscaler-connected device, sign in to KYT.
- In your ZIA logs, filter on
chainalysis.comand check the requests matched your new Forwarding Control rule. - From each system that calls the Chainalysis API, run a test request and confirm it succeeds.
- 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
Receiving the following message: “Access Restricted. Your IP address is not on the Chainalysis Allowed IPs List.”
- Likely cause: Your IPs are not on the Chainalysis allowlist yet, or a different IP was registered.
- How to resolve: Check https://kyt.chainalysis.com/cdn-cgi/trace and confirm the address with your CSM or Chainalysis Support.
Works in the office but not for remote users.
- Likely cause: The device is not using Zscaler, or Chainalysis is on a bypass list.
- How to resolve: Make sure Client Connector is on, and remove
chainalysis.comfrom any bypass or PAC exclusions.
The web interface works, but API calls fail.
- Likely cause: API calls come from servers that do not route through Zscaler.
- How to resolve: Route those servers through Zscaler, or register their fixed egress IPs as well.
Some pages or sign-in fail.
- Likely cause: The rule only covers some Chainalysis hostnames.
- How to resolve: Use
*.chainalysis.comas the destination.
The rule has no effect.
- Likely cause: Changes weren’t activated, or a higher rule matches first.
- How to resolve: Activate pending changes and move the rule higher in the policy.
Blocked even though your IPv4 address is registered.
- Likely cause: Your network is dual-stack and the browser or client is connecting over IPv6.
- How to resolve: Send your IPv6
/64range to your CSM or Chainalysis Support. As a quick test, disable IPv6 on the device and retry.
Sign-in works but API calls return a 403 error.
- Likely cause: 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: 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.
Additional support
We’re here to help. For questions, contact your Chainalysis CSM or Chainalysis Support.