What does rice.edu track?
Before any consent, rice.edu loaded 8 tracking companies and set 1 advertising or analytics cookie.
That's more tracking companies than 89% of the 2,450 sites we scanned.
Scanned October 2, 2026 from Germany, loading www.rice.edu once and clicking nothing. How we scan
- Tracking companies
- 8
- Tracking cookies
- 1
- Third-party hosts
- 29
- Cookies in total
- 9
Consent banner
The page loaded CookieYes, a consent management platform. Everything below was recorded before anyone answered it. 8 tracking companies still loaded while it was unanswered.
Companies contacted before consent
4 of the 16 companies it contacted before consent were analytics companies.
- MNTN (SteelHouse)7 requestsAdvertising
px.mountain.com, dx.mountain.com, gs.mountain.com
- Google Ads7 requestsAdvertising
ep2.adtrafficquality.google, ep1.adtrafficquality.google, ad.doubleclick.net, pagead2.googlesyndication.com
- The Trade Desk5 requestsAdvertising
js.adsrvr.org, insight.adsrvr.org, match.adsrvr.org
- YouTube6 requestsSocial media
www.youtube.com, img.youtube.com
- Amplitude2 requestsAnalytics
cdn.amplitude.com
- Siteimprove2 requestsAnalytics
siteimproveanalytics.com, 6343607.global.r2.siteimproveanalytics.io
- Google Analytics1 requestAnalytics
www.googletagmanager.com
- Ahrefs1 requestAnalytics
analytics.ahrefs.com
Other third parties (content delivery, consent, functional, unclassified)
- 44.238.122.1721 requestUnclassified
44.238.122.172
- 52.71.121.1701 requestUnclassified
52.71.121.170
- CookieYes8 requestsConsent banner
cdn-cookieyes.com, log.cookieyes.com
- Google9 requestsFunctional
www.google.com, cse.google.com, clients1.google.com
- AddToAny3 requestsFunctional
static.addtoany.com
- Bunny.net22 requestsContent delivery
staticws.b-cdn.net
- jsDelivr10 requestsContent delivery
cdn.jsdelivr.net
- Font Awesome2 requestsContent delivery
kit.fontawesome.com, ka-p.fontawesome.com
Cookies set before consent
The longest-lived tracking cookie it set was guid, from MNTN (SteelHouse), lasting about 12 months.
| Cookie | Purpose | Set by | Lasts |
|---|---|---|---|
| guid | Advertising | mountain.com (third party) | 12 months |
| cookieyes-other | Unclassified | rice.edu | 12 months |
| cky-consent | Functional | rice.edu | 12 months |
| cookieyes-advertisement | Functional | rice.edu | 12 months |
| cookieyes-analytics | Functional | rice.edu | 12 months |
| cookieyes-functional | Functional | rice.edu | 12 months |
| cookieyes-necessary | Functional | rice.edu | 12 months |
| cookieyes-performance | Functional | rice.edu | 12 months |
| cookieyesID | Functional | rice.edu | 12 months |
The page also wrote 1 key to local storage, which works like a cookie but isn't sent with requests.
Understanding this page
- How to see which cookies and trackers a website loads
A hands-on walkthrough for checking what a site sets before you've clicked anything, using Chrome and Firefox's built-in tools, plus how CookieTosser automates the same check every month.
- What counts as valid cookie consent in the EU
The rules that actually govern cookie banners — the ePrivacy Directive, the GDPR consent standard, the Planet49 ruling, the strictly-necessary exemption, and what "reject" has to offer compared with "accept.
- Consent management platforms explained
What a CMP banner is actually doing behind the scenes, how the IAB's TCF standard and Google's Consent Mode v2 fit in, and why a banner being present is no guarantee that nothing loads before you answer it.