Skip to content
CookieTosser

What does nsf.gov track?

Before any consent, nsf.gov loaded 3 tracking companies and set 4 advertising or analytics cookies.

That's more tracking companies than 58% of the 2,450 sites we scanned.

Scanned October 2, 2026 from Germany, loading www.nsf.gov once and clicking nothing. How we scan

Tracking companies
3
Tracking cookies
4
Third-party hosts
9
Cookies in total
6

Consent banner

No known consent management platform was detected on the page.

Companies contacted before consent

3 of the 8 companies it contacted before consent were analytics companies.

Other third parties (content delivery, consent, functional, unclassified)

Cookies set before consent

The longest-lived tracking cookie it set was _ga, from Google Analytics, lasting about 13 months.

CookiePurposeSet byLasts
_ce.sAnalyticsnsf.gov12 months
_gaAnalyticsnsf.gov13 months
_ga_CSLL4ZEK4LAnalyticsnsf.gov13 months
_ga_YTMBPD5RB8Analyticsnsf.gov13 months
ADRUM_BTUnclassifiedwww.nsf.govUnder a day
aws-waf-tokenNecessarywww.nsf.gov4 days

The page also wrote 2 keys 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.