> 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.

# Netskope Dedicated Egress IP

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.

Netskope normally sends traffic out from shared NewEdge addresses. Dedicated Egress IP (DEIP) gives your tenant static egress addresses that only you use. With conditional DEIP you can send just Chainalysis traffic through those addresses.

## How it works

| Stage                  | What happens                                                  | Where it’s configured                                                         |
| :--------------------- | :------------------------------------------------------------ | :---------------------------------------------------------------------------- |
| 1. User                | The Netskope Client steers traffic to NewEdge.                | Steering configuration ([step 2](#make-sure-chainalysis-traffic-is-steered)). |
| 2. Netskope proxy      | NewEdge inspects the traffic and checks your DEIP conditions. | Dedicated Egress IP Footprint ([step 3](#turn-on-deip-for-chainalysis)).      |
| 3. Dedicated egress IP | Matching traffic leaves from your dedicated address.          | Netskope IP ranges ([step 4](#record-your-dedicated-ips)).                    |
| 4. Chainalysis         | The request arrives from your registered IP and is accepted.  | Chainalysis allowlist.                                                        |

## Before you begin

To follow this guide, you’ll need:

* A Netskope Dedicated Egress IP license (global or regional).
* Tenant admin access to the Netskope console.
* The Netskope Client deployed to users.
* Your Chainalysis CSM contact in order to register your IPs.

## Chainalysis domains to route

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

| Domain                | What it’s used for                           | Notes                                                                                                                   |
| :-------------------- | :------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------- |
| `*.chainalysis.com`   | All 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.com` | The 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.com` | The 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`.          |

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

## Configuration steps

### Get a Dedicated Egress IP license

Ask your Netskope account team for Dedicated Egress IP. Once it is licensed, Netskope enables it on the back end for your tenant. Choose regions that match where your Chainalysis users work.

### Make sure Chainalysis traffic is steered

In your steering configuration, check that web traffic is steered to Netskope and that `chainalysis.com` is not listed as a steering exception or bypass. Traffic that bypasses Netskope leaves from your local network instead.

### Turn on DEIP for Chainalysis

* Go to **Settings > Security Cloud Platform > Configuration > Dedicated Egress IP Footprint** and turn it on. It is off by default.
* Add conditions matching the Chainalysis domains so only that traffic uses your dedicated IPs. Conditions are OR'ed: a match on any one sends traffic through DEIP.
* If you add no conditions, DEIP applies to all traffic through NewEdge.

> **Note**
>
> **Note:** Conditional DEIP can run alongside Localization Zones, so Chainalysis uses your dedicated IPs while other browsing keeps using shared Netskope addresses.

### Record your dedicated IPs

Find your addresses at **Settings > Security Cloud Platform > Enforcement > Netskope IP Ranges**. DEIPs cannot be aggregated, so list each one.

### 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.

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 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 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

1. On a device running the Netskope Client, sign in to [KYT](http://kyt.chainalysis.com).
2. In Netskope Skope IT, find the Chainalysis requests and confirm they used your dedicated egress IP.
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`](https://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](https://www.chainalysis.com/key-rotation/).

If you have issues, please contact [`support@chainalysis.com`](mailto: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 with your CSM that the exact egress IPs are registered and active.

#### The KYT user interface works but API calls return a 403 error.

* **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](/resources/docs/ip-allowlisting/setup-guides/cloud-nat-gateway)).
  * 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/).

#### 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.

#### Requests leave from a shared Netskope IP.

* **Likely cause:** No DEIP condition matches, or DEIP is not turned on.
* **How to resolve:** Check the Dedicated Egress IP Footprint toggle and your Chainalysis conditions.

#### Works in the office but not for remote users.

* **Likely cause:** The Netskope Client is off, or Chainalysis is a steering exception.
* **How to resolve:** Turn on the client and remove `chainalysis.com` from steering exceptions.

## Additional support

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