/web local tool
Browser Storage Capability Probe
Run active write, read, and delete checks in the current browser or iframe context, then export a reason-coded report without uploading values.
Local execution receiptinput path disclosedTool content stays out of MonoTools URLs and API requests.
- Working input
- Browser memory
- Cross-tool handoff
- Session only · 10 min
- URL payload
- Never
- Export
- Explicit action
Verify it: open DevTools Network, clear the log, use the tool, then inspect fetch/XHR requests. Page assets and optional aggregate analytics may use the network; tool input is not included.
Full privacy modelLoading tool...
01
How to use
- 01Open the page in the same top-level or iframe context as the application you are testing.
- 02Run the probe to create, verify, and remove temporary values in localStorage, sessionStorage, IndexedDB, and a CHIPS cookie candidate.
- 03Read each operation and reason code; Storage Access API inspection does not request permission.
- 04Copy the JSON report or adapt the bounded iframe snippet with an exact targetOrigin.
02
FAQ
- Does a pass prove storage survives reloads?
- No. A pass proves only that a temporary value could be written, read, and deleted in the current browser context. Reload durability, eviction, quota and future policy still need deployment testing.
- Can this prove an HttpOnly CHIPS cookie works?
- No. JavaScript cannot inspect HttpOnly cookies. The cookie check uses a short-lived script-readable Partitioned candidate; verify the real server-issued HttpOnly cookie through response headers and authenticated server behavior.
- Does it request Storage Access API permission?
- No. It only calls hasStorageAccess() when the page is embedded. Permission prompts and user-gesture flows must remain explicit in the application being tested.
- Does the probe send storage values to MonoTools?
- No. Temporary values stay in the current browser context, are removed after each check, and are omitted from the exported report.
03
Related tools
- →/webCookie Header InspectorParse Cookie and Set-Cookie headers, then validate policy.
- →/webHTTP Headers InspectorInspect HTTP syntax, policy conflicts and trust boundaries.
- →/webCSP BuilderBuild Content-Security-Policy headers with safe defaults.
- →/webcURL ConverterConvert cURL and match requests to local OpenAPI contracts.