The VALD product suite, including VALD Hub and all system applications, relies on connectivity to specific domains and endpoints for its online functionality.
If your organization applies restrictive firewall or web-filtering policies, you may need to add the following VALD domains to an allowlist to ensure all platforms function correctly.
Looking for GymAware-specific domains and endpoints? Refer to our recommended GymAware allowlist.
Recommended allowlist additions
| Purpose | Destination | Port |
| Required: Backend APIs | valdperformance.com | TCP 443 |
| Required: Backend APIs | *.valdperformance.com | TCP 443 |
| Required: Authentication and identity | auth.prd.vald.com | TCP 443 |
| Required: Backend APIs | vald.com | TCP 443 |
| Required: Backend APIs | *.vald.com | TCP 443 |
| Required: Authentication and identity | vald-prd.eu.webtask.run | TCP 443 |
| Optional: Diagnostic logging | log1.valdperformance.com | TCP 443 |
Product and region-specific domains
If your VALD tenant is subject to data residency controls, you may choose to explicitly add only the endpoints for your data region to your network allowlist.
Note: Authentication Services are hosted exclusively in the Auth0 public cloud EU-2 data sub-region. If you choose to implement a region-specific allowlist, you therefore must also include `auth.prd.vald.com`.
Blocking access to the EU region will disrupt authentication services.
Comments
0 comments
Please sign in to leave a comment.