Honeit Network Requirements and Recommendations

Call connectivity requirements for Honeit voice, video, screen sharing, and real-time interview sessions.

To ensure a smooth Honeit experience, your company’s network and IT team should allow the required ports, domains, protocols, and IP ranges listed below.

This article is intended for IT professionals or teams with basic networking knowledge. If needed, please send this article to your IT or network administration team.

For help, contact support@honeit.com.

Before conducting important Honeit calls, please review the following checklist:

Honeit uses browser-based real-time communication services for voice, video, and screen sharing.

Your firewall should allow outbound TCP and UDP traffic from user browsers to the services below, plus established return traffic.

You should not need to allow unsolicited inbound traffic to user devices.

If your organization uses a restrictive firewall, VPN, proxy, SSL inspection, DNS filtering, or endpoint security product, please make sure the domains, ports, and IP ranges below are allowed.

Avoid SSL/deep packet inspection for real-time media domains, especially:

SSL inspection can interfere with secure WebSocket signaling, audio, video, and screen sharing.

Allow outbound HTTPS traffic on TCP port 443 to:

Honeit requires browser access to the application, authentication flow, scheduling pages, interview pages, diagnostics pages, and supporting assets.

Used for:

Allow outbound UDP traffic:

The browser or device will select an available source port from the ephemeral port range. On most machines, this means a source port between 1024 and 65535.

Allow outbound TCP 443 traffic to the following domains:

These domains are required for Honeit voice signaling, media setup, browser-based call functionality, and supporting call assets.

If your network already allows *.twilio.com, the specific signaling domains above should generally be covered.

For strict domain allowlisting, also allow the following regional signaling domains:

For older browser voice infrastructure, the following legacy signaling domains may also be required by some environments:

Used for:

Allow outbound access to:

Allow the following outbound ports:

For the best experience, UDP traffic should be allowed.

If UDP is blocked or heavily restricted, video and screen sharing may fail, degrade, or fall back to less reliable relay behavior.

Allow outbound traffic to the following relay IPs for real-time media connectivity:

No customer network changes are required for normal Honeit browser-based calls, interviews, video sessions, or screen sharing based on webhook IPs.

Webhook IP allowlisting is only relevant when an organization is directly receiving webhook requests from Honeit’s real-time communication infrastructure on its own server endpoint.

For normal Honeit customers, Honeit handles server-side webhook processing. End users and customer IT teams generally do not need to allowlist webhook NAT gateway IPs for browser call connectivity.

The following targets are recommended for reliable voice/audio quality:

Lower latency is better. Round-trip latency below 100 ms is ideal when possible, but below 200 ms is the recommended target for reliable voice quality.

Video and screen sharing require more bandwidth than voice-only calls.

Actual bandwidth usage depends on:

For important interviews, we recommend running the Honeit Network Test before the call, especially on corporate networks, VPNs, hotel WiFi, shared office networks, or restricted networks.

Honeit requires WebSocket support for real-time signaling and call control.

Allow outbound secure WebSocket traffic:

If your firewall or proxy blocks secure WebSocket traffic, Honeit calls may fail to connect or may disconnect unexpectedly.

Corporate VPNs, proxies, endpoint security tools, antivirus software, DNS filters, and SSL inspection tools can interfere with real-time browser-based audio and video.

If users experience call failures, one-way audio, no video, frozen video, screen share failure, or frequent disconnects, check whether any of the following are active:

For the best experience, avoid routing real-time Honeit media traffic through restrictive VPNs or proxies when possible.

Use the latest version of a modern supported browser.

Recommended browsers:

Chrome or Firefox is recommended for the best Honeit experience.

Mobile browsers may have limitations with background call connectivity, device permissions, call interruption handling, camera access, microphone access, and screen sharing. For best results, use a desktop or laptop browser.

Before joining a Honeit call, confirm that the browser has permission to access:

For the most reliable experience:

For best call quality:

For the best audio quality:

Bluetooth headsets can behave differently depending on the device, operating system, browser, battery level, and Bluetooth driver.

Before a Honeit call:

If Honeit calls are not working correctly, the issue is often related to one of the following:

If issues continue, run the Honeit Network Test and send the results to support@honeit.com.

At minimum, customer networks should allow the following outbound traffic.

Allow outbound UDP media traffic:

The browser or device will select an available source port from the ephemeral port range. On most machines, this means a source port between `1024` and `65535`.

Allow outbound TCP signaling traffic:

For strict domain allowlisting, also include the regional voice signaling domains and legacy signaling domains listed in the Voice Signaling Requirements section above.

Allow outbound access to:

Allow outbound TCP traffic:

Allow outbound UDP traffic:

Allow outbound traffic to the following relay IPs:

If your IT team has questions or if a user is having trouble connecting to a Honeit call, please contact:

support@honeit.com

When contacting support, please include: