SkieWhat if the school Wi-Fi blocks the Skie web filter?
Skie detects it and flags it. Some networks block the port the encrypted filter needs, so the tablet falls back to the network's own DNS and the dashboard shows the problem. A network check wizard tests the school network and gives a ready message you can send to school IT to allow the filter.
The web filter in Skie is a filtering DNS locked on the device. That is why it follows the tablet from school Wi-Fi to home Wi-Fi to mobile data. On most networks it just works. On some, especially managed corporate or campus networks, the firewall blocks the encrypted DNS port.
When that happens the device uses the network's DNS so that the internet still works, and the dashboard flags that the filter is not in force on that network. You see it as a flag and not a silent failure, which is the point. Nothing is hidden from the admin.
The fix is usually an allowance from whoever runs the network. The network check wizard in Skie tests the school Wi-Fi and, if there is a block, produces a ready message for school IT explaining exactly what to allow. That saves the back and forth that often takes days in a school where the network team is a separate vendor.
A different DNS filter can be used if the school prefers one. The default for organisations without their own is CleanBrowsing Family. An organisation or group filter overrides it, and the owner curates a list of filters that organisation admins choose from.
Tablets are also protected from some routes around the filter. VPN apps and setup are blocked, Private DNS setting is blocked and a bypass of the filter is reported. Other safeguards such as app list control still work on any network.
Securly and GoGuardian are school web filtering products. Skie's filter is a DNS locked on the device, which is why it travels, but it still needs the network to permit its DNS.
A practical tip: run the network check in the room where you will actually use the tablets, not at the front office.