IP Addresses are the way computers are addressed on the Internet. IP Addresses typically come up in the conversation of a firewall or client configuration. Files.com currently supports only IPv4 addresses. IPv6 addresses are not supported.
Files.com is a large global cloud application. Many of our customers are in environments that require whitelisted IP addresses, so we commit to publishing a list of IP addresses that may be involved in inbound or outbound connections to Files.com.
The list is extensive because it includes IPs in all regions where we operate servers, as well as IPs for different service types and integration endpoints for our various integrations. Unfortunately, we are not able to split this list into sub-lists by region or by integration type.
This list may change. To keep up to date with the latest list, please regularly poll our IP Address List API.
Files.com does not offer IPv6 addresses.
files-cli ip-addresses get-reserved
Use this command if your account is migrated from ExaVault and configured to use the ExaVault host key:
files-cli ip-addresses get-exavault-reserved
22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199
Please make sure that all IP addresses are white-listed, as we may switch between these at any time.
Some sites that were migrated from the ExaVault architecture will provide the same host key that was used on ExaVault. For those sites, these IP addresses should also be whitelisted (in addition to the addresses above), if your networking configuration requires a whitelist.
188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199
Please make sure that all IP addresses are white-listed, as we may switch between these at any time. ExaVault does not provide IPv6 addresses.
If you restrict inbound or outbound access via a firewall, you may also need to determine which ports to whitelist in conjunction with our IP list. Ports are protocol specific.
For API traffic, which is used by our Desktop app, mobile apps, web app, CLI, SDKs, and API, port 443 (HTTPS) should be whitelisted.
If you are using FTP, you will need to whitelist port 21 and FTP data ports 40000-50000, and optionally our three alternate FTP ports 990, 3021, and 3990 if they apply to your use case.
If you are using SFTP, you will need to whitelist port 22 and optionally our alternate SFTP port 3022 if it applies to your use case.
For Outbound Connections from Files.com, Files.com will use IPs from the above list for all of outbound connections, including Webhooks, SMTP, LDAP, and Remote Server connections.
The exception is if you have configured dedicated IP Addresses for your site. By default, Files.com will use your dedicated IP addresses for outbound connections to remote servers. This applies to our Remote Server Sync and Remote Server Mount features. However, you can disable the use of your dedicated IP in these circumstances if you need to. For example, you might do that if your counterparty has already whitelisted the main Files.com IP range.
We do not support or recommend that any of our customers ever hardcode IP addresses directly into their client application. We use DNS as part of our redundancy and disaster recovery strategy, and we expect that our customers will always use DNS to look up [subdomain].files.com or app.files.com as appropriate. We also use Geo-DNS to route traffic to the fastest and closest available server, as well as to take troubled servers out of the active pool.
Using a hardcoded or stale IP may well direct you to a server that is down, currently undergoing maintenance, etc.
If you absolutely must use a hardcoded or static IP address, the best workaround is to provision a Custom Domain for your site. When you add a Custom Domain, we will provision a pair of dedicated IPs for your site. It is our goal to have your dedicated IPs remain the same, and we work hard to avoid having IP addresses change out from under you. In practice, dedicated IPs for our customers have remained the same for the past several years.
If we ever have to make changes to dedicated IP addresses that are associated with a custom domain, we will endeavor to provide advance notice. If you need real-time notification of changes, you may poll the the IP Addresses API endpoint to monitor when a change occurs. This endpoint returns a response including both our published list of IP addresses and your site's 2 dedicated IP addresses.
Customers often ask for dedicated IP addresses as a way to avoid having to whitelist a huge list of IP addresses for firewall purposes.
Files.com automatically provisions a pair of dedicated IP addresses for every site that has a custom domain enabled. We do that because FTP, unlike HTTP, requires that every custom domain be hosted on a dedicated IP address in order to have a custom SSL Certificate that matches the domain.
This means that if you have users who restrict outbound access via a firewall, they will only need to whitelist your 2 dedicated IP addresses rather than our entire published list of IP addresses (see above).
Custom domains and dedicated IPs are only available on the Power and Premier plans. If you are on a Starter plan, you will need to upgrade to use a custom domain or dedicated IPs.
Dedicated IPs, once provisioned, are used for both inbound connections to your site via your custom domain, as well as outbound connections from Files.com to Remote Servers that are used for Remote Server Sync and Remote Server Mount.
Files.com does not offer IPv6 addresses for dedicated addresses.
When you use a Files.com-provided SSL certificate with a custom domain, inbound connections to your default account subdomain ([subdomain].files.com) address will also use your dedicated IPs because your custom domain uses a CNAME pointing at the default subdomain address.
When using your own SSL certificate with a custom domain, inbound connections to the Files.com subdomain address ([subdomain].files.com) will use the Files.com general IP pool of IP addresses. Inbound connections to your own custom domain (yoursubdomain.yourcompany.com) will use your dedicated IP addresses.
Remote Servers can be configured to either use your dedicated IP addresses or to use the Files.com general IP pool of IP addresses. The setting for using dedicated IP addresses for remote servers applies to both our Remote Server Sync and Remote Server Mount features.
However, you can disable the use of your dedicated IP in these circumstances if you need to. (You might do that if your counterparty has already whitelisted the main Files.com IP range, for example.)
We will not use your dedicated IP addresses for other types of outbound connections such as webhooks, LDAP, or SMTP. Our view is that this likely isn't a priority for most customers. If you have a need to have webhooks, LDAP, or SMTP originate from a dedicated IP address, we'd love to learn more about your exact use case.
In order to receive dedicated IP addresses for your site, you will first need to set up a custom domain. Once your custom domain is set up and active, you can look up your 2 dedicated IP addresses. Type "Firewall" in the search box at the top of every page and click on the matching result.
Dedicated IP addresses are exclusive to your Files.com site and act as static IP addresses.
It is our goal to have your dedicated IPs remain the same, and we work hard to avoid having IP addresses change out from under you. In practice, dedicated IPs for our customers have remained the same for the past several years. If we ever have to make changes to your IP addresses, we will endeavor to provide advance notice.
We have implemented an automated mechanic for you to be able to get real time notifications when a change occurs. You can achieve this by polling the
/ip_addresses API endpoint shown in our API documentation. This endpoint returns a response including both our published list of IP addresses, and your site's 2 dedicated IP addresses.
If you change the primary region where files are hosted on your Files.com site, we will issue you new IP addresses in the new region and release your old IP addresses.
If you remove a custom domain from your site, the dedicated IPs associated with that custom domain are removed from active use and are no longer associated with your site.
Your users are still able to connect using your subdomain.files.com address as the host, but are no longer able to connect via your custom domain, and your subdomain will no longer resolve to the 2 IP addresses that were dedicated to your site.
After your custom domain is deactivated, your subdomain will resolve to an IP address from the general pool. Those users who require whitelisting in their local network firewalls or elsewhere will need to cover that entire list to ensure that they have consistent connection results.
If your organization blocks all online file sharing by default, this may inadvertently block access to your files. In this situation, even if you whitelist all of the necessary IP addresses to allow connections to and from the Files.com service, you may not be able to transfer items from the Files.com backend.
By default, Files.com will store files in Amazon S3. To access those files, you can enable file transfers by allowing all of the URLs that start with the patterns listed in the table below. If you have enabled Regional Storage to restrict your account to one of our supported regions and you have disabled Global acceleration, then you can allow only the subset of URLs which matches your storage region.
|STORAGE REGION||STORAGE URL BEGINS WITH|
|EU - Germany, Frankfurt|
Additional Content in This Section:
Get Instant Access to Files.com
The button below will take you to our Free Trial signup page. Click on the white "Start My Free Trial" button, then fill out the short form on the next page. Your account will be activated instantly. You can dive in and start yourself or let us help. The choice is yours.Start My Free Trial