Network Information
Code42 app ports
List of ports that require outbound traffic to Code42. You must have both port 443 and 4287 open for use by Code42 apps.
|
Port |
Protocol |
Source |
Destination |
Description |
|---|---|---|---|---|
| 443 | HTTPS | Code42 endpoint agents | Code42 cloud | Communication for File Metadata Collection and deployment policy information |
| HTTPS | Web Browsers | Code42 cloud | Web restore (both zip file and device) and user activity profiles | |
| TLS | Code42 endpoint agents | Code42 cloud | Communication from device to the Code42 cloud (only applies to Code42 environments that sign in to the Code42 console at: https://www.crashplan.com/console) | |
| 4285 | HTTPS | Web Browsers | Code42 cloud | Web restore (both zip file and device) and user activity profiles |
| 4287 | TLS | Code42 endpoint agents | Code42 cloud | Communication from the device to the Code42 cloud |
Additional services integrated with Code42
These are some additional ports used by services that are commonly integrated with Code42 environments.
|
Port |
Protocol |
Source |
Destination |
Description |
|---|---|---|---|---|
|
8200 and 8201 |
TLS | Code42 cloud | Vault | Communication between a Vault instance and the Code42 cloud |
| 443 | HTTPS | Code42 cloud | AD FS server | Sync with AD FS |
| 636 | LDAPS | Your directory server | The Code42 User Directory Sync tool | Used by the Code42 User Directory Sync tool to sync with your directory service |
Code42 IP addresses
Code42 uses the following IP addresses to provide access to Code42 cloud storage. To ensure uninterrupted access to the Code42 cloud, open your firewall to the following IP addresses:
- 68.65.192.0/21
- 162.222.40.0/21
- 67.222.248.0/21
- 103.8.239.0/24
- 216.223.38.0/24
- 149.5.7.0/24
- 216.17.8.0/24
- 50.93.246.0/23
- 50.93.255.0/24
149.5.44.0/24 was formerly used but is now retired and no longer in use. You do not need to open your firewall to this range anymore. If you previously opened your firewall to this range, we strongly recommend removing it because Code42 will not control it after January 1, 2021.
- This information is subject to change, and we recommend that you subscribe to our announcements page in the Code42 Community to learn about upcoming changes to IP addresses. See the table below for the revision history of this article.
- To ensure uninterrupted connectivity to the Code42 cloud, you should have opened your firewall to all available IP addresses listed above before August 11, 2020. For more information, see IP address updates.
The IP addresses that your Code42 environment uses depends on where you sign in to the Code42 console. To ensure uninterrupted access to the Code42 cloud, open your firewall to IP addresses as follows:
-
- The Code42 IP addresses above
- IP addresses managed by AWS in region us-east-1 for Code42 traffic (over port 443)
-
- The Code42 IP addresses above
- Address https://event-ingest-default.prod.ffs.us2.code42.com in region us-east-1 for Code42 traffic (over port 443) if File Metadata Collection is enabled
-
- IP addresses managed by AWS region us-east-1 for all Code42 traffic (over ports 443 and 4287)
-
- The Code42 IP addresses above
- IP addresses managed by AWS in region eu-west-1 for all Code42 traffic (over ports 443 and 4287)
Amazon Web Services (AWS) IP addresses are highly dynamic across a very large range, so consider instead whitelisting the
*.code42.com or *.gov.code42.com domain.Revision history
The table below lists previous updates to this page. To learn more about IP address and network port updates, go to https://success.code42.com/announcements.
| Date | Updates |
|---|---|
| August 12, 2020 | Added a note that IP address range 149.5.44.0/24 is retired. |
| June 3, 2020 | Revised the Code42 IP address usage details for each Code42 cloud environment. |
| May 8, 2020 | Noted that IP addresses are scheduled to be updated August 11, 2020. For more information, see IP address updates. |
| March 12, 2020 | Added details for the Code42 federal environment. |
| January 7, 2020 | Added an attention box stating that port 4282 is no longer supported. |
| March 13, 2019 |
|