๐งญ The Browser Being Analysed
Read from this tab right now. Every figure below describes this browser on this device.
See what this website can actually read from your browser — storage, cookies, tokens, permissions and which files came from your own cache. Everything runs locally; nothing is uploaded.
Read from this tab right now. Every figure below describes this browser on this device.
Run the analysis to see an exposure reading.
Every file this page loaded, and whether your browser reused a stored copy. A resource reporting zero bytes transferred but a non-zero decoded size came from your cache without touching the network — the one browser-cache fact that is genuinely observable.
Everything this origin can read. Values that look like secrets are masked — reveal them only if you are somewhere private. For another site's storage, use the Site Storage Inspector.
JWT-shaped values found in this origin's storage — and a decoder for any token you paste in. To find tokens another site is holding, run the Site Storage Inspector there.
Everything any page can read without asking you first — the raw material of fingerprinting. No single value identifies you; the combination very often does.
Feature detection, not fingerprinting — though the combination of answers is itself identifying.
Images this page loaded, with whether each came from the network or your cache.
Only this page's images — another site's can only be seen from inside it, via the Site Storage Inspector.
Nothing is requested automatically. Each test asks once, reports the answer, and immediately releases anything it was given.
Asks for your coordinates and reports the accuracy. Nothing is stored or sent.
Requests permission and reports the result. No notification is ever sent.
Opens the camera only long enough to confirm access, then stops the track immediately.
Confirms microphone access without recording. Any stream is stopped at once.
Asks to read your clipboard. The length is reported, never the contents.
Asks the browser to exempt this origin's storage from automatic eviction.
Lists your cameras and microphones. Names appear only after media permission is granted — a live demonstration of what consent unlocks.
This page can only read its own origin's data — that is the same-origin policy, and it is what stops any website reading your bank's session. The supported way around it is not to break the rule but to work inside it: run the same checks on the site you want to inspect.
Sixty seconds: install it once, then click it on any site.
It reads localStorage, sessionStorage and document.cookie for
whichever site you are on, flags anything JWT-shaped or named like a secret, and renders a small overlay
with the results. It makes no network request of any kind, and it removes itself when you close the panel.
The full source is in the Copy button above if you would rather read it before trusting it — which,
for anything you are about to run on a site you are logged into, is the right instinct.
Deliberately withheld from every website. If a page claims otherwise, it is guessing.
The same-origin policy means this page cannot read another site's localStorage, sessionStorage, IndexedDB, Cache Storage or ordinary cookies. Each origin is sealed off from every other.
Saved passwords, payment details and your complete history live in the browser's own storage, which page JavaScript has no access to. A page can read history.length for this tab, and nothing more.
An HttpOnly cookie is hidden from document.cookie on purpose — it is the main defence that stops a cross-site scripting bug from stealing a session. If your session cookie does not appear in the Cookies tab above, that is good news.
No page can enumerate the disk cache. The cache table above is inferred per-resource from timing data for this page only, plus anything a service worker explicitly put in Cache Storage.
Our CDN Cache Checker runs from a server, which means it can tell you whether a CDN edge answered a request — but it can never tell you whether your browser would have skipped the network entirely, because it has no browser cache to consult. This page is the other half of that question. Running here, in your tab, it can read the Performance API and see that a resource reported zero bytes transferred with a non-zero decoded size, which happens only when the browser served it from its own cache. That single measurement is the one piece of genuine browser-cache evidence available to any web page. Everything else on this page follows the same rule: it reports what the browser actually exposes to this origin, and states plainly what it is not allowed to know.
These tools all work on the same connection and address data — pick whichever question you actually have.
No. There is no network request in the analysis at all — you can confirm it by opening your browser's network tab and pressing the button. The Export button builds the JSON file locally too.
Because a well-built login cookie is marked HttpOnly, which hides it from JavaScript entirely. Its absence here is a sign the site is doing the right thing.
Anything in localStorage is readable by every script on the page, including any third-party script and anything injected through an XSS bug. A token there can be stolen silently; the same token in an HttpOnly cookie cannot.
The Performance API reports zero bytes transferred alongside a real decoded size, which can only happen when the browser reused a stored copy. Cross-origin resources without a Timing-Allow-Origin header hide their sizes, so those are reported as unknown rather than guessed at.
Exposure of this page's own origin — secure context, tokens reachable by script, secret-looking keys in storage. It is a prompt to look at specific findings, not a grade to chase.
Yes. Nothing is requested until you press a button, camera and microphone streams are stopped in the same function that opens them, and no location, audio or video is stored or transmitted.