This document provides endpoint information needed to allow Silo connections from behind a firewall. If your environment utilizes a firewall to manage network traffic, you may need to implement an exception for ALL applicable entries.
Domain Names
Domain names can be broadly whitelisted using a wildcard entry as shown in the following examples:
*.authentic8.com
*.a8silo.com
*.getsilo.com
Connection Type
Silo uses a TLS connection over port 443 (HTTPS) with the Web Client, while the Installed Client uses a custom network protocol over port 443. We recommend creating a full exception in order to prevent connection issues with various Silo client types.
SSL Inspection
SSL inspection (e.g. SPI/DPI) will need to be disabled for Silo connections.
NOTE: This rule does not apply to Silo Windows Client version 2.9.13 and newer. Please see this article:
https://authentic8.freshdesk.com/a/solutions/articles/16000100713 for additional information.
External API
Some customers may need to whitelist our External API endpoint in order to use other Silo services.
An exception for the following domain will be needed: extapi.authentic8.com
IP Addresses
Please make sure to allow access to TCP port 443 for the following entries:
Web Client IP (a8silo.com):
35.192.87.85
35.192.140.0
Authentic8 registered IP address space:
194.32.244.0 /22
171.22.200.0 /22
92.119.244.0 /22
Third Party Provider:
13.54.16.216
13.239.146.29
35.246.2.137
35.246.47.160
104.155.106.249
130.211.64.174
104.199.169.130
104.199.158.183
104.155.196.214
104.155.196.156
104.196.50.57
104.196.45.238
104.197.151.226
8.34.212.21
104.198.108.190
104.198.102.199
Legacy IP addresses:
* If you are using the legacy load balancers, you may need to create an exception for the following entries:
13.54.16.216
66.85.157.14
198.24.179.20
119.81.23.186
52.193.1.47
5.153.13.248 /29
5.153.51.130
Additional Notes
Please contact Support if you have any additional questions and/or require further information.