StrictDNS

The partner notification when a device stops being protected is the clever bit — most DNS blockers are trivially bypassed by switching the setting back, and this turns that into something a partner actually sees. How do you detect "stopped being protected": a heartbeat from the device, or the absence of queries from its profile? And on iOS, does it rely on a DNS configuration profile, and what happens on a network that forces its own DNS?

Blocking adult content, gambling, and endless-scroll apps on every device at once, with a trusted partner notified when you change the blocks or a device stops being protected, makes a DNS filter harder to quietly undo. If you ever need AI for your business, check out PZERO at pzero.studio.

The trusted-partner alert is a thoughtful safeguard because it makes protection accountable without exposing browsing history by default. The all-device scope also sounds useful for families and small teams; what is the recovery flow when a device loses its protection temporarily due to a network or profile change?

The trusted-partner notifications are a genuinely differentiating feature — accountability to another person is what most blockers miss. Does the block hold at the DNS level so it survives app reinstalls? And if a protected device goes offline, is the partner notified right away or after a grace period? This looks useful for family networks, not just individuals.

Making the partner role free is a clever growth loop: every user brings in a second person who already cares about the problem. One technical question others haven't covered: Chrome and Firefox can switch on their own "Secure DNS" (DNS-over-HTTPS) and skip the device's DNS settings entirely. Do you lock that down, or detect it and treat it as "device not protected" so the partner gets notified? Same for in-app browsers that use their own resolver. Getting that right is probably the difference between a blocker someone trusts and one they quietly work around.

The trusted-partner notification is a clever approach to accountability. One practical question: does StrictDNS work at the router level so every device on the network is covered at once, or does each device need its own setup? That is usually the deciding factor for households and small teams.