Skip to navigation

Tailscale and WireGuard

Route Chainalysis through an app connector, exit node, or WireGuard server you control

If your team uses Tailscale or WireGuard, you can give all Chainalysis traffic one fixed exit point: a server you control with a static public IP. Users can work from anywhere, and Chainalysis only ever sees your registered address.

Choose an option

OptionWhat goes through the static IPBest for
A. Tailscale app connector (recommended)Only traffic to Chainalysis domains. Everything else goes direct.Tailscale users who want Chainalysis routed without changing their other traffic.
B. Tailscale exit nodeAll of the user’s internet traffic while the exit node is on.Teams that already route all traffic through an exit node.
C. Self-hosted WireGuardAll of the user’s internet traffic while the tunnel is up.Teams that run their own WireGuard VPN without Tailscale.

Note: Tailscale’s Mullvad exit nodes and other commercial VPN services are shared with other customers, so we can’t allowlist them. The exit point must be a server you control with a static IP.

Before you begin

To follow this guide, you’ll need:

  • A Linux server with a static public IP. For example, a cloud VM with an AWS Elastic IP, an Azure static public IP, or a reserved Google Cloud address. Run two servers in different zones if you need resilience, and register both IPs.
  • For Tailscale: Owner, Admin or Network admin rights on your tailnet, and access to edit the tailnet policy file.
  • For WireGuard: root access on the server and a way to distribute client configurations.
  • Your Chainalysis CSM contact in order to register your IPs.

Prepare the server

All three options need IP forwarding turned on. On the server, run:

echo 'net.ipv4.ip_forward = 1' | sudo tee -a /etc/sysctl.d/99-forwarding.conf
echo 'net.ipv6.conf.all.forwarding = 1' | sudo tee -a /etc/sysctl.d/99-forwarding.conf
sudo sysctl -p /etc/sysctl.d/99-forwarding.conf

Then check the server’s public IP with curl -s https://kyt.chainalysis.com/cdn-cgi/trace. This is the address you’ll register with Chainalysis. If the server also has IPv6, note its /64 range.

Option A: Tailscale app connector

An app connector routes traffic for specific domains through a chosen device. Clients keep their normal internet path for everything else. App connectors are available on all Tailscale plans and run on Linux.

1

Update the tailnet policy file

In the Tailscale admin console, open Access controls and add these sections (merge them into any you already have):

"tagOwners": {
"tag:chainalysis-connector": ["autogroup:admin"]
},
"autoApprovers": {
"routes": {
"0.0.0.0/0": ["tag:chainalysis-connector"],
"::/0": ["tag:chainalysis-connector"]
}
},
"nodeAttrs": [
{
"target": ["*"],
"app": {
"tailscale.com/app-connectors": [
{
"name": "Chainalysis",
"connectors": ["tag:chainalysis-connector"],
"domains": ["chainalysis.com", "*.chainalysis.com"]
}
]
}
}
]

Your grants must also let users reach internet routes (autogroup:internet) and the connector on port 53 for DNS:

{ "src": ["group:chainalysis-users"], "dst": ["autogroup:internet"], "ip": ["*"] },
{ "src": ["group:chainalysis-users"], "dst": ["tag:chainalysis-connector"], "ip": ["tcp:53", "udp:53"] }
3

Check the app in the console

Open the Apps page in the admin console. You should see the Chainalysis app with your connector listed. If you manage your policy file with GitOps or Terraform, make the changes there instead, or they will be overwritten.

Note: Traffic to Chainalysis domains leaves from the connector’s public IP, not its Tailscale (100.x) address, even if the user also has an exit node turned on. Register the public IP.

Option B: Tailscale exit node

2

Approve it

In the admin console, open Machines, find the server (it shows an Exit Node badge), open its menu and select Edit route settings > Use as exit node. You can also auto-approve exit nodes with autoApprovers in the policy file.

3

Allow users to use it

If you use a custom policy, add a grant with dst set to autogroup:internet for the users who need Chainalysis access.

4

Turn it on for users

Users select the exit node from the Tailscale client menu, or on Linux:

sudo tailscale set --exit-node=<exit-node-name-or-ip>

To make sure users can’t forget, deploy a mandatory exit node through your MDM using Tailscale’s system policies.

Option C: Self-hosted WireGuard

WireGuard routes by IP address, not domain name. Because Chainalysis IP addresses change, Chainalysis users need a full tunnel: all traffic goes through the server while the tunnel is up.

1

Configure the server

Example /etc/wireguard/wg0.conf on the server (replace eth0 with the server’s internet-facing interface):

[Interface]
Address = 10.8.0.1/24
ListenPort = 51820
PrivateKey = <server-private-key>
PostUp = iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
PostDown = iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE
[Peer]
PublicKey = <client-public-key>
AllowedIPs = 10.8.0.2/32

Start it with sudo systemctl enable --now wg-quick@wg0 and open UDP port 51820 in the server’s firewall or security group.

2

Configure clients for full tunnel

[Interface]
Address = 10.8.0.2/32
PrivateKey = <client-private-key>
DNS = 1.1.1.1
[Peer]
PublicKey = <server-public-key>
Endpoint = <server-static-ip>:51820
AllowedIPs = 0.0.0.0/0, ::/0
PersistentKeepalive = 25

AllowedIPs = 0.0.0.0/0, ::/0 sends all IPv4 and IPv6 traffic through the tunnel. If the server has IPv6, add an IPv6 NAT rule as well and register its /64. If it has none, IPv6 traffic will fail and clients will fall back to IPv4.

Register your IPs with Chainalysis

For all options, you must register your IPs with Chainalysis. Send your CSM or Chainalysis support the public IP of every connector, exit node, or WireGuard server, plus the IPv6 /64 of each if it has IPv6. Don’t send Tailscale (100.x) or WireGuard tunnel (10.x) addresses: these are private and can’t be allowlisted.

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.

Confirm your connection

  1. With Tailscale or WireGuard connected, sign in to KYT.
  2. For an exit node or WireGuard, run curl -s https://kyt.chainalysis.com/cdn-cgi/trace on the client: it should return the server’s static IP.
    • With an app connector, this shows the connector’s public IP, because traffic to Chainalysis domains goes through the connector.
  3. For an app connector, run tailscale status on the client and check if the connector is online, then confirm KYT sign-in works from a network that isn’t registered.
  4. Run a test API call from every system that uses the Chainalysis 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: The exit node is optional on the client.
  • How to resolve: Use an app connector instead, or deploy a mandatory exit node with MDM.
  • Likely cause: IP forwarding or NAT isn’t set on the server.
  • How to resolve: Recheck the forwarding settings and the MASQUERADE rule.
  • 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.