Secret Detector & Redactor
Paste text, code or logs to find AWS, GCP, GitHub, Slack and Stripe keys, JWTs, private keys, URL credentials and high-entropy tokens. Get a report and a redacted copy.
Use the tool
Why this tool exists
Secrets end up in places they should not be: a stack trace pasted into a ticket, a config snippet shared in chat, a log sent to a vendor. Once a key is in a public gist or a support thread, you have to treat it as leaked and rotate it.
This tool is a quick check before you share anything. It matches well-known key formats, flags private key blocks, credentials inside URLs and generic high-entropy strings, and lists each hit with its line and column. The redacted version replaces the values with labels, masks or stable pseudonyms. Scanning is pattern based and local, so it helps but cannot promise to find every secret.
How to use it
- Paste the text, code or log lines into the input box.
- Choose the redaction style (label, mask or pseudonym) and how many trailing characters to keep.
- Decide whether to flag generic high-entropy tokens and whether to show the report, the redacted text or both.
- Run the tool, review the findings and copy the redacted text.
Frequently asked questions
What kinds of secret does it find?
AWS, GCP, GitHub, Slack and Stripe keys, JSON web tokens, private key blocks, credentials inside URLs and, optionally, generic high-entropy tokens. It works from patterns, so unusual formats can be missed.
If I redact a leaked key, is it safe?
No. If a real secret was ever pasted somewhere public or shared, rotate it. Redaction only protects the copy you share next.
Why are some harmless strings flagged?
The high-entropy option flags long random-looking strings such as hashes or IDs. Untick it if you get too many false positives, and always read the report before trusting it.
Is my text uploaded?
No. Detection and redaction run in your browser, and nothing is sent to a server. Avoid pasting live production secrets into any page you do not trust.