FlashDroid's Web Filter Isn't Blocking Sites: What to Check

You block the “adult” category.

Then a site still opens.

The natural reaction is:

“The web filter is not working.”

Sometimes that is true.

But the first thing to determine is where the content is opening.

FlashDroid’s web filtering is designed for category-based website filtering. It is not a system-wide scanner that reads content inside every app.

That distinction solves a lot of confusion.

First question: browser or native app?

If the content is inside:

• TikTok
• Instagram
• Reddit app
• Telegram
• another native app

then the browser web filter is not the layer deciding what individual post, video or message appears.

If the child taps a normal web link and it opens in a browser, then the browser/category rule is relevant.

This is why a parent can correctly block a website category and still see related content inside an allowed app.

Confirm the category is actually enabled

Open the parent rule and verify:

• the intended category is turned on
• the rule is assigned to the correct child
• the child phone is online
• the latest rule has synced

Do not assume a parent-side toggle became active on an offline child device immediately.

Reconnect the phone and test again.

Test a known category site in the normal browser

Use a safe test domain from your filtering provider if available.

Avoid using explicit content simply to test a filter.

The test should answer:

Does the browser request get blocked?

If yes, the filter layer is working.

If a particular site still loads, classification may be the issue rather than the entire filter.

Category filters are not perfect site lists

Website classification can have:

• false negatives
• false positives
• new domains not classified yet
• mixed-purpose websites that do not fit one category cleanly

That is why parent allow/block exceptions matter.

A useful workflow:

1. Category rule handles the broad class.
2. Manual block handles a known miss.
3. Manual allow handles a legitimate false positive.

Check which browser is being used

A common failure pattern:

• Chrome is configured
• another browser is installed
• child opens the site there

Review:

• which browsers are installed
• which one is the default
• which browser path the FlashDroid filter is configured to cover

If the family wants one primary browser, remove unnecessary alternatives where appropriate.

For broader architecture, read the web-safety guide.

Browser filtering is different from SafeSearch

SafeSearch mainly filters explicit Google Search results.

A category filter decides whether a destination website/category is allowed.

Those are separate jobs.

A child can bypass a search-result path by using a direct URL while still being blocked by a website filter.

Or a child can see content inside an app while both Search and browser filtering are functioning correctly.

Understanding the layer prevents unrealistic expectations.

Check background health if filtering stopped broadly

If the filter worked earlier and stopped later, background health may be relevant.

Android Doze can defer background network access and CPU work while the device is idle.

Source: https://developer.android.com/training/monitoring-device-state/doze-standby

Use the generic diagnosis first: why parental-control apps stop working in the background.

Then use the exact phone-brand guide if needed:

• Samsung
• OnePlus
• generic Android

Do not disable broad system protections unless the phone-specific guidance actually calls for it.

When it is not a bug

A site can load even when FlashDroid is behaving correctly if:

• the category is not enabled
• the rule has not synced yet
• the request occurs in a browser path not covered by the current setup
• the content is inside a native app rather than the browser
• the site is not currently classified into the blocked category

The right fix depends on which one happened.

What FlashDroid does and does not do

FlashDroid’s web layer:

• filters browser website access by category
• supports parent-managed website rules

It does not:

• read private messages
• classify individual TikTok/Instagram posts
• inspect every video inside YouTube
• act as a hidden system-wide content scanner
• guarantee impossible-to-bypass filtering

For app access, use FlashDroid’s separate app rules.

See the Android parental-controls guide and limit games and apps use case.

Fast troubleshooting order

1. Confirm category is enabled.
2. Confirm correct child.
3. Confirm child phone is online and synced.
4. Test in the normal supported browser.
5. Confirm whether the content is actually in a native app.
6. Test a second known site in the same category.
7. Add a manual block if classification missed one domain.
8. Check background service health if the filter stopped working broadly.

Sources

• Android Developers — Doze and App Standby
  https://developer.android.com/training/monitoring-device-state/doze-standby