Separate headers from consent
Set-Cookie attributes explain how the server asks browsers to handle cookies. They do not prove consent state, tracker purpose, or legal compliance.
Privacy and security · cookie attributes
Inspect redacted Set-Cookie headers for Secure, HttpOnly, SameSite, Partitioned, Domain, Path, prefix, and lifetime signals. The result keeps response evidence separate from consent, tracking, and legal claims.
No sample cookies, consent-compliance grade, security score, user-tracking claim, ranking impact, traffic claim, or manufactured cookie risk score appears before a live bounded response check.
Set-Cookie attributes explain how the server asks browsers to handle cookies. They do not prove consent state, tracker purpose, or legal compliance.
Session, authentication, and preference cookies usually deserve intentional Secure, HttpOnly, SameSite, path, domain, and lifetime decisions.
Some sites create cookies only after a GET request, JavaScript execution, or consent action. Use browser storage and network evidence for that deeper pass.
