What is the __Host-next-auth.csrf-token cookie?
Used to help with site security in preventing Cross-Site Request Forgery attacks.
Our October 2026 scan found it on 5 sites (0% of the 2,450 we scanned), set before any consent.
- Purpose
- Functional
- Belongs to
- NextAuth.js
- Set as
- First-party (under the site's own domain)
- Typical lifetime
- Session (vendor says: session)
Sites that set __Host-next-auth.csrf-token before consent
The highest-ranked 5 of 5 sites.
- drpc.org6 tracking companies
- docusign.com9 tracking companies
- myfitnesspal.com1 tracking company
- marksandspencer.com10 tracking companies
- nifty.com32 tracking companies
How to stop it
Declining non-essential cookies in a site's consent banner should stop __Host-next-auth.csrf-token being set on later visits. Blocking third-party cookies in your browser settings stops the third-party kind everywhere, and clearing cookies for a site removes any it already set.
Description from the Open Cookie Database (Apache 2.0).
Understanding this page
- How cookie lifetimes work, and why a 13-month _ga matters
What a cookie's "expires" field actually controls, why Google Analytics ships a 2-year default that many sites cut down to 13 months, and how Safari's 7-day cap on script-set cookies changes the picture.
- First-party vs third-party cookies (and why "first-party" still tracks you)
What the distinction actually means technically, why browsers only block one of the two, and how CNAME cloaking, server-side tagging and cookies like _ga let sites keep tracking under their own domain.
- How to block or limit trackers
Browser privacy settings, content blockers, Global Privacy Control and clearing cookies compared honestly — what each one actually stops, what it doesn't, and what it costs you in return.