The second-browser problem

Most parental filters guard one door in a house full of doors. You lock down one browser, and a week later your kid is on one you have never heard of. That is not a parenting failure. It is a design flaw in browser-based filtering, and there is a real fix. Here is the whole story.

What is the second-browser problem?

You spend an evening doing everything right. You add a filtering extension to Chrome. You turn on the built-in controls. You test it, and the bad stuff is blocked. You go to bed feeling like you finally handled it.

A week later, they are on a browser you did not know existed. Not because they are a hacker. Because installing a browser takes thirty seconds and a search, and the filter you set up only ever lived inside the first one. The new browser has never heard of your rules.

That is the second-browser problem, and if it has happened to you, you are in very good company. It is the single most common way home filtering quietly falls apart.

Why does it keep happening?

Because a browser filter only sees inside that one browser. It is not watching the machine. It is watching a single app. Anything that happens outside that app, a different browser, a portable one run off a USB stick, a game with a built-in web view, is invisible to it.

So the fix is never “find the one true browser and lock it too”. There is always another one. It is a house with a hundred doors, and you are running around bolting them one at a time while your kid strolls through the next unbolted one. You cannot win that race by adding locks faster.

We know this pattern well. It is close to the reason FamilyProtect exists in the first place, which is a longer story in why we built FamilyProtect.

What actually fixes it?

You stop guarding doors and start guarding the hallway they all open onto.

Every browser and every app, no matter which one, does the same thing when it opens a website: it asks for the site’s address before it can load anything. FamilyProtect filters at that step, below all the browsers. When the address belongs to a harmful or adult site, the answer is refused and the page never loads, and it does not matter one bit which browser asked. First browser, fifth browser, a portable one you have never seen: all filtered, because the filtering happens underneath all of them.

There is no second-browser loophole to close, because there is no browser doing the filtering. The hallway is covered, so every door is.

But can’t they just get around that too?

Not the way they got around the browser filter. The classic escape route is reaching for a different lookup service to route around the filtering. FamilyProtect blocks those attempts too, and shows them to you as a filter-bypass attempt, which is usually an app doing it automatically rather than a child plotting. There is a calm guide to what that means in when kids try to bypass web filters.

It also runs with system privileges a standard child account cannot change, and it checks itself continuously and repairs itself if something breaks. So it is not one more door for them to find open. It is the floor under all of them.

If this has been you

Stop blaming yourself for the browser you did not think of. There was always going to be one. The problem was never your diligence, it was that you were handed a tool built to guard one door. Guard the hallway instead, and the second browser stops mattering.

Ready to cover every browser at once, including the ones you have not heard of? Get started.