Files.com is a large, global cloud and SaaS application. Many of our customers are in environments that require whitelisted IP addresses, so we commit to publishing a list of IP addresses that are used for inbound or outbound connections to Files.com.

If you need to Whitelist Files.com in your firewall, this article explains how to do it. If your firewall does not require whitelisting of file transfer traffic, this article may not be applicable to you.

Files.com IP Address Simplification and Transition

We have recently acquired our own contiguous IP address range and will be transitioning to exclusive use of that range for inbound or outbound connections to Files.com. This IP address transition will occur on March 2, 2026. This date was chosen to provide 9 months worth of advance notice and avoid the busy Q4 season where many organizations have change freezes.

After that date, only a single firewall rule will be required to whitelist the entire Files.com IP Range.

Until that date, whitelisting Files.com's IPs is more complicated, because we currently use both our Owned IP Range and an additional long list of IP addresses that we exclusively control on Amazon Web Services (AWS).

Make sure that all IP addresses are whitelisted, as we do use them all and often switch our active IPs as part of our standard operational procedures.

Files.com Owned IP Range

Files.com owns the IP Range 198.72.80.0/20, which includes all IP Addresses from 198.72.80.0 through 198.72.95.255.

Lists of Non-Owned IP addresses Used

The following IP Address lists represent IP Addresses that are owned by Amazon Web Services but exclusively used by Files.com.

These lists are extensive because they include 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.

We offer an IP Address List API, however it no longer useful. We will not be changing this list any more as part of our transition to the Files.com Owned IP Range.

Until March 2, 2026, you will need to whitelist all of the following IP addresses in addition to the FIles.com Owned IP Range.

You will be able to remove this additional list after March 2, 2026.

Additionally, if your site was formerly an ExaVault site that was migrated to Files.com and still uses the ExaVault host key, you will also need to whitelist the list of Non-Owned IP Addresses below that specifically applies to sites using the ExaVault host key.

13.115.185.197
13.211.6.58
13.211.8.8
13.228.110.5
13.230.174.211
13.251.23.79
13.251.75.92
18.130.82.3
18.130.85.21
18.184.31.111
18.196.218.237
18.196.249.148
18.205.187.185
18.210.222.34
3.124.213.47
34.193.60.221
34.194.175.247
34.204.145.250
34.204.150.23
34.204.153.236
34.204.236.250
34.204.250.40
34.205.137.182
34.206.140.166
34.246.103.210
34.251.118.53
34.252.200.237
35.157.95.231
35.176.125.40
35.178.122.29
35.178.154.72
35.178.42.15
35.178.42.158
35.182.68.20
46.51.239.135
52.17.96.203
52.18.87.39
52.20.236.84
52.215.35.55
52.221.157.129
52.23.22.134
52.28.101.76
52.29.176.178
52.44.29.99
52.56.167.16
52.56.197.159
52.58.79.145
52.60.101.109
52.60.113.8
52.60.129.247
52.60.153.17
52.60.214.201
52.60.239.159
52.60.245.89
52.62.59.186
52.64.150.164
52.64.199.91
52.64.2.88
52.64.251.226
52.64.6.120
52.68.30.197
52.68.4.44
52.74.166.120
52.74.188.115
52.77.142.208
52.77.8.56
52.8.210.89
52.9.227.24
54.193.65.189
54.193.69.198
54.193.69.200
54.193.69.72
54.207.27.239
54.208.20.30
54.208.63.151
54.209.222.205
54.209.231.233
54.209.231.99
54.209.242.244
54.209.246.217
54.209.91.52
54.232.253.47
54.64.240.152
54.95.179.0
54.95.60.23
99.79.110.182

Former ExaVault Customers Using The ExaVault Host Key

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 are also used (in addition to the addresses above).

13.228.186.243
13.238.24.104
13.42.187.250
13.43.144.19
13.43.252.114
15.156.171.39
15.157.18.35
15.222.152.139
15.223.99.121
18.130.100.59
18.140.210.180
18.141.46.121
18.142.81.195
18.169.205.250
18.179.140.197
18.192.220.219
18.205.170.87
18.205.8.81
18.233.238.114
3.1.164.240
3.10.244.187
3.104.7.236
3.105.246.2
3.105.7.234
3.11.144.56
3.11.99.9
3.115.57.224
3.217.82.30
3.227.183.71
3.232.229.87
3.24.7.224
3.64.69.163
3.69.89.96
3.71.218.186
3.98.119.91
3.98.231.156
3.98.73.0
34.192.34.71
34.202.116.48
34.202.23.159
34.202.28.186
34.231.28.146
34.233.32.85
35.157.224.212
35.158.202.135
35.171.168.150
35.174.249.23
44.197.126.42
44.205.164.56
44.205.181.212
44.205.218.209
44.205.47.95
47.128.84.237
52.195.51.46
52.198.164.219
52.58.177.36
52.58.234.163
52.60.180.89
52.62.116.80
52.63.177.193
52.69.163.199
54.175.70.146
54.199.165.62
54.205.227.156
54.250.51.79
54.254.174.4
54.254.184.120
54.79.148.165
54.82.79.68
54.84.38.86
54.86.1.128
57.180.72.80

Ports

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.

Outbound Connections from Files.com

For Outbound Connections from Files.com, Files.com will use IPs from our owned IP range or the non-owned IP list above for all of outbound connections, including Webhooks, SMTP, LDAP, and Remote Server connections.

If you have configured dedicated IP addresses for your site, you can configure some features to use those IP addresses for outbound connections. Whenever possible, we recommend not using your dedicated IP addresses for outbound connections; the ability to do so is provided for rare situations when the counterparty has strict firewall requirements that would make it unfeasible to whitelist all of the addresses in the general Files.com pool.

Remote Server connections can be configured to use your dedicated IP addresses for outbound connections, which will be used for our Remote Server Sync and Remote Server Mount features. The Custom SMTP feature also supports this capability, as does the Webhooks feature.