Web Pages Cannot Read Cross-Origin Cookies
Because of the browser Same-Origin Policy, this page cannot directly read cookies belonging to claude.ai. Without the optional helper, session traces remain Unconfirmed.
The Browser Helper Reads Only Metadata
When explicitly authorized by you, the MV3 helper inspects only cookie names, domains, HttpOnly/Secure flags, and storage key names—immediately discarding any token values.
Name Matching Preserves Uncertainty
Matched names are grouped into auth, challenge, analytics, and preference categories. Partitioned cookies, other browser profiles, or opaque keys may not be covered.
Do Not Infer Account Status from Cookie Names
Seeing an auth cookie name does not prove the session is currently valid or restricted, and clearing local cookies cannot alter server-side account status.
Common Real-World Scenario
For example, an auth cookie name may belong to an expired session. The helper never sends requests to Claude to test the token and never claims you are actively signed in.
Check metadata and understand what local cleanup changes
An ordinary diagnostic page cannot read cookies belonging to Claude. If using the browser helper, verify its source and requested domain permissions before running a metadata check. Results should contain names, domains, attributes, or storage keys. Pasting sessionKey values, cookie contents, or login links is not part of this metadata workflow.
When a possible authentication marker is found, retain its category and source. Do not label it as a valid current session or proof of a ban. After a previous restriction, retained identifiers may be relevant to how a new account is assessed, but a name match cannot verify that effect or reconstruct the IP and language used during an earlier login.
If you choose to clear data, locate the relevant origin in the browser settings and check whether doing so will sign you out. Clearing Claude data differs from clearing this tool's history. The latter removes local test IPs and fingerprint summaries; it does not delete the provider's account records or constitute an unban action.
References & Freshness
The above is independent diagnostic guidance with no access to Anthropic internal risk controls. Policies, UIs, and support workflows may change—always verify against official effective dates and your account portal.