If your organization has strict network security settings, some Go1 features may not load correctly. This guide lists the domains your IT team needs to allow through your firewall or proxy.
Before you begin
Share this article with your IT or network security team. They will need firewall or proxy admin access to make these changes.
Required domains
These domains are required for all Go1 users.
Go1 content player
Domain | Purpose |
| Core Go1 platform |
| Go1 platform (legacy) |
| Static assets |
| SCORM content delivery |
| Go1 API |
| Embedded content |
| Fonts |
| Media assets |
| Media API |
| Video content |
| Video streaming |
Note: If your organization uses a specific Go1 portal URL, you can replace *.mygo1.com with just your portal domain — for example, yourorganization.mygo1.com.
Go1 platform
Domain | Purpose |
| Text editor |
| Real-time features |
| Content delivery |
Optional domains
Only allow these domains if your organization uses the relevant features.
Payments
Required if your organization processes payments through Go1.
Domain | Purpose |
| Stripe payments |
| Stripe payments |
Single sign-on (SSO) with SAML
Required if your organization uses SAML-based SSO.
Domain | Purpose |
| Auth0 authentication |
Analytics and platform services
Domain | Purpose |
| In-platform live chat support |
Google Analytics | |
| Internal Go1 services |
| Go1 analytics service |
Still having issues?
If you've allowed these domains and are still experiencing problems with specific course content, the issue may be with a content provider's domain.
Learn how to identify content provider domains to allowlist using Chrome developer tools.