Can this guarantee my logs are safe to share?

No. This is a heuristic pattern matcher, not a security audit. It can miss secrets that don't match a known format and can flag things that aren't actually sensitive. Always review the findings and the redacted output yourself before sharing.

Secret Detector & Redactor

Q: Is anything I paste here uploaded or saved?

No. Detection and redaction run entirely client-side with regular-expression pattern matching. The input is never sent to a server, added to the URL, saved to local storage, or logged to analytics.

Q: What's the difference between conservative and aggressive mode?

Conservative mode only reports high-confidence patterns (private keys, AWS/GitHub/Slack/Stripe/Google keys, JWTs, bearer tokens, connection-string credentials) that are unlikely to be false positives. Aggressive mode adds broader, noisier patterns — generic key/password-named assignments, emails, and IP addresses — that need more manual review.

Q: How does consistent redaction work?

Every occurrence of the exact same secret value anywhere in the input is replaced with the same numbered placeholder (like [REDACTED-JWT-1]), so you can still see that the same token repeats without revealing what it is.

Paste code, a log excerpt, a .env file, or config below. Detection and redaction happen entirely in your browser using pattern matching — nothing is uploaded, put in the URL, saved, or sent to analytics.

Pattern matching, not a guarantee

This tool flags strings that look like secrets. It will miss secrets that don't match a known pattern (false negatives) and may flag things that aren't actually sensitive (false positives) — especially in Aggressive mode. Always review findings before trusting them.

Detection mode

Conservative (high-confidence only)

Aggressive (more patterns, more noise)

Input

Nothing to scan yet — paste some input above.

Secret detection examples

Scan realistic context, then review both matches and the redacted output before sharing.

Repeated bearer token

Authorization: Bearer example_token_1234567890

Every identical occurrence receives the same numbered placeholder.

Database URL credentials

postgres://demo:example-password@db.example.invalid/app

Embedded username and password material is treated as a high-confidence credential pattern.

Common mistakes

Assuming no matches means the text is safe.
Publishing redacted output without reviewing context.
Using aggressive mode without accounting for false positives.

How to redact production logs before sharing Browse log and privacy tools

Examples and guidance reviewed July 19, 2026.

Secret Detector & Redactor

Secret detection examples

Common mistakes

FAQ

Is anything I paste here uploaded or saved?

What's the difference between conservative and aggressive mode?

Can this guarantee my logs are safe to share?

How does consistent redaction work?