trio.so
School

Web Filter for Schools: How to Choose One That Covers Every Device

How a web filter for schools works: network, DNS and device layers, what CIPA requires, how students bypass filters, and what to check before you buy.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on

A web filter for schools blocks harmful and distracting websites on the devices students use, at school and, for take-home devices, at home. Covering every device can take more than one layer: a network or DNS filter for everything on the school network, and a filter on the device itself for iPads, laptops and Chromebooks that leave the building. This guide explains the layers, what the Children's Internet Protection Act (CIPA) asks of a filter, how students get around filters, and what to check before you buy.

Why schools filter the web

US schools that take E-Rate discounts for internet access or internal connections must run a filter that blocks pictures that are obscene, child pornography, or (for minors) harmful to minors. That is a condition of CIPA, and the school certifies compliance each funding year, on FCC Form 486 or 479 today and on Form 471 from funding year 2028 (USAC, CIPA page, read 10 Nov 2026). Our guide to CIPA compliance covers the full list of requirements.

CIPA sets the floor, not the ceiling. The school or local community decides what else counts as inappropriate, so a school may also block categories such as gaming, social media during class time, proxies and VPN services. Our post on why schools restrict websites explains the reasons from the student side.

The layers of a school web filter

Filters work at different points between the student and the website. Each layer covers something the others miss.

LayerHow it worksCovers devices off campusMain gap
Network or firewall filterInspects traffic on the school network, often with category lists and HTTPS inspectionNoStops working when the device leaves the network
DNS filterRefuses to resolve blocked domains for devices that use the school's DNS serversOnly if the device is set to use that DNS everywhereSees domains, not full pages; bypassed if the device uses another DNS service
Device-level filterA policy or agent on the device applies the rules wherever it connectsYesNeeds managed devices and support for each operating system
Browser extensionFilters inside one browser, common on ChromebooksYes, in that browserOther browsers and apps are not covered

One workable setup is a network or DNS filter as the base for everything on campus, plus a device-level filter for every school-owned device that goes home.

The take-home device gap

A filter that lives on the school firewall protects students only while they are on the school network. Once a school iPad or laptop joins a home Wi-Fi network or a phone hotspot, that filter no longer sees its traffic. In 1:1 programs, those devices spend evenings and weekends off the school network.

Closing the gap means putting the rules on the device. That takes managed devices: school-owned iPads enrolled and supervised, laptops enrolled in device management, and a filter that each platform supports. If you are starting a program, our guide to starting a 1:1 device program covers enrollment.

How students get around filters

No filter is perfect. Knowing the common workarounds helps you choose settings that close them.

  • VPNs and proxy sites. Block the VPN and proxy category in the filter, and stop students from installing VPN apps on managed devices.
  • Other DNS services. A device set to a public DNS resolver, or a browser sending DNS over HTTPS to its own resolver, skips a DNS filter. Lock DNS settings on managed devices, and block known public resolvers at the firewall.
  • Personal hotspots and home networks. Only rules set on the device, such as a device-level filter or locked DNS settings, cover these.
  • Other browsers or apps. A browser extension covers one browser. Restrict which browsers and apps can be installed.
  • Personal devices. A student's own phone on mobile data is outside the school's control. Policy and supervision cover this, not the filter.

What to check before you choose a web filter

  1. Platform coverage. List every device type students use (Chromebooks, iPads, Windows and Mac laptops) and confirm the filter covers each, on and off campus.
  2. CIPA categories and local categories. The three CIPA categories must be blocked; check that you can add your own categories and lists.
  3. Per-group policies. Younger students often need stricter rules than high school students, and staff need different rules again.
  4. HTTPS handling. Ask how the filter deals with encrypted traffic and what it needs installed on devices to do so.
  5. Reporting. USAC asks schools to keep reports showing the filter was installed and working, for at least 10 years after the funding year. Check what reports the filter produces and how you can export them.
  6. Overblocking and unblock requests. Teachers will need sites unblocked for lessons. Check how fast a request can be approved.
  7. Adult override. CIPA lets an authorized person disable the filter for an adult doing bona fide research. Check that the filter supports it.
  8. Student privacy. Ask what browsing data the vendor stores, where, and for how long. CIPA does not require keeping browsing history (FCC).

If you need a starting list of sites, our list of websites blocked by schools comes with a free download of over 11,000 domains in three strictness levels, ready to import.

Free template: write the filter into your internet safety policy

CIPA expects the filter to be part of an internet safety policy that went through public notice and a hearing or meeting. Our template has sample wording for what the filter blocks, which devices it covers at school and at home, and how an adult gets it switched off for research.

The filter pages of the School Internet Safety Policy (CIPA) template: blocked categories, device coverage and the adult disabling procedure
  • Word policy with fillable fields and a filled-in example district
  • PDF of the same policy, ready for the board packet
  • Excel checklist of the records USAC asks for, with a keep-until date for each funding year and a log of filter disable requests

Filtering school devices with trio.so

trio.so manages school devices on Windows, macOS, Linux, iOS/iPadOS and Android from one console, and it covers the device-level layer on iPads and iPhones. On supervised iPads and iPhones it applies a web content filter policy using Apple's built-in allow and deny lists, so the rules go with the device to school, home or a hotspot. On Macs it can connect a third-party filter plugin. On Apple and Android devices it can also set encrypted DNS settings that point the device at your district's DNS filter, if that filter offers an encrypted DNS address. That is a DNS setting, not a filter of its own. Cover Windows and Linux laptops with a separate filter. ChromeOS support is coming soon.

For records, trio.so shows for each device whether a policy is applied, failed or pending, and keeps an audit trail of policy changes, exportable as CSV or JSON. New iPads from Apple School Manager can arrive supervised with the filter policy already on. Plans start at $5 per device.

Start free trial or Book a demo.

14-day free trial. No credit card required.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Put the filter on the iPad itself

trio.so applies a web content filter to supervised iPads and iPhones, with the allow and deny lists you choose, so students carry the same rules home. Cover laptops and Chromebooks with a network or DNS filter.

Start free trial

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently asked questions

The best one is the one that covers every device type your students use, on and off campus, and blocks the CIPA categories plus your own. A common approach is to combine a network or DNS filter with a filter on take-home devices.

US schools that receive E-Rate discounts for internet access or internal connections must, under CIPA. The filter has to block pictures that are obscene, child pornography, or (for minors) harmful to minors.

A network filter does not. A filter set on the device itself, or a DNS setting locked on the device, keeps working on home Wi-Fi and hotspots.

The usual ways are VPNs, proxy sites, other DNS services, other browsers and personal hotspots. Blocking VPN and proxy categories, locking DNS and app installs on managed devices, and filtering on the device close most of them.

Yes, at the domain level. A DNS filter refuses to look up a blocked domain whether the site uses HTTPS or not, but it cannot see individual pages within an allowed domain.

Related

From the blog

The related industry news, interviews, technologies, and resources.