Enter a domain to check the public signals behind blank ad slots, then work through the reasons AdSense ads fail to display.
This lookup reads the public registration record for the domain you enter. It answers from the outside only: it cannot read your AdSense account, your content or your policy history, so it is guidance rather than a Google approval guarantee. How PubSpy handles data.
Registration age, expiry window and registry status - a domain in trouble takes the ad code down with it.
Blank ad slots are almost always client-side. We tell you that plainly and list what to inspect in the browser, in order.
Ad serving status, payment holds and policy filters sit inside AdSense. This page tells you which screen to open instead of guessing.
First, the browser: content blockers, tracking protection, Brave shields or a corporate DNS filter all stop the ad request before it reaches Google. Test in a clean profile before you change any code.
Second, the code: an ad unit that was deleted, a script blocked by your own Content Security Policy, a consent message that never fires, or a slot inside a container with zero height.
Third, the account: pending review, a payment hold, or ad-serving filters that Google applies to a page. That part is only visible inside your AdSense account.
Confirm registration, registrar and expiry before debugging any JavaScript.
No extensions, no blockers. If ads appear there, the problem is client-side.
Confirm the site is approved, the ad units are active, and no policy filter applies to the page.
The usual causes are ad blockers, a blocked or missing ads.txt, a consent flow that never completes, ad code removed from the template, or ad serving paused on the account. Start in a clean browser profile without extensions.
Blocked ad requests on your own visitors are visible in AdSense reporting as missing requests, not on this page. This check looks at domain-level signals only.
No. Visitors may block ads. What violates policy is encouraging clicks or hiding ads behind deceptive layouts.
For AdSense it is a verification signal rather than a switch. A missing or wrong ads.txt can limit demand from other networks, so keep it accurate if you run them.
Free AdSense checker for any website: registration age, registrar, registry status and expiry, plus the content and technical signals that decide AdSense compatibility.
Google AdSense checker: see domain age, registrar, registry status and expiry for any site, plus the page-experience signals Google assesses, including indexing and Core Web Vitals.
AdSense ban checker for publishers: check a domain for the public risk signals behind AdSense bans and disapprovals - registration age, ownership churn and registry status.
Looking for the other direction - which publisher IDs own a site? Open the AdSense publisher ID reverse lookup, or read what PubSpy costs before you run a full analysis.
PubSpy reads the site you are viewing - copy, structure, pricing signals - and returns an evidence-backed case study with source-linked research. Eligible new accounts get 100 starter credits; each analysis or follow-up costs 5.
Install the free extension Claim starter credits