Quick, Standard, or Deep.
Results
Live scan details.
Blocked means your blocker caught it
Open means the request or bait got through
Warning means the signal timed out or was unclear
No matching checks.
Cosmetic filters
Static and dynamic ad-shaped boxes show whether your blocker hides empty ad spaces.
Scripts and pixels
Local baits and third-party probes check ad scripts, analytics, social pixels, and error monitors.
Network signals
A small set of reachability checks helps spot common ad endpoints that still answer from the browser.
Cosmetic bait zone
Harmless traps used by the scan.
If these boxes disappear, cosmetic filtering is doing its job.
Ad banner
Sponsored
Native ad
Static ad
Plain answers
How to read the score.
Most ad scripts, trackers, and cosmetic bait are blocked. Review any open rows, but you are in good shape.
Your blocker is working, but some categories are slipping through. Start with Open rows under ads, analytics, and social trackers.
The blocker may be off, too permissive, or missing common lists. Try one blocker at a time, update lists, then run Deep scan again.
What should I fix first?
Start with Open rows in Ad networks, Analytics, Social trackers, and Cosmetic filtering. Those categories usually have the biggest day-to-day browsing impact.
What does “Blocked” mean?
The script, pixel, request, or ad-shaped box failed to load or became hidden. That usually means your blocker caught the test case.
What does “Open” mean?
The test case loaded or stayed visible. It does not always mean your blocker is bad, but it is the row to inspect if your score is lower than expected.
What does “Warning” mean?
The browser could not give a clean answer. Timeouts, strict browser settings, flaky third-party hosts, or network conditions can create warnings.
Why can a test say “open” even when my blocker works?
Some providers allow simple image or script probes while still blocking real ad behavior elsewhere. Treat the score as a practical snapshot, then inspect the detailed rows.
Does this page upload my results?
No. The checks run locally and results are rendered in your browser. This site does not include third-party analytics.
Why is there only a small network reachability check?
A browser page cannot reliably prove device-level or resolver-level blocking. This test keeps network reachability small and uses it only as a supporting signal beside scripts, pixels, and cosmetic checks.
Why do blocker apps and browser extensions score differently?
They block at different layers. Apps can stop whole endpoints, while extensions can hide page elements and block specific script paths. Running several blockers together can also create false positives.
Should I aim for 100/100?
No. A very high score is nice, but a perfect score can require aggressive lists that may break sites. A strong score with normal browsing working well is the better goal.