Skillet requires access to a specific set of domains to function properly within your organization’s network. If your company uses a firewall, web proxy, or other network filtering, your IT team should allow (“whitelist” or “safelist”) the domains below to ensure that Skillet works without interruption.
Skillet is built and backed by Wayground (formerly Quizizz) and runs on the same trusted infrastructure. As a result, Skillet relies not only on its own skillet.io domains but also on certain wayground.com and quizizz.com domains for parts of its functionality. All of these are listed below.
Step 1: Safelist the Skillet domains
Allow the following domains through your firewall for both HTTP and HTTPS traffic. We recommend using the wildcard entries below, which cover all current and future subdomains automatically.
Step 2: Safelist supporting service domains
Skillet also relies on the following domains. These must be allowed for the application to load and sign you in correctly.
Why are quizizz.com and wayground.com required?
Because Skillet is built and backed by Wayground (formerly Quizizz), it shares their infrastructure. Media and asset files (images and JavaScript/CSS bundles) are delivered from quizizz.com, and authentication and single sign-on (SSO) are routed through wayground.com.
If your network doesn’t support wildcards
Some networks can’t use wildcard (*) rules and require an explicit list of individual domains. Because Skillet’s infrastructure changes over time, we don’t publish a static list of every host — an outdated list can cause parts of the product to silently break.
If you need an explicit, non-wildcard list of domains to safelist, please contact our team at support@skillet.io and we’ll provide the latest current list for your environment.
Step 3: Verify browser and network compatibility
Confirm that the following are supported and not blocked on devices using Skillet:
WebSockets are enabled on port 443 (required for real-time connections)
Cookies are enabled for skillet.io and all of its subdomains
JavaScript, HTML5, CSS3, and Local Storage are enabled in the browser
Recommended browsers:
Google Chrome (recommended)
Microsoft Edge
Safari
Firefox
A note on CDNs and IP-based filtering
Most networks filter traffic by domain name, in which case allowing the domains above is sufficient — even though some of them are served through content delivery networks (CDNs). You do not normally need to safelist the underlying CDN hosts separately.
If your network filters by destination IP address rather than by domain name (common in stricter enterprise environments), please contact support@skillet.io for guidance specific to your setup.
Need more help?
If issues persist after updating your firewall settings, or your IT team needs additional information, please contact us at support@skillet.io.