Skip to main content

What domains should we whitelist in our network to ensure access to Ingenious?

This article will list the URLs that may need to be whitelisted in order to ensure access to them.

T
Written by Taylor Vickhammer
Updated over a week ago

Overview

If your organization restricts access to certain websites, you may need to update the network's allowlist to ensure full access. ​For an optimal experience, you may consider adding these domains to your approved list.


Domains

To ensure all connections (web app, API, integrations, and training) work correctly, please allow these domains:

*.ingenious.build
*.ingenious.training
ingenious.build


Using wildcard rules (for example, *.ingenious.build) ensures access to all subdomains, while explicitly allowing ingenious.build covers the root domain.


IP Addresses (Regional Entry Points)

Ingenious operates on Google Cloud Platform (GCP) with global load balancing.

This means IP addresses can change dynamically; however, the following are current primary entry points per region and environment:

Environment / Region

Domain

Current IP Address

Notes

Production (US)

ingenious.build

34.54.21.121

Primary entry for US

APAC (Australia)

au.ingenious.build

34.117.30.33

Main AU production environment

APAC (China)

cn.ingenious.build

34.98.97.194

Mainland China region

EMEA (Europe)

eu.ingenious.build

34.149.2.184

Europe region

EMEA (Saudi Arabia)

sa.ingenious.build

34.160.187.89

Middle East region

Training Environment

ingenious.training

34.98.74.132

Primary AU training entry point

⚠️ Important:
Ingenious runs on Google Cloud Platform with dynamic global load balancing.

Static IPs are not supported.

Where possible, whitelist by domain, not IP.


TLS and Security

  • Minimum supported TLS version: 1.2

  • Also supports: TLS 1.3

  • To confirm supported ciphers, you can use:

nmap --script ssl-enum-ciphers -p 443 {your-region}.ingenious.build


​

Did this answer your question?