Skip to navigation

Corporate network

Send Chainalysis traffic from your VPN, proxy, or office firewall through fixed IPs

This guide is for organizations that don’t use one of the security clouds covered by our other guides. It applies to corporate VPNs (for example, Fortinet, Cisco Secure Client, GlobalProtect on-premises, OpenVPN and WireGuard), on-premises web proxies, and office firewalls.

Following these steps ensures that Chainalysis traffic leaves your network from a small set of fixed public IP addresses.

How it works

StageWhat happensWhere it’s configured
1. User or systemA device in the office or on the VPN opens a Chainalysis site or calls the API.Device, VPN client, or proxy settings.
2. Corporate networkTraffic to Chainalysis is routed through your VPN, proxy, or office gateway.VPN tunnel policy, Proxy Auto-Configuration (PAC) file or firewall rules.
3. Fixed egress IPThe firewall translates traffic to one of your static public IPs.Firewall NAT or proxy outbound address.
4. ChainalysisThe request arrives from your registered IP and is accepted.Chainalysis allowlist.

Before you begin

To follow this guide, you’ll need:

  • Admin access to your VPN, proxy, and firewall configuration.
  • Static public IP addresses on your internet connection. If you’re not sure, ask your internet service provider (ISP).
  • Your Chainalysis CSM contact in order to register your IPs.

Chainalysis domains to route

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

Find your fixed egress IPs

From a device on your office network or VPN, visit a “what is my IP” service such as https://kyt.chainalysis.com/cdn-cgi/trace and note the address. Do this for each office, VPN concentrator, and data center. Confirm with your network team or ISP that these addresses are static.

If your network is dual-stack, also find your IPv6 /64 range. Browsers often prefer IPv6, so this matters even if most traffic is IPv4.

2

Send remote users through the VPN

  • Full tunnel: if your VPN already sends all traffic through the tunnel, no change is needed.
  • Split tunnel: add *.chainalysis.com (or kyt.chainalysis.com and api.chainalysis.com) to the list of destinations that go through the tunnel. Most VPNs support domain-based include lists. If yours only supports IP routes, use a full tunnel for Chainalysis users instead since our IPs change.
3

Check your web proxy

If your users go through a web proxy, make sure Chainalysis domains are proxied and not listed as direct or bypass in your PAC file. Confirm the proxy’s outbound address is one of the fixed IPs from step 1.

4

Pin outbound NAT on your firewall

Make sure your firewall translates traffic to Chainalysis to a static public IP, not a pool that can change. If you have several internet links, either pin Chainalysis traffic to one link or register the IPs of every link.

5

Cover servers and integrations

Servers that call the Chainalysis API also need a fixed egress IP. On-premises servers should use the same firewall NAT; cloud servers should follow our Cloud NAT guide.

6

Register your IPs with Chainalysis

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

  • Your fixed egress IPv4 addresses and, if your network uses IPv6, your IPv6 /64 range.
  • Your organization name and the Chainalysis account or organization each IP applies to.
  • Whether each address is used for the web interface, the API, or both.

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.

7

Confirm your connection

  1. From your office, sign in to KYT.
  2. From a remote user on the VPN, sign in again and confirm that https://kyt.chainalysis.com/cdn-cgi/trace shows a registered IP.
  3. Run a test API call from all systems that use the KYT API.

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 https://kyt.chainalysis.com/cdn-cgi/trace and confirm the address with your CSM or Chainalysis Support.
  • Likely cause: Split tunnelling sends Chainalysis traffic directly to the internet.
  • How to resolve: Connect to the VPN and route all of *.chainalysis.com through the allowlisted IP.
  • Likely cause: Your public IP is dynamic, or traffic uses a different internet link.
  • How to resolve: Use static IPs and pin Chainalysis traffic to one link, or register every link.
  • 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: 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.