Ad Block Test: is your blocker actually working?
We fire requests at 32 real ad networks, trackers, push services and in-app ad SDKs from your device, and show which ones get through.
Requests go straight from your browser with no cookies and no referrer. Nothing is sent to pwnsy.
Every endpoint
How the test decides
Network check. For each endpoint the page makes a request with no cookies and no referrer. Any HTTP answer, even an error page, means the device reached the server: reached. A refused request means something stopped it before it left: a content blocker, a filtering DNS resolver, a firewall or a VPN's blocklist: blocked. A request with no answer in 8 seconds is marked no answer and left out of the blocked count: some DNS filters answer with an address that never responds, and a slow server looks the same.
Connection check. Four ordinary sites (pwnsy, Wikipedia, Mozilla, GitHub) are requested too. If they fail, the connection is the problem and the result is not trusted.
Layer check. The page also places a hidden decoy element with common ad class names. Browser content blockers that do cosmetic filtering hide elements like it; a DNS resolver cannot touch the page. A hidden decoy proves a browser blocker is active. A visible one proves nothing, because some blockers only block requests. A blocked request looks the same to the page whichever layer stopped it, so the reliable way to separate them is to run the test twice with one layer switched off.
Two limits. Your browser may use its own secure DNS setting instead of the phone's Private DNS, so apps can see a different resolver from this page. And some filter lists only block an ad domain when it loads on another site, so a result here can differ from a news page.
What to do with the result
Ads and trackers reached: install a content blocker (uBlock Origin on Firefox, uBlock Origin Lite on Chrome, a Safari content blocker on iPhone), or set a filtering resolver as Private DNS. How to set up encrypted DNS walks through each device.
In-app ad SDKs reached: a browser blocker does nothing for apps. Only a DNS filter or a system-wide blocker covers ads inside apps, including the ones that open shopping apps on their own.
Push services reached: these only matter if you have allowed a site to send notifications. Remove sites you do not need under your browser's notification settings.