
Developers and reviewers can examine pasted text before sharing it when they suspect that a key or token may have been left behind.
Catch keys and tokens accidentally left in a body of text, helping reviewers identify sensitive elements before the content is shared.
With an excerpt containing an api_key line and an example password, the tool flags patterns that look like secrets. Review each alert to decide whether it is a real sensitive value or just a sample, then remove anything that should not circulate.
Input
api_key = AKIAIOSFODNN7EXAMPLE
password = example123The analysis runs entirely in your browser. The text you paste stays on your device and is not sent to any external service. You can inspect an excerpt before sharing it, without an account or storage.
Open the context around the match and check whether the string really looks like a key or token. Variable names, documentation examples and test identifiers can trigger an alert. If it is a false positive, note it and continue your review.
Yes, you can paste an excerpt or import a supported text file. For a large file, start with sensitive sections such as credentials, tokens and environment variables. Remove any real data before sharing the result.
No, it only flags them in the analysed text. You must remove the value, revoke the exposed key and fix the source file. If a secret was already published, treat it as compromised and replace it.