Skip to main content
Preparing workspace

Network Ad Blocker

Check a site, HAR capture or DNS-over-HTTPS lookup against community blocklists, spot CNAME-cloaked trackers, and export Pi-hole, hosts or dnsmasq rules.

Still loading. If the tool doesn’t appear, reload this page.

About this tool

Network Ad Blocker

Check websites, DNS-over-HTTPS sinkholes, CNAME-cloaked trackers, and HAR captures against community blocklists, then export Pi-hole, dnsmasq, or hosts configs.

Network Ad Blocker downloads upstream filter feeds (AdGuard DNS, Anudeep Adservers, HaGeZi Threat Intelligence & Multi Light, and StevenBlack) when you first use it and compiles them with your custom rules in the browser. Enter a public website or paste page HTML to list external scripts, iframes, pixels, and beacons; run DNS-over-HTTPS probes across Google, Cloudflare, and AdGuard DNS to check sinkholing and CNAME cloaking; audit Chrome or Firefox HAR captures for the bytes your rules would block; and export ready-to-deploy blocklists for Pi-hole, AdGuard Home, dnsmasq, Unbound, BIND RPZ, PAC proxies, or Manifest V3 extensions. Requests that carry your input go to api.allorigins.win and dns.google.

How to use Network Ad Blocker

  1. 1

    Start with any control: on first use the AdGuard DNS, Anudeep and HaGeZi Threat Intelligence lists (about 10 MB of text) download into the in-browser lookup. Click Sync Live Lists later to refresh them.

  2. 2

    Enter any public domain such as cnn.com or nytimes.com in the Site Network Scanner and click Scan Live Traffic to inspect real scripts, iframes, pixels, and 3rd-party hosts.

  3. 3

    Select DoH on any flagged host or open Live DNS & CNAME Probe to compare Google 8.8.8.8, Cloudflare 1.1.1.1, and AdGuard DNS side by side.

  4. 4

    Drop a browser DevTools .har trace in Traffic Stream & HAR Audit or export your tuned ruleset in hosts, dnsmasq, Unbound, RPZ, PAC, or Chrome MV3 JSON format.

Why use Network Ad Blocker

  • Counts from real feeds and traces

    Rule counts, fetch times, DNS records, and verdicts come from the feeds you synced, the page fetched, the resolvers queried, or your own HAR trace.

  • Parallel DoH & CNAME-cloaking detection

    Compares unfiltered resolvers (8.8.8.8 and 1.1.1.1) against AdGuard DNS and Cloudflare Security and checks CNAME chains against your compiled rules.

  • Seven deployable export formats

    Turn your tuned ruleset into Pi-hole/AdGuard syntax, 0.0.0.0 hosts files, dnsmasq, Unbound, BIND RPZ, PAC scripts, or Manifest V3 JSON.

Common use cases

  • Audit any live website URL to see every third-party script, ad frame, tracking pixel, and inline beacon before deploying network-wide DNS filtering
  • Verify whether a tracker domain is sinkholed (0.0.0.0 or NXDOMAIN) by AdGuard DNS or disguised behind a first-party CNAME alias
  • Analyze exported browser DevTools .har files in your browser to see the share of requests your rules match and the payload bytes they carried
  • Compile custom allowlists and blocklists into clean hosts, dnsmasq, Unbound, RPZ, PAC, or Chrome declarativeNetRequest files

Frequently asked questions

How does this Network Ad Blocker work?

The first time you use it, it downloads three community blocklists (about 10 MB of text) from adguardteam.github.io, raw.githubusercontent.com and cdn.jsdelivr.net, parses hosts and Adblock Plus syntax into an in-browser subdomain lookup, and caches them in IndexedDB. Nothing is downloaded just by opening the page. When you scan a URL, probe a domain over DNS-over-HTTPS, or open a HAR file, each host is checked against that compiled lookup in your browser.

What is CNAME cloaking and how does the DNS probe catch it?

Some trackers hide behind a first-party subdomain (for example metrics.example.com) that points via a DNS CNAME record to a third-party tracking provider. The DNS probe reads the CNAME records returned over DoH and checks every target in the chain against your active blocklists.

Are my HAR files, rules, or typed domains uploaded?

HAR files, custom rules, raw HTML scans, and exports stay in your browser. A URL you type into the scanner is sent to our own inspector route, which fetches the page; if that route fails, the browser tries the page directly and then the public relay api.allorigins.win, which sees the URL. Feed downloads fall back the same way. A domain you probe is sent to dns.google, cloudflare-dns.com, dns.adguard-dns.com, security.cloudflare-dns.com, and any custom resolver you add.

What does the blocking check send?

Only when you click Send test requests, your browser requests a few ad and tracker hosts from your synced lists, so those hosts see your IP address. It then reports whether your browser, extensions, or DNS stopped each request.

Which router and DNS formats can I export?

You can copy or download compiled rules as Pi-hole / AdGuard Home filters (||domain^), /etc/hosts (0.0.0.0), dnsmasq config, Unbound local-zone rules, BIND RPZ zones, PAC proxy scripts, or Chrome Manifest V3 declarativeNetRequest JSON.