If your firewall allows a wildcard hostname when setting up rules, we recommend using the hostname for Wildcard (All services). If specific sites or hostnames are required in your firewall, the table below shows service specific hostnames. Simply replace the domain with your actual domain (customer account) name.
| Hostnames (All locations) | |
| Component | Hostname(s) |
| Wildcard (All services) |
*.egnyte.com |
| Cloud Services |
domain.egnyte.com |
| Sync | sync-domain.egnyte.com |
| FTP |
ftp-domain.egnyte.com |
| Migration App for On-Premises Source | Review the Migration App Specifications section of the Product Guide |
| Smart Cache | Review the Firewall Domains Allowed section of the Hyper-V or VMware Product Guides |
Active Directory, External HSM, and Custom SMTP IP Addresses
If using a Directory Service Integration, like Microsoft Active Directory and/or external HSM, then allow the following IP subnets. These subnets can be utilized alongside the hostnames within the Directory Service Integration, especially if hostnames cannot be used.
| Location | Default IP Subnet Address |
| Global |
162.216.249.0/24 162.216.250.0/24 162.216.251.0/24 162.216.252.0/24 |
Mail Server IP Addresses
To ensure users are able to receive all emails from Egnyte, add the following IP addresses to your allowed sites. If using a custom SMTP email server, whitelist the Global IP addresses listed above in addition to the mail server IP addresses below.
| Location | Mail Server IP Addresses |
| Global |
168.245.53.124 208.117.56.144 149.72.193.80 149.72.202.3 149.72.133.214 |