> ## Documentation Index
> Fetch the complete documentation index at: https://docs.truu.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Network and allowlists

> Hosts and ports TruU IDV uses: what end users, admins, and your systems connect to, what TruU calls outbound, TLS requirements, and what to allowlist when SSL inspection breaks camera streams or vendor SDKs.

This page is for the network or proxy administrator preparing a rollout. When you finish, you have the allowlist entries for your egress proxy and managed browser settings, and you can confirm that nothing needs to be opened inbound.

## Summary

* All connections are outbound from your side, over TLS on port 443.
* TruU makes no inbound connection to your network. There is nothing to open on a firewall, and no agent or relay to install for the directory, ServiceNow, or storage connections.
* On-premises directories are not connected directly.

## Your side: who connects where

| Who | Host | Port | Used for |
| - | - | - | - |
| End users | `verify.truu.ai` | 443 | The verification page opened from a link |
| End users | `agent.truu.ai` | 443 | Session calls made by the verification page |
| End users | Proofing vendor hosts (see below) | 443 | Document and selfie capture through the vendor's SDK, Proofing factor only |
| End users | AWS Rekognition streaming endpoints | 443 | Streamed camera video for liveness, Face factor only |
| Admins and agents | `idv.truu.ai` | 443 | IDV Console |
| Admins and agents | `verify.truu.ai` | 443 | help desk app |
| Admins and agents | `agent.truu.ai` | 443 | Console API calls |
| Admins using Enterprise SSO | Your identity provider | 443 | Console sign-in |
| Your systems | `agent.truu.ai` | 443 | API, the ServiceNow app, Passwordless pairing |

End users on phones usually complete verification off your network. The entries above matter for desktop users behind a corporate proxy and for kiosks and shared workstations.

## TruU's side: what TruU calls outbound

You do not need to open anything for these, but a reviewer will ask, and some destinations are yours.

| Destination | Hosts | When |
| - | - | - |
| Microsoft Entra ID | `login.microsoftonline.com`, `graph.microsoft.com` | Directory reads at verification time; TAP issuance when the Windows TAP connector is on |
| Your ServiceNow instance | `<your-instance>.service-now.com` | Event push for the ServiceNow connector |
| Your storage | Your Amazon S3 or Azure Blob endpoint | Writes of decision records and face references when Your stores is configured |
| Proofing vendors | The vendor's API host | Starting checks and reading outcomes for the Proofing factor |
| AWS Rekognition | TruU's AWS account | Face comparison and liveness results |
| SMS and email delivery | Twilio, Customer.io | Link and one-time code delivery |

TruU only ever calls hosts ending in the domains above. If your storage endpoint or ServiceNow instance sits behind an IP allowlist, contact support.

## Proofing vendor hosts

The Proofing factor loads the vendor's SDK in the user's browser. Allowlist the vendor you use.

| Vendor | Allowlist |
| - | - |
| Integrated provider (Didit) | `*.didit.me` |
| Persona | `*.withpersona.com` |
| PingOne Verify | Your PingOne environment's region host, `*.pingone.com`, `*.pingone.eu`, `*.pingone.asia`, or `*.pingone.ca` |
| Entrust | `*.onfido.com` |

## TLS and SSL inspection

All traffic is TLS. The verification page, consoles, and API serve current certificates from public authorities; no private CA is required.

> [!WARNING]
>
> SSL inspection breaks camera streams and vendor SDKs. Liveness streams video from the browser to AWS Rekognition, and proofing SDKs open their own connections to the vendor. Both validate the server certificate in ways an inspecting proxy cannot satisfy. Symptoms: the camera preview never starts, the Face step loops on "move closer" or "move further", or the Proofing step fails before the document is captured.

Fix: bypass inspection for `verify.truu.ai`, `agent.truu.ai`, the AWS Rekognition streaming endpoints, and the proofing vendor hosts above. If you cannot change the proxy configuration, direct desktop users to the phone handoff: the verification page shows a QR code, and the phone completes the camera steps off the corporate network.

## Lock screen and kiosk notes

* Camera permission is not available on the Windows lock screen. Users there complete the camera steps on their phone through the QR handoff.
* Kiosks and shared workstations with a locked-down browser need `verify.truu.ai`, `agent.truu.ai`, and the camera-related hosts above, plus camera permission pre-granted for `verify.truu.ai`.

## Checklist

**1. Allow the TruU hosts**

`idv.truu.ai`, `verify.truu.ai`, `agent.truu.ai` on 443.

**2. Allow the camera hosts for the factors you use**

AWS Rekognition streaming endpoints for Face; the vendor hosts for Proofing.

**3. Exclude those hosts from SSL inspection**

Or plan on phone handoff for desktop users.

**4. Confirm nothing inbound**

Directory, ServiceNow, and storage are all outbound from TruU. If a reviewer asks for an inbound rule, the answer is none.

**5. Test from a managed desktop**

Open a sample-mode verification link on a corporate laptop behind the proxy and complete a Face step. If the camera does not start, see [Troubleshooting](https://docs.truu.ai/idv/resources/troubleshooting.md).

## Related pages

> [card] [Product security](https://docs.truu.ai/idv/security/overview.md)
>
> What TruU calls and what calls TruU, and why.

> [card] [Data flow and custody](https://docs.truu.ai/idv/security/data-handling.md#how-data-moves)
>
> What travels on each of these connections.

> [card] [Troubleshooting](https://docs.truu.ai/idv/resources/troubleshooting.md)
>
> Camera and delivery symptoms.

> [card] [Microsoft Entra ID](https://docs.truu.ai/idv/connect/directory/entra-id.md)
>
> The directory connection in detail.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.