Ad Landing Page Checker
The click URL in your tag is almost never where the user actually lands. We resolve the click destination macro-aware, follow the redirect chain hop by hop, and judge the page at the end.
Trace a Tag's Click Chain →Follow the click chain, hop by hop
Resolve the click destination
Resolution is macro-aware, so ad-server click macros don't stop the trace before it starts.
Record every hop
Each hop is logged with its URL, HTTP status, and hop type — the full path, not just the endpoints.
Judge the final page
The final page gets the audit: status, HTTPS, soft 404s, parked domains, mobile viewport, page weight, and domain drift.
What we judge on the final page
| Check | What it catches | Severity |
|---|---|---|
| HTTP error status | Final page answers with an error status | Launch-blocking |
| Parked domain | Registrar parking markers — Sedo, Bodis, GoDaddy parking copy | Launch-blocking |
| Soft 404 | A 200 whose title or heading says "not found," or a near-empty body | Warning |
| Domain drift | Destination redirects to a different registrable domain | Warning |
| HTTPS | Final page served over HTTPS, or not | Reported |
| Mobile viewport | Mobile viewport declared, or missing | Reported |
| Page weight | Measured within a bounded fetch | Reported |
Every rule cites its primary source in the validation policy.
Soft 404s: dead ends monitors call healthy
Uptime monitors watch status codes. A soft 404 returns HTTP 200 while showing the user a dead end — a "not found" title or heading, or a near-empty body. Status-code monitoring reads that as healthy. This checker reads the page, so a 200 that behaves like a 404 is flagged as one.
Domain drift: how hijacked campaigns pass review
The URL that got reviewed isn't always the URL that serves. Domain drift is when the resolved destination redirects to a different registrable domain — the pattern behind cloaked and hijacked campaigns that pass review on one URL and serve another. A drift warning includes the full hop chain that produced it.
Safe by design
Every fetch is SSRF-guarded: destinations that resolve to private or internal addresses are blocked and flagged, never fetched. Chains stop at 10 hops or 10 seconds, whichever comes first; when a bound cuts a trace short, the report says so rather than passing off the last hop as the confirmed destination.
Frequently asked questions
What is a soft 404, and why does status-code monitoring miss it?
A soft 404 returns HTTP 200 but is actually a dead end — its title or heading says "not found," or its body is near-empty. Monitors that only watch status codes see the 200 and call the page healthy.
How is a parked domain detected?
By registrar parking markers — parking copy from services like Sedo, Bodis, and GoDaddy. A parked landing page is a launch-blocking finding.
Are redirects followed safely?
Yes. Every fetch is SSRF-guarded — private and internal destinations are blocked and flagged — and chains are bounded at 10 hops and 10 seconds, with truncation reported honestly.