heise.de
Heavy tracking seen
25/100
- We didn’t find a reject button on the first screen of the cookie banner
- The banner asked visitors to accept 159 ad-industry “partners”
- 27 cross-site tracking companies were seen after accepting
- Device-fingerprinting techniques seen (audio, canvas)
Where the data went
From our checker in London to 22 tracker server locations in 10 countries. Drag to spin.
- Advertising
- Data broker
- Our checker (London)
Server locations
Tap one to find it on the globe
Companies
Who showed up
- 01333AcrossAd exchange and identity · New York · servers in New YorkAdvertisingBeforeAfter accept
- 02AAdformAd platform · Copenhagen · servers in CopenhagenAdvertisingBeforeAfter accept
- 03AAdobeMarketing analytics and ad platform · San Jose · servers in Ashburn, Frankfurt am MainAdvertisingBeforeAfter accept
- 04AAmazon AdsAd network · Seattle · servers in Seattle (South Lake Union)AdvertisingBeforeAfter accept
- 05CCriteoRetargeting ad network · Paris · servers in Paris, GroningenAdvertisingBeforeAfter accept
- 06DDoubleVerifyAd verification · New York · servers in Montreal, Toronto (Old Toronto)AdvertisingBeforeAfter accept
- 07EEpsilonMarketing data (data broker) · Irving, TX · servers in Frankfurt am MainData brokerBeforeAfter accept
- 08EEquativAd exchange · Paris · servers in Palo Alto, Frankfurt am MainAdvertisingBeforeAfter accept
- 09GGoogleAd network, analytics and search · Mountain View · servers in Dublin, Palo AltoAdvertisingBeforeAfter accept
- 10GGumGumContextual ads · Santa Monica · servers in DublinAdvertisingBeforeAfter accept
- 11IID5Shared ad identity · London · servers in RoubaixData brokerBeforeAfter accept
- 12IIndex ExchangeAd exchange · Toronto · servers in Toronto (Old Toronto), Frankfurt am MainAdvertisingBeforeAfter accept
- 13LLinkedInProfessional network and ad platform · Sunnyvale · servers in LondonAdvertisingBeforeAfter accept
- 14LLiveRampIdentity graph (data broker) · San Francisco · servers in Kansas CityData brokerBeforeAfter accept
- 15LLotameData platform (data broker) · Columbia, MD · servers in DublinData brokerBeforeAfter accept
- 16MMagniteAd exchange · Los Angeles · servers in Ashburn, LondonAdvertisingBeforeAfter accept
- 17MMicrosoftAd network and analytics · Redmond · servers in Doylestown, Seattle (South Lake Union)AdvertisingBeforeAfter accept
- 18OOpenXAd exchange · Pasadena · servers in Kansas CityAdvertisingBeforeAfter accept
- 19PPubMaticAd exchange · Redwood City · servers in Singapore, Palo AltoAdvertisingBeforeAfter accept
- 20QQuantcastAudience data and ads · San Francisco · servers in AshburnAdvertisingBeforeAfter accept
- 21RRTB HouseRetargeting ad network · Warsaw · servers in Amsterdam, PhoenixAdvertisingBeforeAfter accept
- 22SSeedtagContextual ads · Madrid · servers in Kansas CityAdvertisingBeforeAfter accept
- 23SSovrnAd exchange · Boulder · servers in DublinAdvertisingBeforeAfter accept
- 24TTeadsContent recommendation and video ads · New York · servers in London, ChicagoAdvertisingBeforeAfter accept
- 25TThe Trade DeskAd buying platform and identity (UID2) · Ventura · servers in Seattle (South Lake Union)AdvertisingBeforeAfter accept
- 26TTripleLiftAd exchange · New York · servers in Frankfurt am MainAdvertisingBeforeAfter accept
- 27YYahooAd network · New York · servers in LondonAdvertisingBeforeAfter accept
From our last check on 25 Oct 2026 from London: homepage only, three fresh visits (did nothing, clicked reject, clicked accept). Server locations are approximate, from the IP addresses we connected to. Some requests after rejecting may be strictly necessary services; this is what we observed, not proof that the site broke the law. How we check · Run this site? Ask for a re-check or add a statement
See this live on every site you visit
Browser Monster shows who’s watching on every page, what you agreed to, and helps you clear it up. It works on your device and never sells your data.
Add to ChromeCheck another site