Test your ad blocker.

Your score is the weighted share of checks that were blocked. Higher-weight checks represent common ad, analytics, tracker, or cosmetic-blocking signals. Warning rows are shown separately and do not add points.

Start with Open rows in Ad networks, Analytics, Social trackers, and Cosmetic filtering. Those categories usually have the biggest day-to-day browsing impact.

The script, pixel, request, or ad-shaped box failed to load or became hidden. That usually means your blocker caught the test case.

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.

The browser could not give a clean answer. Timeouts, strict browser settings, flaky third-party hosts, or network conditions can create warnings.

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.

No. Results are rendered in your browser and this site does not include third-party analytics. Some checks do contact test endpoints so your blocker can be measured against real browser requests.

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.

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.

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.