BrowserCheck · Browser environment diagnostics
Test actual first-party cookie, localStorage, sessionStorage and IndexedDB write/read operations with temporary markers and verified cleanup.
A browser can report cookies enabled while a specific storage operation still fails. This test writes a random temporary marker, reads it back and checks cleanup for first-party cookies, localStorage, sessionStorage and IndexedDB. Each run uses its own names and leaves other site data alone.
Running local checks…
Copied and printed output omits IP addresses, the full User Agent, exact versions, fingerprint hashes, and precise location.
The script sets a short-lived SameSite=Lax cookie on this origin, reads its value and deletes it. Because cookie assignment has no success return, write acceptance is verified through the readback rather than assumed from navigator.cookieEnabled.
Each storage API is tested independently. A successful write is followed by an exact value check, removal and an absence check. The test never calls clear() or deletes unrelated keys.
The test creates a temporary database, commits a write transaction, reads the marker in a separate transaction, closes the database and requests deletion. Timeouts and blocked cleanup are reported rather than hidden.
Write, read and cleanup are shown individually. Available means all stages completed. A policy rejection is labelled blocked when the API reports it; an unexplained mismatch is not attributed to a specific setting.
No. It removes only the random marker and temporary database created by this run. It does not clear the origin's other data or Lab markers.
navigator.cookieEnabled is a broad browser report. Policy, context and implementation behavior can still prevent this page's particular write/read operation.
No. The cookie is set and read by the top-level BrowserCheck origin. Third-party and cross-site behavior needs a separate test setup.