Is Supreme AdBlock working in this browser?
This page is a demonstration, not a comparison. It shows that your copy of the extension is doing its job right now, on this page. It says nothing about any other blocker, and nothing about how much better or worse one is. This page cannot always tell which extension or browser feature passed a check. To see Supreme AdBlock alone, pause it from its popup and reload: rows 1 and 2 should change.
Checking…
Not installed yet? Get it from the Chrome Web Store, then reload this page.
The checks
-
1. Network blocking
What it checks: this page asks its own server for a test file whose address looks like an ad banner, and for a second file that does not. Blocking means the first request fails while the second one loads.
Checking…
What it does not prove: anything beyond one rule and one test file. It does not show that any particular ad network on any other site is stopped. It also cannot show that Supreme AdBlock, not another blocker or your browser, did it.
-
2. Element hiding
What it checks: the box below carries a name that the built-in generic hiding list covers. If the extension is active here, the box is hidden.
Checking…
What it does not prove: that the ad on a given site is hidden. Sites use their own names, which depend on site-specific rules; this box does not test those. It also cannot show that Supreme AdBlock, not another blocker or your browser, did it.
-
3. Tracking parameters
What it checks: follow this link. Its address carries
utm_sourceandfbclid. When you arrive, this page reports whether they are still in the address bar.Follow the link above to see the result.
What it does not prove: that every tracking parameter is removed. Only the names on the built-in list are, and only when a page is opened. It also cannot show that Supreme AdBlock, not another blocker or your browser, did it.
-
4. Global Privacy Control
What it checks: whether this page can read
navigator.globalPrivacyControlastrue, the browser signal that asks a site not to sell or share your data.Checking…
What it does not prove: that a site respects it. The signal is a request, and some browsers send it without any extension, so this row cannot show that Supreme AdBlock sent it.
-
5. Cookie banner
What it checks: the banner below is a demo. Its Reject button reuses one button id of a widely used consent platform (an invisible name in the page code; nothing from that platform is loaded), and nothing else on this page is a banner. If the extension is on, it presses Reject by itself.
Demo banner: nothing is stored.
Waiting for the extension to answer the banner…
What it does not prove: that every banner on the web is answered, or that it is always refused. Real banners differ; when a banner has no Reject button the extension recognises, it presses Accept as a last resort (see how it answers banners). It is built to press only controls it recognises as part of a consent banner. This page also cannot tell which extension pressed the button, only that one did while Supreme AdBlock's banner handling was on.
Nothing on this page is sent anywhere
The checks run in your browser and read only this page. The two test files come from this same server, like any other file of this page. Our server counts nothing and keeps no log of these requests. Your own extension's counters in its popup may go up by one, as on any page, and stay on your device. The page keeps one flag in this tab's session storage to know you followed the link in check 3; it is gone when you close the tab. This page loads nothing from another site; only if you follow the Chrome Web Store link does Google see that you came from this page. See the privacy policy.
If a row says “Not blocked”
- Protection may be switched off or paused. Open the popup and check the main switch.
- This site may be on your allowed list. Allowing a site turns blocking off there on purpose.
- The feature may be off in Settings: tracking-parameter clean-up, cookie banners or Global Privacy Control each have a switch.
- Another extension or a browser setting may be in the way, or the page was opened before the extension finished starting. Reload once.
Still not working? See support.