Developer tools for security engineers
Find leaked secrets and PII, sanitize debugging artifacts, and verify signatures before anything is shared — all locally, so sensitive material never leaves your machine.
Run the Log Sanitizer workflow → Browse security tools →
Launch a tool
Tip: press 1–8 to open one- 1Secrets ScannerDetect API keys, tokens, and credentials in payloads.
- 2PII DetectorFind and redact personally identifiable information.
- 3HAR SanitizerRedact secrets, export Postman / cURL / fetch packs.
- 4JWT DecoderDecode JWTs locally and verify HMAC signatures with a supplied secret.
- 5Webhook VerifierVerify Stripe / GitHub / Slack HMAC signatures.
- 6Hash GeneratorMD5, SHA-1, SHA-256, SHA-512 — hex or Base64.
- 7Certificate & PEMDecode X.509 certs, inspect CSRs, split PEM bundles.
- 8Phishing Link & Email InspectorCheck suspicious links, domains, senders, and raw email headers locally.
Run a workflow right here
Runs locally — nothing is uploadedLog Sanitizer (PII + secrets)
Redact PII (emails, phones, cards) and then scan the redacted text for likely secrets. Best-effort local checks.
pii-detector-redactor → secrets-scannerSnippet Redact, Scan & HAR Handoff
Paste a request/response snippet to redact PII and flag secrets, then hand off to the HAR Sanitizer for whole-HAR-file cleanup.
pii-detector-redactor → secrets-scanner → har-sanitizerBase64 Payload Secret Scan
Base64-decode an opaque payload and scan the decoded text for secrets and tokens.
base64-tool → secrets-scannerTrack a checklist
Progress is saved on this deviceDaily tasks, guides & FAQ
Common daily tasks
- Remove secrets/PII before sharing logs
- Sanitize HAR files before sending to vendors
- Verify webhook signatures
- Inspect JWT claims safely
- Check certificate expiry/subject
- Generate hash digests for verification
Recommended workflows
- Log Sanitizer — redact PII then scan for secrets.
- HAR Redact Prep — snippet redact and scan, then HAR Sanitizer.
- Base64 Decode Secret Scan — decode a Base64 payload and scan for secrets.
- JWT Claims Secret Scan — decode JWT claims and flag secrets.
Top tools
Secrets Scanner
Scan logs, payloads and config for exposed API keys, tokens and passwords.
Scan for secrets →PII Detector & Redactor
Detect and redact emails, phone numbers, IP addresses and card numbers from text.
Redact PII →HAR Sanitizer
Redact cookies, tokens and Authorization headers from HAR files before sharing.
Sanitize a HAR file →Webhook Signature Verifier
Recompute Stripe/GitHub/Slack/custom HMAC signatures to debug mismatches.
Verify a webhook →See the full security & debugging tool cluster →
Why browser-local matters for security engineers
Security work means handling logs, tokens, HAR captures and signing secrets that must not be exposed. Everything runs 100% in your browser — no analytics scripts, no cookies, no third-party requests. We count anonymous visits at the CDN edge only. That means you can scan and redact sensitive material without trusting a third-party server.
FAQ
Is sensitive data uploaded when I scan for secrets?
No. Everything runs 100% in your browser — no analytics scripts, no cookies, no third-party requests. We count anonymous visits at the CDN edge only. Logs, tokens, and PII are scanned in memory and never sent to a server.
How do I remove secrets from a log before sharing it?
Run the Secrets Scanner (or the Log Sanitizer workflow) to detect and mask API keys, tokens and passwords, then copy the redacted output.
Should I sanitize a HAR file before sending it to support?
Yes. HAR files contain cookies, Authorization headers and request bodies; the HAR Sanitizer redacts them locally before you share the file.
Can I redact PII like emails and credit-card numbers?
Yes. The PII Detector & Redactor finds emails, phone numbers, IP addresses and Luhn-valid card numbers and masks them, all in your browser.
Related
- API developers — decode tokens, verify webhooks, debug responses.
- Support & escalation engineers — make anything safe to paste into a ticket.
- Security and debugging tools — the full tool cluster.
- Sanitize a HAR file before sharing it with support