Am I Blocking Cookies
Cookie blocking
Checking…
Tests navigator.cookieEnabled and a first-party write on this origin. Third-party cookie blocking is separate.
How to use
- Open the page on the site you want to audit — the answer appears immediately.
- Read cookieEnabled and the first-party write test in Details.
- Change browser cookie settings, then Refresh to see if the result changed.
FAQ
Am I blocking cookies?
You are blocking (or cookies are disabled) if navigator.cookieEnabled is false or this page cannot write and read back a small test cookie on the current origin. Otherwise cookies work for this site at the first-party level.
I block third-party cookies — does that count?
Not for this test. Safari Intelligent Tracking Prevention and Chrome third-party cookie phase-out restrict cross-site cookies separately. This tool only tests whether this website’s own origin can set cookies.
Why do sites break when cookies are blocked?
Logins, carts, language preferences, and consent banners often store session IDs in first-party cookies. Blocking them causes logout loops or empty carts.
What is navigator.cookieEnabled?
A boolean that reports whether the browser allows cookies at all. It can be false due to settings, enterprise policy, or private modes with restrictions.
Can extensions block cookies?
Yes. Privacy extensions may strip cookies even when the browser setting looks enabled. Disable extensions temporarily and refresh to compare.
Is the test cookie kept?
The probe sets a short-lived name and removes it immediately after the read check. It is only for detection on this page.
Introduction
Am I Blocking Cookies tells you whether this website can use first-party cookies in your current browser profile — the kind that keep you signed in, remember preferences, or hold a shopping cart. The answer appears as soon as the page loads: cookies work, or they appear blocked/disabled.
Cookie confusion is everywhere: global “block all cookies,” per-site shields, Safari cross-site rules, and GDPR banners. When something fails silently, the first question is whether the browser still allows a cookie from this origin. This tool answers that without opening DevTools.
What we test
| Step | What it verifies |
|---|---|
| navigator.cookieEnabled | Browser-wide cookie permission flag |
| Write + read probe | A test cookie can be set on this origin and read back |
| Headline: No | Both checks passed — first-party cookies work here |
| Headline: Yes (blocking) | Setting disabled or write failed |
First-party vs third-party
- First-party — cookies for the same site you are visiting (what this tool tests).
- Third-party — cookies in cross-site iframes or trackers; controlled by separate browser features (not fully tested here).
You can pass this page but still block trackers on other domains.
Common use cases
- Login loops — confirm cookies work before blaming the password.
- E-commerce QA — verify cart persistence on staging.
- After tightening privacy — see if “block all cookies” broke only some sites.
- Support — send users this link on the failing domain.
Best practices
- Run the test on the exact origin that fails (
wwwvs bare domain can differ). - Toggle per-site cookie settings in the lock icon, then Refresh.
- For permissions (camera, etc.), see what permissions have I granted.
- For all cookies including HttpOnly, use browser DevTools → Application → Cookies.