Skip to navigation

Cisco Umbrella Reserved IP

Send Chainalysis traffic through the Secure Web Gateway to your Reserved IPs

Cisco Umbrella normally sends web traffic out from shared Umbrella address ranges, which other Umbrella customers also use. The Reserved IP add-on gives your organization single-tenant egress addresses for web traffic through the Secure Web Gateway, so you can register just those addresses with Chainalysis.

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.

How it works

StageWhat happensWhere it’s configured
1. UserThe Umbrella roaming module or a tunnel sends web traffic to Umbrella.Roaming module, IPsec tunnel, or PAC file.
2. Secure Web GatewayUmbrella proxies HTTP and HTTPS traffic to Chainalysis.Umbrella web policy.
3. Reserved IPTraffic leaves the Umbrella data center from your reserved address.Provisioned by Cisco (Step 1 below).
4. ChainalysisThe request arrives from your registered IP and is accepted.Chainalysis allowlist.

Before you begin

To follow this guide, you’ll need:

  • An Umbrella SIG package that includes the Secure Web Gateway.
  • The Reserved IP add-on, bought through your Cisco representative for the regions your users work in.
  • Admin access to the Umbrella dashboard.
  • 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

Buy and provision Reserved IP

Ask your Cisco representative for the Reserved IP add-on. It’s purchased by region, and each data center in a region gets one reserved address. Cisco provisions the addresses; there is no setting for you to configure.

Choose only the regions your users use Chainalysis from. Every region adds addresses you will need to register with Chainalysis.

2

Send web traffic through the Secure Web Gateway

Reserved IPs only apply to HTTP and HTTPS traffic proxied by the Secure Web Gateway. DNS-only protection is not sufficient.

  • Deploy the Umbrella roaming module (Cisco Secure Client) with the SWG module turned on, or send traffic through an Umbrella IPsec tunnel or PAC file.
  • Make sure chainalysis.com is not on any web policy bypass or external domain list, otherwise the traffic leaves from your local network instead.
3

Allow Chainalysis in your web policy

Check that your Umbrella web policy allows the Chainalysis domains and does not block them by category. HTTPS inspection is not required for this to work.

4

Record your reserved IPs

Get the list of reserved addresses from Cisco, one for each data center in the regions you purchased.

Note: Reserved IP is tied to the data center handling the traffic, not to individual destinations. All SWG web traffic from that data center uses it, not just Chainalysis traffic.

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.
  • Every reserved IP in every region your users connect through, since Umbrella can serve traffic from any data center in that region.

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 with the roaming module on, sign in to KYT.
  2. In the Umbrella dashboard, go to Reports > Core Reports > Activity Search. From here, open a Chainalysis request and confirm if Umbrella Egress IP Address is one of your reserved IPs.
  3. Run a test API call from every system that uses the KYT API.
  4. Repeat the sign-in test with a remote user who is not on 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: Traffic is going through a data center without a reserved IP, or bypassing the SWG.
  • How to resolve: Check the egress data center in Activity Search, and remove any SWG bypass for Chainalysis.
  • Likely cause: That region has no Reserved IP, or its IPs weren’t registered.
  • How to resolve: Add the region to your Reserved IP order, or register its addresses with your CSM.

Additional support

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