CMPT 415 - Ad Blocker Research PoC

Built with: plain html + css + js

A single page with content sections for content-blocker and NoT.js research: non-ad images, AdSense slots, PostHog comments, and deliberate initiator-chain evasion patterns. No framework, no bundler, no build step - every function a crawler sees is written exactly as it ships.

Remote images served from picsum.photos and placehold.co. These are baseline content and should remain visible even when an ad-blocker is active.

Mountain landscape
Mountain landscape picsum.photos - pending
Beach sunset
Beach sunset picsum.photos - pending
City skyline
City skyline picsum.photos - pending
Forest path
Forest path picsum.photos - pending
Desert dunes
Desert dunes picsum.photos - pending
Sample placeholder image
Sample placeholder image placehold.co - pending

Advertisements (Google AdSense)

Each slot below is a real <ins class="adsbygoogle"> element backed by AdSense publisher ca-pub-7908406465990634. Loader script and slot push calls are intermixed with regular page logic in a single bootstrap function (see bootstrapPageAndAds() in js/67522eea-c769-430a-a5ce-ecc2c7b50534.js) so we can observe how content blockers handle non-isolated ad code paths.

AdSense script: loading...
Slots queued: 0 / 3
Ad-block heuristic: running...
Local visits: 0

NoT.js evasion patterns

Three initiator-chain experiments that run automatically on page load (no clicks required) so NoT.js / Duumviri crawlers capture function call stacks and network requests. Tracker hosts are EasyPrivacy-listed (googlesyndication.com, google-analytics.com).

Bootstrap: pending

Pattern 1 - Call chain with benign callee in initiator

a() → b() → c() → d() loads the AdSense script on load. Inside d(), benign e() runs before the script append and sends a same-origin HEAD /favicon.ico control request.

Tracker URL:

Pattern 2 - Overridden fetch decoy vs native fetch tracker

On load: decoy window.fetch is installed, then benign HEAD /favicon.ico and GA collect via saved nativeFetch.

Tracker URL:
Benign fetch: pending · Native tracker fetch: pending

Pattern 3 - Shared request wrapper (collateral damage)

On load: functional and tracker traffic both go through the exact same sharedFetchWrapper function, differing only in the URL/kind passed in - isolating whether sharing a wrapper causes collateral damage, independent of which request API is used.

Tracker URL:
Wrapper calls - functional: 0, tracker: 0, errors: 0
Functional: pending · Tracker fetch: pending

Comments (0)

User-generated content, persisted in localStorage on this device. Activity (post / delete / reset) is sent to PostHog via posthog.capture(...), interleaved with form logic in the handlers below. Set posthogProxyMode: 'custom' and posthogApiHost in config.js to your CNAME subdomain for first-party proxy / cloaking experiments. Tip: Ctrl+Enter submits the form.

PostHog SDK: initializing...
Events captured: 0
Proxy mode:
Cookieless:
api_host: