Hi,
We are integrating FaceIO’s facial authentication into our application, but we are currently facing issues where our corporate firewall is blocking requests to your services. This intermittently prevents users from completing the facial authentication flow.
To ensure reliability and improve our security posture, we would like to confirm the official network requirements for FaceIO. Specifically, could you please provide:
1. The complete list of domains and URLs that must be allowed for FaceIO to function correctly (API, CDN, widget, auxiliary services, etc.).
2. Whether you offer fixed IP addresses or IP ranges that can be safely whitelisted in enterprise environments.
3. If IPs are dynamic due to CDN usage, what is the recommended approach for firewall configuration in restricted corporate networks (e.g., DNS-based allowlisting).
4. Any additional network requirements such as ports, protocols, or TLS considerations.
Our current implementation interacts with:
• api.faceio.net (backend REST API)
• cdn.faceio.net (client-side SDK/widget)
• status.faceio.net (health/status)
However, we want to ensure that no other required endpoints are being blocked.
This information is critical for us to configure our firewall correctly, avoid intermittent failures, and maintain a secure and stable integration.
Thank you in advance for your support.
Best regards,
Danilo Bonfim
[email protected]
FaceIO Firewall Configuration: Required Domains and IPs for Integration
Asked
Modified
Viewed
6292 times
✓ Accepted Solution
Hi Danilo,
Thank you for reaching out regarding the integration of FACEIO’s facial authentication. To ensure reliable operation, please whitelist the following domains:
- widget.faceio.net
- api.faceio.net
- cdn.faceio.net
- ws[1..15].faceio.net
- console.faceio.net
We recommend whitelisting all FACEIO subdomains including the community forum to avoid any potential issues.
If you have any further questions or need additional assistance, feel free to ask.
Best regards,
FACEIO