cookiewall.wtf

/ site / cnn.com

F

cnn.com

Consent was never the plan.

scanned 2026-07-05 · clean Chromium · Frankfurt, EU

What it did

  • 14 tracker host(s) contacted before you were asked anything.
  • 3 third-party cookie(s) set before consent.
  • No reject option on the first layer. Accepting is one click; refusing is a journey.
  • Rejecting takes 2 click(s); accepting takes 1. Asymmetry is the point.

Consent Facts

Per first visit, before any consent given

Cookies set26
first-party23
third-party3
Tracker hosts contacted14

9121dee25fe653e49092db11211de6b7.safeframe.googlesyndication.com · census-web.scorecardresearch.com · dt.adsafeprotected.com · +11

Consent vendorOneTrust
Reject on first layerno
clicks to reject2 (accepting: 1)

The evidence

What our browser saw, before anyone clicked anything.

Screenshot of cnn.com on first load

The watch

Consent flows change quietly. Watching means you hear about it — including if this site ever cleans up.

Cancel from any email. No account, no dashboard.

Grades change when sites do. Anyone can re-scan this domain — three fresh scans an hour, results cached for a day.