No device left behind. Each installer below takes under five minutes, works on hardware up to a decade old, and uses the same family filter as the rest of Breaking Chains. If a device lives at home behind the Gateway or a filtered router, it is already covered — these steps make the protection travel with the device.
One tap installs the Breaking Chains filter profile. It encrypts and filters every DNS lookup on Wi-Fi and cellular, so the protection rides along to any network.
Download the profileSame profile as above. iPads from 2018 onward run it natively. If your iPad is older and Settings says the profile "cannot be installed," use the per-network fallback:
Any Android (2013 or newer): we use Google's free, open-source Intra app pointed at the Breaking Chains resolver. This covers every app on every network, including hotspots, and works the same on a brand-new Pixel or a decade-old phone.
Fire tablets hide the Private DNS toggle, so the cleanest device-level filter is per-network DNS plus Amazon's built-in controls:
Repeat step 1-3 for each Wi-Fi network the tablet joins. At home behind the Gateway, every Fire tablet is covered the moment it connects.Covered at home automatically
Two layers, use both when you can:
The PlayStation has a hidden web browser reachable through apps and manuals, so it gets the same treatment as the Xbox. At home behind the Gateway it is already covered; the manual lock makes it stick:
Covered at home automatically
The Switch has no open browser, but its hidden one can be reached through workarounds, so we close the door anyway:
Covered at home automatically
Every one of these has a browser or sideload path. They live at home, so the Gateway covers them all automatically - that is the honest headline. Belt-and-suspenders locks where the device allows it:
All covered at home automatically
The quiet loopholes. A VR headset has a private browser two inches from your eyes; a Steam Deck is a full Linux PC; a Kindle has a web browser behind the bookstore.
Covered at home automatically
The Xbox has a full web browser in disguise (Edge), so it belongs in the protection plan. If it lives at home behind the Gateway or a filtered router, it is already covered. Add the manual lock so the coverage holds no matter what:
Covered at home automatically
Mac: the same one-tap profile as the iPhone works: download it, open it from Downloads, then approve in System Settings > Privacy & Security > Profiles.
Windows 11: Settings > Network & internet > Wi-Fi > Hardware properties > DNS server assignment Edit > Manual > IPv4 on:
185.228.168.168 185.228.169.168 (set DNS over HTTPS to On (automatic) where offered)
Members on Brother and above get named per-device profiles instead, so your reports say which device did what — that setup happens in your member app.
Filters love to say "works on everything." Here is what that actually means, version by version. Where a device is too old for the modern encrypted path, we name the fallback instead of pretending.
Swipe the table sideways to see every column.
| Device | OS versions | How we protect it | Coverage |
|---|---|---|---|
| iPhone / iPad | iOS / iPadOS 14 and newer (2020+) | One-tap encrypted profile (above) | Full — every app, every network |
| Older iPhone / iPad | iOS 8 – 13 (devices back to ~2012) | Manual DNS per Wi-Fi network (steps) | Per network + full at home |
| Mac | macOS 11 Big Sur and newer (2020+) | Same one-tap profile as iPhone | Full |
| Older Mac | macOS 10.15 Catalina and earlier | Manual DNS in Network settings | Per network + full at home |
| Android — modern | Android 9 and newer (2018+) | Built-in Private DNS setting (steps) | Full — every app, every network |
| Android — older | Android 5.0 – 8.1 (2014 – 2018) | Free Intra app (by Jigsaw / Google) with our filter address | Full — every app, every network |
| Android — ancient | Android 4.x and earlier (pre-2014) | Manual DNS per Wi-Fi network | Per network + full at home |
| Amazon Fire tablet | Fire OS 5 – 8 (all generations) | Static DNS per network + Parental Controls PIN (steps); Fire OS hides Android's Private DNS menu | Per network + full at home |
| Chromebook | ChromeOS 78 and newer (2019+) | Secure DNS in Chrome + per-network DNS + Family Link (steps) | Full with Family Link |
| Older Chromebook | Before ChromeOS 78, incl. end-of-life units | Per-network custom name servers | Per network + full at home |
| Windows PC | Windows 11 | Manual DNS with encrypted DoH switched on (steps) | Full |
| Older Windows PC | Windows 7, 8, 10 | Manual DNS on the network adapter | Full filter, unencrypted lookup |
| Xbox / PlayStation | All current + last generations | Manual DNS + console family passkey (Xbox / PlayStation) | Full at home |
| Nintendo Switch | Switch, Switch Lite, Switch 2 | Manual DNS + Nintendo Parental Controls app (steps) | Full at home |
| Smart TVs / streamers | Apple TV, Fire TV, Roku, Samsung, LG | Per-device DNS where offered + device PINs (steps); Roku is network-layer only | Full at home |
| VR / handheld / e-reader | Meta Quest, Steam Deck, Kindle | Manual DNS where offered + supervision PINs (steps) | Per device + full at home |
Chrome switches every extension off in incognito windows by default, and an extension is not allowed to switch itself back on. That means a private window is the one place the browser layer protects nothing, and it is the first place most men look. It takes fifteen seconds to close.
Open the extension again afterwards. If it says Protecting instead of warning you, it is on.
Worth knowing: the network filter on your devices already covers incognito, because it works below the browser. This step closes the browser layer too, so both are covering you.