> This page is for Resources.

> For clean Markdown of any page, append .md to the page URL. For an index of any product or section, append /llms.txt to its URL (e.g. /kyt/docs/llms.txt). The root index at /llms.txt lists every product.

# Set up your IP allowlist

An IP allowlist is a required security measure that lets you specify the IP addresses that can access Chainalysis products. This currently includes:

* The KYT user interface and KYT API. API requests must come from an IP address on your allowlist.
* Address Screening
* Reactor

IPs you send us will be added to the IP allowlist. After it’s set up, only IP addresses on your allowlist are authorized. Other IP addresses that attempt to access these products or make API requests are automatically rejected, even if they have valid login details or an API key.

Any IP address not on your allowlist fails with a `403` status code and the following message: “Access Restricted. Your IP address is not on the Chainalysis Allowed IPs List.”

This page provides information on the types of IPs we support, how to submit IP addresses to us, and frequently asked questions. It also provides a number of [guides](#what-guides-do-you-have-available) on routing Chainalysis traffic through dedicated egress IPs.

## IP address support

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.

| What we accept        | Notes                                                                                                                                                                                                                         |
| :-------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Public IPv4 addresses | Individual 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 ranges           | Send 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 only     | This includes corporate VPNs, proxies, office gateways, dedicated security-cloud IPs, and cloud NAT addresses.                                                                                                                |

At this time, we don’t 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.

## Instructions to set up your IP allowlist

Identify the fixed public IP addresses your users and systems use to reach Chainalysis, such as your corporate VPN, proxy, office gateway, or cloud NAT. Include your IPv6 `/64` range if your network uses IPv6.

* We can accept up to 50 addresses. We don’t accept home internet connections, shared or commercial VPN services, or broad ISP ranges.

Complete the

IP submission template

and send it to your CSM or [`support@chainalysis.com`](mailto:support@chainalysis.com). This template requests:

* Your organization name and ID.
* A technical contact’s name and email address.
* Your IP address or range.
* IP version.
* Source type.
* What it’s used for (the UI, the API, or both).
* A location and description of the IP address.
* What you want us to do with the IP address (add it or remove it from the allowlist).

We’ll add your IPs to an allowlist that can access Chainalysis products, and let you know when it’s completed.

After we add your IPs to the allowlist, please:

* Verify that you can log in to [KYT](https://kyt.chainalysis.com) or [Reactor](https://reactor.chainalysis.com).
* Reset your password (if your organization uses SSO, you can skip this):
  * To reset your password, log out and go to [`app.chainalysis.com`](https://app.chainalysis.com). Enter your email address, click **Continue**, select **Reset password**, and follow the on-screen instructions.
  * If you have issues resetting your password, please contact [`support@chainalysis.com`](mailto:support@chainalysis.com).
* Rotate your API keys by following the steps on [this page](https://www.chainalysis.com/key-rotation/).

> **Note**
>
> **Note:** If your organization uses a security cloud such as Zscaler, Netskope, Cloudflare, Cisco Umbrella, or Prisma Access, follow one of the [guides](#what-guides-do-you-have-available) below to route Chainalysis traffic through dedicated egress IPs.

## Frequently asked questions

#### Why are you doing this?

IP allowlisting adds a network-level control on top of passwords, multi-factor authentication, and API keys. Even if a credential is compromised, it cannot be used from outside your registered networks.

#### Which products are affected?

At this time, KYT (the UI and the API), Address Screening, and Reactor.

#### What do I need to do?

Provide Chainalysis with the following information:

* The fixed public IP addresses your traffic leaves your network from, including IPv4, or your IPv6 `/64` range if your network uses IPv6. Ranges broader than `/64` are subject to approval.
* 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.

Include this information in the

IP submission template

and send it to your Chainalysis CSM or Chainalysis Support.

For information on routing Chainalysis-specific traffic, check out the [guides](#what-guides-do-you-have-available) linked on this page. We include detailed steps for many different network configurations to get you connected to Chainalysis.

#### What should I do after you add my IPs to the allowlist?

After we add your IPs to the allowlist, please:

* Verify that you can log in to [KYT](http://kyt.chainalysis.com) or [Reactor](http://reactor.chainalysis.com).
* Reset your password (if your organization uses SSO, you can skip this):
  * To reset your password, log out and go to [`app.chainalysis.com`](http://app.chainalysis.com). Enter your email address, click **Continue**, select **Reset password**, and follow the on-screen instructions.
  * If you have issues resetting your password, please contact [`support@chainalysis.com`](mailto:support@chainalysis.com).
* Rotate your API keys by following the steps on [this page](https://www.chainalysis.com/key-rotation/).

#### How many addresses can my IP allowlist contain?

Up to 50 addresses in total. Every address in a range counts, so a `/24` counts as 256. Each IPv6 `/64` counts as one.

> **Note**
>
> **Note:** If you have a large network, discuss options with your CSM. A common fix is to route Chainalysis traffic through a small set of dedicated egress IPs.

#### Can I give you a domain name instead of IPs?

We only allowlist source IP addresses. In the other direction, you should always allow Chainalysis by domain (`*.chainalysis.com`) and not by our IP addresses as they change.

#### What guides do you have available?

Follow one of the guides below, depending on how your organization reaches the internet:

* [Zscaler Internet Access](/resources/docs/ip-allowlisting/setup-guides/dedicated-zscaler-ip)
* [Cisco Umbrella](/resources/docs/ip-allowlisting/setup-guides/cisco-umbrella-reserved-ip)
* [Palo Alto Prisma Access](/resources/docs/ip-allowlisting/setup-guides/prisma-access-egress-ip)
* [Netskope](/resources/docs/ip-allowlisting/setup-guides/netskope-dedicated-egress-ip)
* [Cloudflare Zero Trust (WARP / Gateway)](/resources/docs/ip-allowlisting/setup-guides/cloudflare-dedicated-egress-ip)
* [Servers in AWS, Azure or Google Cloud](/resources/docs/ip-allowlisting/setup-guides/cloud-nat-gateway)
* [Tailscale or self-hosted WireGuard](/resources/docs/ip-allowlisting/setup-guides/tailscale-and-wire-guard)
* [Corporate VPN, web proxy, or office firewall (everything else)](/resources/docs/ip-allowlisting/setup-guides/corporate-network)

#### We use Zscaler, Netskope, Cloudflare, Mullvad, or another shared service. Can you allowlist their IPs?

Not their shared egress pools, because other organizations use the same addresses. Most of these services offer dedicated egress IPs that only you use; our guides explain how to send Chainalysis traffic through them.

#### Our servers call the Chainalysis API from the cloud. What do we do?

Give those servers a fixed outbound address with a NAT gateway and a static public IP. The [Cloud NAT](/resources/docs/ip-allowlisting/setup-guides/cloud-nat-gateway) guide covers AWS, Azure, and Google Cloud.

## Troubleshooting

This section lists issues you might run into after setting up your IP allowlist and how to resolve them.

Each guide we provide includes additional troubleshooting information depending on how you connect to the internet.

#### Receiving the following message: “Access Restricted. Your IP address is not on the Chainalysis Allowed IPs List.”

* **Likely cause:** You’re connecting from an address that isn’t registered.
* **How to resolve:** Check your public IP at [https://kyt.chainalysis.com/cdn-cgi/trace](https://kyt.chainalysis.com/cdn-cgi/trace) and compare it with what you registered.

#### 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 `/64` range 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, 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](https://www.chainalysis.com/key-rotation/).

#### Remote users are blocked.

* **Likely cause:** They’re not on the VPN, or Chainalysis is split-tunnelled.
* **How to resolve:** Connect to the VPN and route all of \*.chainalysis.com through the allowlisted IP.