> For the complete documentation index, see [llms.txt](https://docs.silkline.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silkline.ai/configuration/network-allowlist.md).

# Network Allowlist

Configure ingress (Silkline IP addresses) and egress (Silkline domains) allowlist rules so integrations and webhooks can connect through network controls

## Overview <a href="#h_network_allowlist_overview" id="h_network_allowlist_overview"></a>

When connecting Silkline to external systems that enforce network-level access controls, you may need to configure both **ingress** (traffic from Silkline into your system) and **egress** (traffic from your system out to Silkline) rules. The two directions are configured differently — ingress is covered by allowlisting Silkline's IP addresses, while egress requires allowlisting Silkline's domain names.

{% hint style="info" %}
**Ingress vs. egress**:

* **Ingress**: Silkline reaches your system (e.g. Silkline calling your Manufacturo API). Allowlist the Silkline IP addresses below.
* **Egress**: Your system reaches Silkline (e.g. Manufacturo sending webhooks to Silkline). Allowlist the Silkline domains below — IP-only allowlisting is not sufficient for egress.
  {% endhint %}

## Ingress: Silkline IP Addresses <a href="#h_silkline_ip_addresses" id="h_silkline_ip_addresses"></a>

Add the following IP addresses to your allowlist for traffic coming **from** Silkline **into** your system:

| IP Address     |
| -------------- |
| `3.32.104.229` |
| `3.32.154.65`  |
| `96.127.63.31` |
| `3.32.119.86`  |
| `3.32.177.28`  |
| `3.32.254.198` |

{% hint style="warning" %}
**Important**: Ensure all six IP addresses are allowlisted. Missing even one may cause intermittent connectivity issues as Silkline routes traffic across multiple addresses.
{% endhint %}

## Egress: Silkline Domains <a href="#h_silkline_domains" id="h_silkline_domains"></a>

For traffic leaving your system **to** Silkline (for example, webhook callbacks), allowlist the following domains. Egress policies typically cannot be satisfied by IP allowlisting alone because Silkline's hostnames resolve to a rotating set of addresses.

| Environment | Application domain        | Authentication domain      |
| ----------- | ------------------------- | -------------------------- |
| Production  | `app.silkline.ai`         | `auth.silkline.ai`         |
| Test / Gov  | `dev-app-gov.silkline.ai` | `dev-auth-gov.silkline.ai` |

The authentication domain is where users sign in. Allowlist it wherever a proxy or firewall filters your users' browser traffic, including for [SSO](https://docs.silkline.ai/configuration/sso-configuration.md) sign-ins — a blocked authentication domain prevents login even when the application domain is reachable.

{% hint style="warning" %}
Allowlist only the domain(s) that match the environment you are connecting to. Most customers only need `app.silkline.ai` and `auth.silkline.ai`.
{% endhint %}

## When to Allowlist

You need to allowlist these IPs or domains when:

* Connecting Silkline to an on-premise or IP-restricted system
* Your external system's firewall blocks unknown inbound connections (ingress)
* Your external system's outbound proxy blocks unknown destinations (egress)
* Setting up integrations that require Silkline to reach your system's API (e.g., [Manufacturo](https://docs.silkline.ai/configuration/integrations/manufacturo.md), webhook endpoints)
* Connecting an [Epsilon3](https://docs.silkline.ai/configuration/integrations/epsilon3.md#fedramp-workspaces) workspace on Epsilon3's FedRAMP deployment (each workspace is allowlisted separately)

{% hint style="info" %}
If you are unsure whether your system requires network allowlisting, contact your network administrator or reach out to Silkline support.
{% endhint %}
