Skip to content
Browse tools

Site Storage Inspector

One click shows you exactly what any website is storing in your browser — localStorage, sessionStorage, cookies and login tokens. Works on sites you're signed into, and nothing ever leaves your machine.

🔖 Storage Inspector
Drag the button above to your bookmarks bar — clicking it here won't do anything useful. Makes no network request. Nothing is sent to us or anyone else.
Why this exists. A web page can only read its own site's data — that's the same-origin policy, and it's what stops a random site reading your bank's session. So our Browser Privacy & Storage Analyzer can only ever show you our storage. This bookmarklet doesn't break that rule — it works inside it, by running the same checks on the site you're actually looking at.

📖 Setting It Up

Takes about thirty seconds, once. Watch it first if you'd rather see the whole thing before installing anything.

The whole thing end to end — drag it to the bar, open a site, click once.

StepWhat to do
1
Show your bookmarks bar
Press Ctrl+Shift+B on Windows, or +Shift+B on a Mac. In Safari it's View → Show Favourites Bar.
2
Drag the 🔖 button onto it
Drag, don't click. It becomes a normal-looking bookmark that happens to hold code instead of a web address.
3
Go to the site you want to inspect
Somewhere you're signed in is the interesting case — that's where tokens and session data actually live.
4
Click the bookmark
A panel appears in the bottom-right listing everything that site has stored. Click Close and it removes itself completely.

🔍 What It Shows You

localStorage
Data the site keeps permanently — it survives closing the browser entirely.
sessionStorage
Data that disappears when you close the tab.
Cookies
Only the ones JavaScript is allowed to read. HttpOnly cookies stay hidden — see below.
JWT tokens
Anything shaped like a login token gets flagged, so you can see whether the site is leaving credentials somewhere scripts can reach.
Likely secrets
Keys named like token, auth, session or api_key are marked and their values masked.

🚫 What It Still Can't Show

Running inside a site widens what's readable — it doesn't remove every limit.

HttpOnly cookies
Hidden from all JavaScript by design. If a site's session cookie doesn't appear, that's the site doing security properly.
Saved passwords
Live in the browser's own vault, which no page can touch.
Browsing history
A page can count entries in the current tab and nothing more.
Other sites
Still one site at a time. Run it again on the next site.
The disk cache
No page can enumerate it, anywhere, ever.

🛡️ Is This Safe?

A fair question, and one you should be asking about any bookmarklet.

Makes any network requestNo — none at all
Sends data to usNo
Changes anything on the siteNo — read only
Stays after you close itNo — removes itself
Masks secret-looking valuesYes, by default
Source you can read firstYes — below
Be careful with bookmarklets generally. One runs with full access to whatever site you're on, so a malicious one could read your session and send it away. Attackers exploit exactly this — it's called self-XSS, and it's why browser consoles print those big red "don't paste anything here" warnings. Ours is about twenty lines and does nothing but read and display. Read it below before you trust it, and apply the same suspicion to any bookmarklet anyone hands you, including this one.
Read the full source

                

🧰 If It Doesn't Work

Nothing happened
Some sites use a strict Content-Security-Policy that blocks bookmarklets. Nothing is wrong with the bookmark — that site simply refuses it.
Firefox did nothing
Firefox blocks javascript: typed or pasted into the address bar. Dragging it to the bookmarks bar works fine.
Dragging won't work
Use Copy the code, then create a bookmark manually and paste it into the URL field instead of an address.
The panel is empty
That site genuinely stores nothing readable. Common on static sites, and on sites that correctly keep their session in an HttpOnly cookie.
On mobile
Bookmarklets are awkward on phones. This one is really a desktop tool.
HOW IT WORKS

A Bookmark That Holds Code Instead of a Link

An ordinary bookmark stores a web address. A bookmarklet stores JavaScript, and clicking it runs that code on the page you're currently viewing rather than navigating anywhere. That single difference is what makes this work: the browser treats the code as belonging to whatever site you're on, so localStorage means that site's localStorage. Nothing is bypassed and no rule is bent — the code simply runs where the data already lives, with your explicit click as the trigger. It's an old technique; the "save to Pocket" and "share to" buttons people have kept in their bookmarks bar for years work exactly the same way. Ours reads the three storage areas, flags anything shaped like a JWT or named like a secret, masks those values, renders a panel, and removes itself when you close it. No network call is made at any point, which you can confirm from the source above or by watching your own network tab while it runs.

What else can you check?

These tools all work on the same connection and address data — pick whichever question you actually have.

Want to see the full path to a site? DNS, redirects, every hop, the CDN, TLS and the origin server. Want to know your public IP? See your IPv4 and IPv6 addresses, location, ISP and ASN. Want to check your tower & route? Live ping, speed, DNS, traceroute and a map of nearby points. Want to ping from around the world? Real latency from real probes across 12 countries, live on a map. Want to locate any IP address? City, region, country and coordinates for any public IP. Want to know if an IP is risky? Proxy, VPN, Tor, hosting and abuse-report indicators. Want to know if you're blacklisted? Check an address against major spam and abuse DNSBLs. Want to know who owns an IP? Network owner, ASN, CIDR range and abuse contact. Want to explore an AS number? Announced prefixes, BGP neighbours and registry details. Want to test your connection speed? Measure real download, upload, ping and jitter. Want to see what changed? Word-level diff between two blocks of text or code. Want to know if a DNS change is live yet? Compare answers from five independent public resolvers. Want to verify a domain's nameservers? Direct authoritative checks, glue records and SOA serials. Want to check a domain's DNSSEC setup? DNSKEY, DS records, signature expiry and real validation. Want to see the hop-by-hop path to a server? A real traceroute from a genuine probe anywhere in the world. Want to know if a server port is open? A real TCP connection attempt - open, closed or filtered. Want to measure latency to a server? Real connect timing - min/avg/max, jitter and connection loss. Want a clean URL slug from a title? Real transliteration, stop words and batch mode. Want to find and replace across a document? Regex, capture groups and a live preview before you commit. Want to find the invisible character? Code points, escapes, bytes and hidden-character detection. Want to escape text for HTML? Minimal, named or numeric entities, attribute-safe. Want to strip emoji cleanly? Whole clusters - no half-flags or stray modifiers left. Want to spot repeated words? Frequency, density and accidental doubles like "the the". Want to know if a URL is cached? Two requests prove whether your CDN is really caching it. Want to see what a site knows about you? Storage, cookies, tokens and what your browser actually cached. Want to know who your site talks to? Renders the page and names every outside company it contacts.
COMMON QUESTIONS

Site Storage Inspector FAQ

What is a bookmarklet?

A bookmark that stores JavaScript instead of a web address. Clicking it runs that code on the page you're currently viewing. It's a long-established technique — many "save this page" buttons work this way.

Does it send my data anywhere?

No. It makes no network request of any kind. The full source is on this page so you can verify that yourself rather than taking our word for it.

Is it safe to use on my bank?

This one only reads and displays, and you can check that in the source. But the honest general answer is: be very cautious running any bookmarklet on a sensitive site, because one genuinely could steal your session. Read the code first — every time, from anyone.

Why can't the main analyzer page just do this?

Because it isn't that site. A page can only read its own origin's storage, which is what prevents any website from reading your logged-in sessions elsewhere. Moving the code to the site is the supported way to widen what's visible.

Why don't I see the login cookie?

It's almost certainly marked HttpOnly, which hides it from all JavaScript. That's the correct way to store a session, and its absence here is a good sign.

Can I use it on my own site while developing?

Yes, and that's a good use for it — a quick way to check what your app is leaving in localStorage without opening devtools, especially on a device where devtools is awkward to reach.