Is your blocker working? This page attempts to fetch twelve
well-known tracker resources — analytics libraries, ad-server tags, social pixels, session-replay
scripts — and reports which ones your browser, extensions, or network layer actually blocked.
100% client-side · no results are transmitted anywherenothing runs until you press the button
Read before running. By design, this test makes real network requests to known
tracker domains (Google Analytics, DoubleClick, Meta, TikTok, Hotjar, and others). If your stack
does not block a request, that tracker's server will see an ordinary resource request
from your IP address. Requests are sent without cookies (credentials:
"omit") and without a referrer, and the page never executes any tracker code — it only
observes whether each request completes. Scoring happens locally; nothing about you or your
results leaves this page.
How it works
Each endpoint is requested with fetch(url, {mode:"no-cors", cache:"no-store"}) and a 4-second timeout.
A rejected or cancelled request counts as BLOCKED — content blockers cancel matching requests, which surfaces as a network error.
A completed (opaque) response counts as LOADED — the tracker host was reachable.
Separately, bait elements with standard ad class names (adsbox, ad-banner, ad-placement…) are inserted and measured to detect cosmetic filtering — the element-hiding half of a content blocker.
Honest caveats
A blocked request is indistinguishable from a network failure. If you are offline, or a firewall or captive portal interferes, everything reads as "blocked".
no-cors responses are opaque: the page can only observe reachability, not what came back. A DNS filter that answers with a dummy server can read as "loaded" even though the real tracker never saw the request.
Some blockers neutralise trackers by substituting a harmless local stub instead of cancelling the request. Those can read as "loaded" even though tracking is disarmed.
Filter lists update constantly. The same browser can score differently next week, and results vary by list subscriptions and blocker configuration.
Firefox's built-in tracking protection blocks known trackers in private windows by default; blocking in normal windows requires strict mode.
Cosmetic filtering is often disabled on local file:// pages unless you grant the extension file access.
This matrix is twelve well-known endpoints, not the whole tracking ecosystem. A perfect score here is evidence your blocker works — not proof you are untrackable.
the limit of this test
This page only tests your browser. Server-side collection — first-party
beacon endpoints, server-to-server conversion APIs, log-based analytics — is invisible from here,
and no extension can block it. ad.rip audits what sites actually
collect. For defence, start with the privacy guides.