# Allowing Venzeo through your company network

> The browsers, domains and email senders your IT team must allow so the Venzeo™ web and mobile apps work on your network.

Source: https://help.venzeo.com/en/article/it-administrator-instructions
Language: en
Updated: 2026-10-09

This page is for the IT team that manages Venzeo™ access through your company's browsers, firewall, proxy and email server.

## Browsers

- Use a current version of Google Chrome, Microsoft Edge, Mozilla Firefox or Apple Safari.
- On 9 October 2026, the minimum versions were Chrome 111, Edge 111, Firefox 114 and Safari 16.4 (on iPhone and iPad: iOS 16.4).
- Older browsers are not supported. The web app may not load in them, or parts of it may not work.

## Domains for the web app

Allow HTTPS (TCP port 443) and secure WebSocket (`wss://`) traffic to these domains and all their subdomains. Make sure your internet provider does not block them either.

- `*.venzeo.com`: the Venzeo web app, the API (for example `api-internal-eu.venzeo.com`), sign-in (`auth.venzeo.com`) and real-time updates over WebSocket
- `*.google.com`, `*.googleapis.com`, `*.gstatic.com`: sign-in, sign-in with Google, and bot protection (Google reCAPTCHA) on the sign-in and registration pages
- `login.microsoftonline.com`: sign-in with a Microsoft or Office 365 account
- `*.amazonaws.com`: uploading and viewing photos and files (Amazon S3)
- `*.mapbox.com`, `*.arcgis.com`, `*.tile.openstreetmap.org`: maps and address search
- `*.sentry.io`: error reporting
- `*.fullstory.com`: usage analytics
- `*.statuspage.io`: service status

## Domains for the mobile app

Phones with the Venzeo mobile app need the same `*.venzeo.com` and `*.amazonaws.com` access over company Wi-Fi, plus:

- `venzeo-alternate.app.link`: device invitation links
- `*.googleapis.com`: Google Firebase services (app configuration, push notifications, crash reports) and the Google Play integrity check on Android
- `*.soniox.com`: dictating text by voice in a report
- `*.solarwinds.com`: app diagnostics that help us solve problems on a device

Push notifications also need the ports that Google and Apple require: TCP 5228–5230 on Android ([Android Enterprise network requirements](https://support.google.com/work/android/answer/10513641)) and `*.push.apple.com` on TCP 5223 on iPhone ([Apple products on enterprise networks](https://support.apple.com/en-us/101555)).

For phone models and operating systems, see [Mobile device requirements (Android and iOS)](https://help.venzeo.com/en/article/requirements-of-the-mobile-device-android-and-ios).

## Check that Venzeo is reachable

To test HTTPS access from a computer on your network, run this command in a terminal (Windows 10 and later, macOS and Linux include `curl`):

`curl https://api-internal-eu.venzeo.com/api/ping`

The command prints `pong` when the connection works. Any other answer, a certificate error or a timeout means that a firewall, proxy or TLS inspection is blocking Venzeo.

> **Note:** `ping`, `tracert` and `traceroute` do not prove that Venzeo works. They use ICMP or UDP, while Venzeo uses HTTPS on TCP port 443.

## Email senders

Sign-in links and notifications arrive by email. Add these senders to your email server's allow list so that the emails do not end up in spam:

- `*@venzeo.com`
- `*@auth.venzeo.com`
- `*@notification.venzeo.com`

Checked on 9 October 2026 against the current Venzeo web app and mobile app.