Cookies Test

Are cookies and site storage working here?

Cookies

Detectingโ€ฆ

Status

Cookies enabled
โ€ฆ
First-party test
โ€ฆ
localStorage
โ€ฆ
sessionStorage
โ€ฆ
Detectingโ€ฆ enable JavaScript.

What are cookies?

Cookies are small notes a site asks your browser to keep โ€” login sessions, preferences, shopping carts. First-party cookies belong to the site you visit; third-party cookies belong to embedded services and are increasingly blocked by default.

What we test

We set a tiny first-party test cookie, write to localStorage and sessionStorage, then read them back โ€” all on this page, all deletable. Nothing is sent anywhere. If a check fails, your browser is set to block it (private window defaults, โ€œblock all cookiesโ€, or an extension).

How it works

Open this page and the embedded script queries only documented browser APIs. Nothing is installed, no account is needed, and results reflect your current browser profile โ€” including extensions, private mode and OS display scaling.

Limitations

Support varies by browser. Privacy features (tracking prevention, user-agent reduction, fingerprint randomization) can generalize or withhold values. Treat results as a best-effort live snapshot rather than a certified hardware inventory.

Privacy

Detection runs in your browser. We do not store fingerprints or device reports. The only network call any tool makes is the optional public-IP lookup on /my-ip (via a third-party IP API, disclosed in the privacy policy).

FAQ

Are cookies dangerous?

First-party cookies are mostly convenience. Risk comes from pervasive third-party tracking โ€” which modern browsers now restrict. Managing per-site permissions beats disabling everything.

Cookies vs fingerprinting?

Cookies can be deleted; fingerprints are re-derived. Blocking cookies does not stop fingerprinting, which is why browsers also generalize detectable signals.

Related tools

Related guides