>
BunchTool — Cookie Checker
🔗 Share
↺ Reset
🍪 Cookie Actions
Cookies Enabled: Checking…

Reads navigator.cookieEnabled to verify whether cookies are permitted for this browser session.

The test token (BunchToolTest) expires automatically after 10 minutes and stores no personal data.

📋 Active Cookies for This Domain

JavaScript-readable cookies currently set for this domain, parsed from document.cookie. HttpOnly cookies are intentionally hidden by the browser.

Related Tools

More free privacy tools


🛡️ Hardware & Privacy Tools

Cookie Checker —
Test Cookie Support & View Active Domain Cookies Free

Instantly verify whether your browser has cookies enabled, list every JavaScript-readable cookie currently set for this domain, and write or delete a safe temporary test token — all with BunchTool's free Cookie Checker, running 100% client-side in browser RAM.

Reads navigator.cookieEnabled to instantly verify browser cookie permissions
Parses document.cookie to list all same-origin readable cookies per domain
Writes a temporary BunchToolTest token with 10-minute expiry for live write/delete testing
100% private — no cookie data is ever transmitted to any external server
🍪
InstantPermission Check
100% LocalRAM Process
Zero UploadCookie Data
How It Works

Check and test cookies in three easy steps

Step 1
🍪
Auto-Check Cookie Permissions

The tool instantly reads navigator.cookieEnabled and reports whether cookies are verified enabled or blocked by browser policy or privacy extensions.

Step 2
✍️
Write or Delete a Test Cookie

Click Set Temporary Test Cookie to write a BunchToolTest token that expires in 10 minutes. Click Clear Test Cookie to delete it instantly via Unix epoch expiry.

Step 3
📋
Inspect Active Domain Cookies

The right panel parses document.cookie and lists every JavaScript-visible cookie set for this domain. HttpOnly cookies are correctly excluded as per browser security rules.

Why BunchTool

Why use our free Cookie Checker tool?

🔑
Live Cookie Permission Probe

Uses navigator.cookieEnabled to instantly return a boolean permission status — detecting cookies blocked by ITP, browser flags, or privacy extensions in real time.

✍️
Safe Write & Delete Token Testing

Writes a harmless BunchToolTest token to document.cookie with a 10-minute TTL, then deletes it by setting expiry to Thu, 01 Jan 1970 — the standard Unix cookie deletion mechanism.

🔒
Same-Origin Sandbox — Zero Leakage

All cookie reads and writes execute inside browser RAM via JavaScript. Cookie data never leaves your device — enforced by browser same-origin policy and our zero-server architecture.

FAQ

Frequently asked questions

What does navigator.cookieEnabled actually check?
navigator.cookieEnabled returns a boolean indicating whether cookies are enabled in the browser. It does not check per-cookie attributes like HttpOnly or SameSite — only whether the cookie API is functional.
Why can I only see some cookies and not others?
Browser same-origin policy restricts document.cookie to cookies set with a matching domain and path. Cookies flagged as HttpOnly are also invisible to JavaScript — they are transmitted by the browser in HTTP headers only.
What is the BunchToolTest cookie and is it safe?
BunchToolTest is a harmless temporary token written by this tool with a 10-minute expiry. It stores no personal data and is deleted the moment you click 'Clear Test Cookie' or when the expiry elapses automatically.
Can I see cookies set by other websites?
No. Browser same-origin policy enforces strict cookie isolation. JavaScript on bunchtool.com can only read cookies explicitly scoped to the bunchtool.com domain.
Is this tool completely private?
Yes. All analysis metrics and utility functions for the Cookie Checker process data locally inside your web browser. Zero user inputs or URLs are stored or tracked.
Detailed Guide

Understanding Browser Cookie Mechanics: navigator.cookieEnabled, document.cookie Parsing, HttpOnly Isolation & Same-Origin Policy

navigator.cookieEnabled is a read-only boolean exposed by the W3C Navigator API. It returns true if the browser's cookie jar is accessible to the active origin and false if cookies are blocked by browser flags (e.g. Chrome's Block third-party cookies), OS-level parental controls, or privacy extensions like uBlock Origin. Crucially, it reflects the top-level same-origin cookie policy — not the attribute-level restrictions imposed by HttpOnly or SameSite.

document.cookie exposes the serialised cookie string for the current document's origin. Each cookie is a name=value pair delimited by semicolons. This tool splits the string on ; and trims whitespace to display each pair on its own line. Cookies written by the server with the HttpOnly flag are intentionally hidden from document.cookie — a security mechanism that prevents XSS attacks from exfiltrating session tokens.

Cookie deletion via Unix epoch is the standard cross-browser mechanism: setting expires=Thu, 01 Jan 1970 00:00:00 UTC forces the browser to immediately purge the named cookie, because the expiry timestamp is in the past. This tool writes a harmless BunchToolTest=ActiveCookieToken token with a 10-minute TTL (now + 600,000ms) and deletes it by resetting the expiry to the Unix epoch — zero server involvement at any stage.

Other Collections

Explore other useful categories

Explore 247 more free tools —
no login, no limits.

BunchTool covers PDF editing, text conversion, SEO analysis, calculators, design tools, unit converters and much more. All 100% free, all browser-based.

Browse All 247 tools →