ZonoTools
Home/Device Tools/Am I Blocking Ads

Am I Blocking Ads

Ad blocking

Checking…

Uses a bait element targeted by common filter lists. Some blockers may not be detected.

How to use

  1. Open the page — Yes or No appears after the bait element test runs.
  2. Temporarily disable your ad blocker for this site and Refresh to compare results.
  3. Read the detection method line to understand what was tested.

FAQ

Am I blocking ads?

If the headline says Yes, a hidden bait element with class names common filter lists target was collapsed, hidden, or removed from layout — a strong sign an ad blocker or cosmetic filter is active.

Why does a site ask me to disable adblock when this says No?

Sites use their own scripts that may detect different patterns than this bait. DNS-level blockers (Pi-hole) or novel lists may not touch our test element.

Which blockers are detected?

Many list-based tools (uBlock Origin, AdBlock, AdGuard, Brave shields) hide elements with ad-related class names. Detection is heuristic, not a list of extension names.

Is ad blocking bad?

It is a user choice. Some sites break without ads revenue; blockers improve privacy and speed. This page only reports whether a blocker likely affects this tab.

Can I whitelist this site?

Yes — use your extension’s disable-on-this-site control, then Refresh here to see No.

Is anything uploaded?

The bait element is created and measured locally. No ad blocker name is sent to us.

Introduction

Am I Blocking Ads checks whether an ad blocker or cosmetic filter list is probably active in your browser by creating a harmless bait element with class names filter lists recognize (adsbox, ad-banner, and similar). If the element is hidden or zero-sized, the headline reads Yes — ad blocker likely active.

Millions of users run uBlock Origin, AdBlock, Brave Shields, or corporate DNS blockers. Sites respond with paywalls or broken layouts when they detect blocking. Whether you want to confirm your shield is on — or debug why a site complains — this page gives a quick local signal.

How detection works

Step Purpose
Insert hidden div with ad-like classes Mimics ad slot markup filter lists target
Measure size / visibility after paint Blocked elements often have 0 height or display:none
Report Yes or No Heuristic, not extension fingerprinting by name

This is the same family of technique sites use for “disable adblock” messages — used here for your transparency.

False positives and false negatives

  • False positive — aggressive “annoyances” lists hiding unrelated elements with “ad” in the class.
  • False negative — DNS-only blocking (router Pi-hole) without cosmetic filters in the browser.
  • Brave/Safari — may report differently than desktop uBlock; always compare with Refresh after toggling shields.

Common use cases

  • Confirm extension is on after install.
  • Whitelist a broken site — disable blocker, Refresh, confirm No, re-enable selectively.
  • Support — verify whether a blank video player is adblock vs codec issue.
  • Privacy audit — pair with what is my fingerprint and what permissions have I granted.

Best practices

  • Prefer site-specific allowlisting over turning the blocker off globally.
  • If a site you trust breaks, try No here first before blaming the network.
  • DNS blockers need router admin checks — this page is browser-side only.
  • For connectivity issues unrelated to ads, see am I online.