DNS Ad Block Checker
Check whether your DNS server is likely blocking ads and trackers, such as Pi-hole or AdGuard Home.
Input
How it works
This tool sends lightweight requests to a control host and several well-known tracker or ad hosts. If the control host works but the tracker hosts fail, your DNS is likely filtering ads or trackers.
Limitations
This cannot read your DNS server directly. Browser extensions, VPNs, captive portals, firewalls, or general connectivity problems can affect the result, so treat it as a likely signal rather than a proof.
Test targets
Control: a neutral connectivity check. Trackers: DoubleClick, Google Ads/DoubleClick, Google Analytics, and Meta Pixel.
Output
Result summary
Run the check to see whether tracker hosts are being blocked.
| Probe | Target | Status | Time |
|---|---|---|---|
| Connectivity check | www.gstatic.com | Not checked yet | |
| DoubleClick | www.doubleclick.net | Not checked yet | |
| Google Ads / AdSense | pagead2.googlesyndication.com | Not checked yet | |
| Google Analytics | www.google-analytics.com | Not checked yet | |
| Meta Pixel | connect.facebook.net | Not checked yet |
Readme
What is DNS-based ad blocking?
DNS-based ad blocking works by preventing requests to known ad, tracker, or telemetry domains before they reach the browser. Instead of blocking content in the page itself, the network layer stops those hostnames from resolving normally.
Because the browser never gets a usable address for a blocked domain, requests may fail, time out, or resolve differently depending on the DNS service and filtering rules in use. That makes it possible to infer whether a network is using ad blocking or privacy filtering.
Tool description
This tool checks whether ad blocking appears to be active by probing a control request and several known tracking URLs. It summarizes the result with a table that shows each probe host, its status, and how long the request took.
It is a practical diagnostic tool for understanding whether DNS filtering is affecting a network, browser, or device.
Features
- Heuristic detection: Compares a control request with known tracker probes
- Request timing: Shows how long each probe took to help distinguish blocked and reachable hosts
- Simple status table: Makes it easy to scan the result without digging through raw network details
How it works
The tool sends no-cors fetch requests with a timeout and classifies each probe based on whether it appears reachable, blocked, or timed out. This is an inference method, so the result reflects network behavior rather than a direct ad-blocker API.
Limitations
- It requires network access to run the probes.
- The result is heuristic and can vary by DNS provider, browser, or firewall.
- Some networks may return misleading responses instead of a clean block.