/crypto local tool
Secret Scanner
Detect tokens, private keys and high-entropy values, then create a redacted copy.
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
- 01Paste a log, .env file, stack trace, config snippet or HTTP transcript.
- 02Review the exposure radar, severity groups and line/column findings.
- 03Copy the redacted output or incident notes before sharing the text.
02
FAQ
- Does this replace repository secret scanning?
- No. It is a fast local pre-flight check for pasted text. Keep using server-side and CI secret scanners for full repository and history coverage.
- Will it upload my logs or secrets?
- No. Pattern matching, entropy scoring and redaction run inside your browser with React state only.
- Why does it flag high-entropy strings?
- Many generated tokens look random. Entropy is a heuristic, so review the context before rotating credentials.
guides
Guides
Authentication debugging6 min read
How to Inspect a JWT Locally Without Uploading It
Read JWT header and payload claims locally, check exp, iss and aud, and learn why decoding is not the same as signature verification.
Read guide →Secure debugging7 min read
How to Remove Secrets from Logs Before Sharing
Scan logs and configuration snippets for credentials, create a redacted copy, and respond correctly when a real secret is found.
Read guide →03