Managing Network Whitelisting with Axon Cloud Services

Customers that have implemented network-based controls to manage internet access, your users', clients', or devices' access may be blocked from connecting with Axon Cloud Services unless specific network configurations are made. The network based configuration must support all connectivity that is needed to access to Axon Cloud Services (including web application access), Axon Client Application (including mobile, desktop, offload servers, Interview Room, Commander and MDT applications) connectivity, and Axon Devices (including the Axon Dock) connectivity. 

To enable this internet-based connectivity, Axon recommends that customers whitelist based upon fully qualified domain names (FQDN). This approach will aid in ensuring continued connectivity to Axon Cloud Services.

FQDN Whitelisting Requirements

For web application and client access to Axon Cloud Services, whitelist the following:

• <customer>.<regioncode>.evidence.com (for login and Evidence.com user access)
• login.<regioncode>.evidence.com (for forgot agency URL workflow)
• share.<regioncode>.evidence.com (for share links)
• api.<regioncode>.evidence.com (for Partner API connectivity)
• fleet.<regioncode>.evidence.com (for Fleet login)
• sentry.<regioncode>.evidence.com (for client error reporting)
• api.mapbox.com (for map rendering and geocoding functionality)
• api.mixpanel.com (for product insights and user analytics)

Customer URLs conform to the <customer>.<regioncode>.evidence.com scheme with the exception of US 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. Refer to the Region Codes and IP Addresses table for the region code. 

Example URLs: 

• For the non-Federal 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.eu.evidence.com

For the Axon Dock, whitelist only the following:

• <customer>.<regioncode>.evidence.com
• Ensure outbound port 53 (UDP) access from the Axon Dock, see the Axon Dock - Network Configuration article for additional details

For the Axon Body 3 Dock, whitelist only the following:

• <customer>.<regioncode>.evidence.com
• Whitelist port 443 (TCP) for outgoing traffic to your agency’s Axon Evidence.com instance. This is used to send video and data files to Axon Evidence.com using the HTTPS protocol. 
• Whitelist port 80 for time synchronization. 

 For Axon Aware Livestreaming, whitelist the following:

• axon-aware-streaming-relay.<regioncode>.evidence.com 
• Whitelist port 443 (TCP) access on the user network

For Access to Axon Help Documentation and Support, whitelist the following:

• public.evidence.com (for access to Axon Release Notes and User Guides)
• help.axon.com (for access to Axon Help Center)
• communities.taser.com (for access to Axon technical and customer support)

When using Axon Mobile Applications from within your network, the following additional whitelists are recommended, but optional:

• crashlytics.com (for mobile application crash reporting to Axon)
• fabric.io (for mobile application crash reporting to Axon)

IP Whitelisting Requirements

Customers choosing to manage internet access based upon IP must ensure IP whitelisting is implemented to enable connectivity to Axon Cloud Services' IP addresses. Axon Cloud Services' IP addresses are subject to change and customers must ensure to periodically review this page and reconcile the IP Addresses listing into their whitelisting. If the IP whitelisting is not maintained, customers should expect service degradation and outages until connectivity is re-established to Axon Cloud Services.

Prior to removing IPs from usage, Axon will communicate to customers of the upcoming depreciation of IP addresses. Customers are solely responsible in taking action to ensure continued connectivity to Axon Cloud Services for applicable customer users, clients, and devices.

Even with proper IP whitelisting, some functionality may be negatively impacted by using IP based whitelisting. Axon recommends to whitelist based on FQDN where possible.

For web application, client, and device access to Axon Cloud Services, whitelist outbound on Port (443) to the Region Specific IP Addresses shown below to match your deployed region*.

Additionally, for the Axon Dock, ensure outbound Port 53 (UDP) is enabled, see the Axon Dock - Network Configuration article for additional details.

Region Codes and IP Addresses 

* Customer URLs conform to the <customer>.<regioncode>.evidence.com scheme with the exception of US 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

** See Axon Cloud Services Privacy Policy for information on Axon Cloud Services data center locations.

*** Axon Cloud Services's IPs are subject to change and customers must ensure to periodically review this page and reconcile the IP listing into their whitelisting.

Change Log

The following table lists the changes to this article.