If your organization restricts network traffic with a firewall, allow the Reality Defender hosts below for the products you use. Most traffic is outbound HTTPS on port 443. RealCall SIPREC integrations also need the additional ports and inbound rules listed in their section.

If you use the Reality Defender web app, allow these hosts.

If the LaunchDarkly hosts are blocked, the web app can’t load your plan’s features, and products show “Upgrade” even when your plan includes them.
​
Media and results are loaded from Amazon S3 through temporary links. If your security policy requires specific hostnames instead of wildcards, contact Reality Defender Support.

All SDK and API traffic, including file uploads, goes to a single host.

Allow the hosts below for the RealCall integrations your organization uses.

Genesys Cloud connects to this host directly, so AudioHook traffic doesn’t pass through your network and you don’t need to add them to your firewall. They’re listed here for reference.

For SIPREC integrations, your Session Border Controller (SBC) connects to the Reality Defender Session Recording Server (RDSRS).

*Both directions are needed when your SBC supports re-INVITE, because RDSRS may open a new connection to send it. If your SBC doesn’t support re-INVITE, SBC to RDSRS is enough.

These hostnames resolve to addresses that can change, and the SIP and media proxies use different addresses. Your Reality Defender account team will provide the current IP addresses to add to the allowlist. If you connect through an IPSec VPN or private peering, your account team will provide a dedicated hostname and IP range instead. For details, see RealCall SIPREC Integration: Session Recording Server (RDSRS).

Your Teams client contacts only one Reality Defender host. Meeting media flows between Microsoft and Reality Defender and doesn’t pass through your network.