Egnyte Public IP Address for Firewall Rules

Using Hostnames

If your firewall allows a wildcard hostname when setting up rules, we recommend using the hostname below rather than specific IP addresses which can change. 


If specific sites or hostnames are required, use the following below. Replace <domain> with your actual domain name.


Using Public IP Addresses

Egnyte maintains a list of public IP addresses for customers that requires a whitelist rule. 

Last Updated: 14th August 2018

Component New Ip(s) Datacenter
Web UI and Drive
Sync Europe
Backup Europe
Access URL Europe
FTP Europe
Mail Server Europe
Default NAT IP* Europe
IP Range, Europe
SAML Authentication Europe


Component Old IP(s) New IP(s) Datacenter
Web UI and Drive
East Coast - US
Events East Coast - US
Sync East Coast - US
Backup East Coast - US
Access URL East Coast - US
FTP East Coast - US
Mail Server East Coast - US
Default NAT IP* East Coast - US
SAML Authentication East Coast - US


Component Old IP(s) New IP(s) Datacenter
Web UI and Drive
West Coast - US
Events West Coast - US
Sync West Coast - US
Backup West Coast - US
Access URL West Coast - US
FTP West Coast - US
Mail Server West Coast - US
Default NAT IP* West Coast - US
SAML Authentication West Coast - US

              *Typically used for Directory Service Integration such as Microsoft Active Directory or custom SMTP.


List of outbound connections from CMM:

     Google DNS both UDP and TCP protocols on port 53

  • IPv4:,
  • IPv6: 2001:4860:4860::8888, 2001:4860:4860::8844


Note: IP addresses may be added or removed. While we strive to keep IP changes at a minimum,  new IP addresses may be required for operational purposes. 

Need help? Contact us at with any questions, comments, or concerns about new addresses. 


Egnyte Community

Egnyte Community

Want to connect with other Egnyte users and our Egnyte team? Share ideas and ask questions in our Community .