Axon IP addresses and network requirements
If you implemented network-based controls to manage internet access, you might find that your user, client, or device access won't connect with Axon Cloud Services without specific network configurations. The network-based configuration must support all connectivity required to access Axon Cloud Services (including web application access), Axon Client Application (including mobile, desktop, offload servers, Interview Room, Evidence Local, and MDT applications), and Axon Devices (including the Axon Dock).
To enable this internet-based connectivity, set your allowed list based on Fully Qualified Domain Names (FQDN). Some services and devices might require open ports or IP address allowed lists.
FQDN allowlist requirements
Axon Cloud Services use the following regional domains:
| Region | Domain Name |
|---|---|
| Australia/Southeast Asia | *.au.evidence.com
*.au.axon.com |
| United States Government/Law Enforcement | *.evidence.com
*.usa.axon.com |
| United States Federal | *.us.evidence.com
*.axonfed.us |
| Commercial/Enterprise | *.ent.evidence.com
*.ent.axon.com |
| Canada | *.ca.evidence.com
*.ca.axon.com |
| European Union (legacy) | *.eu.evidence.com
*.eu.axon.com |
| European Union | *.eur.evidence.com
*.eur.axon.com |
| Latin America/South America | *.la.evidence.com
*.la.axon.com |
| United Kingdom | *.uk.evidence.com
*.uk.axon.com |
| Germany | *.de.evidence.com
*.de.axon.com |
Customer URLs conform to the <customer>.<regioncode>.evidence.com scheme with the exception of US Government/Law Enforcement customers, where the scheme may exclude the region code and is <customer>.evidence.com. US Federal customers conform to the scheme <customer>.us.evidence.com or <customer>.axonfed.us. Refer to the Region Codes and IP Addresses table
Example URLs
- For the US Government/Law Enforcement customer Axon Police Department in Arizona (<customer> = axonpdaz) the URL would be: axonpdaz.evidence.com
- For the Axon Police Department in Australia (<customer> = axonpd) the URL would be: axonpd.au.evidence.com
- For the Axon Police Department in France (<customer> = axonpd) the URL would be: axonpd.eur.evidence.com
Common subdomains used by Axon Evidence
Axon Evidence uses multiple subdomains within each region to separate and secure certain key services and traffic.
The following table provides examples of the types of traffic you might encounter within the Axon Evidence domain and their associated use cases. This list only contains examples and is not exhaustive. As Axon's system and features evolve, the list of subdomains may change. To avoid outages, we advise against restricting traffic only to these subdomains.
| Subdomain | Use |
|---|---|
| id | Axon login and authentication |
| share | Axon Case and Evidence sharing |
| fleet | Fleet login and authentication |
| api | Core Axon APIs |
| register | Used for Axon Dock and Camera registration |
| axon-aware-streaming-relay | Axon Respond livestreaming |
| livestream | Axon Respond livestreaming |
| upload* | Used for evidence and file upload |
| *.upload | Used for evidence and file upload, split by source |
| telemetry | Client-side error reporting |
| files | Used for file serving |
| status | To monitor the operational status of various Axon systems |
Additional external resources used by Axon Cloud Services
To get the full Axon experience, allow access to the following domains in your firewall configuration.
| Domain | Protocol/Port | Use Case |
|---|---|---|
| *.arcgis.com | HTTPS (TCP 443) | For map tiles and GIS data used within Axon apps retrieved from Axon's GIS provider |
| *.crashlytics.com | HTTPS (TCP 443) | Mobile application crash reporting to Axon |
| public.evidence.com | HTTP/HTTPS (TCP 80/443) | Axon Evidence Release Notes/User Guide |
| my.axon.com | HTTP/HTTPS (TCP 80/443) | My Axon Resource Center |
| communities.taser.com | HTTP/HTTPS (TCP 80/443) | Axon Technical and Customer Support forums |
Additional external resources used by Axon Fusus
For resources used by Axon Fusus, see the "Axon Fusus US Trusted Sites List" in the Axon Trust Center.
Additional external resources used by Axon Academy
For Axon Academy, you will need to allow the USA Virginia IPs for Docebo (third-party site).
US Federal customers will also need to allow the IP ranges for US Government/Law Enforcement in the Region codes and IP addresses table below.
Open ports
For the Axon dock:
- For Axon Body 3 and later, see Network configuration - Body 3+ Docks
- For Axon Body 2, see Network configuration - Legacy Dock
For Axon Respond Livestreaming, allow the following:
- Port 443 (TCP) access on the user network
- UDP 3478 for Fleet or body camera streaming to Axon cloud services
IP allowlist requirements
If you manage internet access based on IP, you must make sure IP allowlists are implemented to enable connectivity to Axon Cloud Services IP addresses. These addresses are subject to change and you must periodically review this page and reconcile the IP Addresses listing into your allowlist. If the IP allowlist is not maintained, you can expect service degradation and outages until connectivity is re-established to Axon Cloud Services.
Axon will send notice prior to removing IPs from use. You are solely responsible for taking action to ensure continued connectivity to Axon Cloud Services for applicable customer users, clients, and devices.
Even with a proper IP allowlist, some functionality may be negatively affected by using IP-based listing. Axon recommends setting your allowlist based on FQDN where possible.
For web application, client, and device access to Axon Cloud Services, allow outbound on Port (443) to the Region-specific IP addresses shown below to match your deployed region*.
Global IP addresses
Certain IP addresses provide global services that direct users to their specific region. These IP addresses are listed below. Axon recommends allowing these addresses in all firewalls regardless of the region.
-
Economic Area: Global
- Region-Specific IP Address: 52.227.251.93
- Ensure continuous service by adding these additional blocks to your network allowlist:
64.40.128.0/20
2607:9240::/32
Region codes and IP addresses
| Region Code | Economic Area** | Region-Specific IP Addresses*** |
|---|---|---|
| AU | Australia/Southeast Asia | 20.36.34.147
20.36.35.174 20.36.39.214 20.36.67.249 20.37.47.79 20.37.47.86 20.39.99.96/28 20.53.24.224/28 20.70.14.192 20.70.14.193 IPv6: 2603:1010:300::200/120 |
| CA | Canada | 20.200.97.192/28
40.86.228.88 52.139.87.160/28 52.233.5.203 52.228.43.132 52.228.43.144 52.228.45.77 52.235.42.72 40.85.244.71 40.85.253.137 40.86.228.88 IPv6: 2603:1030:f02:3::100/120 |
| DE | Germany | 9.141.13.160/28 2603:1020:c01:2::300/120 (IPv6) 20.79.129.51/32 20.113.207.193/32 |
| EU | European Union (legacy) | 54.246.136.170
54.246.136.171 54.246.136.172 54.246.136.173 3.248.2.170 108.128.24.31 52.236.20.128/28 IPv6: 2603:1020:2:3::500/120 |
| EUR | European Union | 20.76.106.192/28
20.93.109.80/28 13.93.3.108 13.93.7.228 IPv6: 2603:1020:201:f::1a0/124 2603:1020:201:10::200/120 |
| LA | Latin America/South America | 20.201.27.240/28
191.233.171.0/28 191.239.248.108 191.239.249.95 IPv6: 2603:1050:1:5::100/120 |
| UK | United Kingdom | 20.58.6.199
51.140.2.33 51.140.3.217 52.142.154.208/28 51.143.249.112/28 52.151.85.29 51.140.84.175 IPv6: 2603:1020:700:3::100/120 |
| US | United States Government/Law Enforcement |
52.227.170.136
|
| US | United States (Federal Region) |
52.227.168.125
62.10.122.146 |
| ENT | Commercial/Enterprise | 52.250.94.128/28
52.250.94.140 65.52.116.144/28 13.77.150.90 52.183.44.115 IPv6: 2603:1030:c02:9::100/120 |
* Customer URLs conform to the <customer>.<regioncode>.evidence.com scheme with the exception of US Government/Law Enforcement customers where the scheme can exclude the region code and is <customer>.evidence.com. US Federal customers conform to the scheme <customer>.us.evidence.com.
** See Axon Cloud Services Privacy Policy for information on Axon Cloud Services data center locations.
*** Axon Cloud Service's IPs are subject to change and you must periodically review this page and reconcile the IP listing into your allowlist.
VR IP addresses
Information about VR IP address management in your network allowlist, see Manage Axon VR IP addresses in network allowed lists.
