Paste the exact text you plan to share
Use the final artifact, because secrets can reappear after another log export, configuration merge, or copied request header.
Check code, logs, configuration, and HTTP transcripts for common credential shapes before sharing. Detection and redaction run in this browser, and no input is uploaded.
Add the exact code, log, configuration, or transcript you plan to share.
Review every line. A clean pattern scan cannot prove that text is safe.
This secrets tool keeps input local, but its result still needs the human review described in the steps below before it is shared or used.
Use the final artifact, because secrets can reappear after another log export, configuration merge, or copied request header.
The scanner reports categories and counts without repeating detected values in its summary. Open the redacted preview to verify that technical context remains useful.
Replace likely credentials with explicit labels, then manually check personal data, internal identifiers, signed URLs, and application-specific secret formats that pattern matching may miss.
Pattern matching produces both false positives and false negatives. It cannot prove that text is safe, determine whether a token is live, inspect external files, or replace a repository scanner, data-loss prevention system, or human review.
Before sharing the secrets result, read Secret scanning before sharing for the matching context and privacy checks.
Privacy, limits, and correct interpretation.
No. Detection, categorization, preview, and replacement run locally in this browser.
It checks common private-key blocks, AWS keys, GitHub and Slack tokens, JWTs, bearer headers, database credential URLs, and common assigned credential names.
No. Custom token formats, personal data, business identifiers, and transformed secrets may not match. Review the complete text yourself.
No. If a real credential was exposed anywhere, revoke or rotate it in the system that issued it.
Choose another browser tool only when the next task changes from free local secret scanner and redaction tool to formatting, comparison, encoding, or measurement.
Pretty-print compact JSON, minify a valid document, or locate a syntax error without uploading the input. The formatter runs entirely in this browser.
Open tool →Compare an original and changed block line by line without sending either version to the server. Use the result for a quick inspection, not as a replacement for version-control history.
Open tool →Convert UTF-8 text to Base64 or decode a Base64 value locally. Base64 is a transport representation, not a confidentiality or access-control mechanism.
Open tool →Measure visible writing and actual UTF-8 storage size as you type. Counts update locally and help you check a text block before creating a paste.
Open tool →Percent-encode a URL component or decode an encoded value without uploading it. Use this tool for query values, paths, callback parameters, and sanitized HTTP examples.
Open tool →Inspect the Base64URL-encoded header and payload of a three-part JSON Web Token in this browser. The decoder never verifies the signature and never proves that a token is authentic or safe to trust.
Open tool →Convert Unix seconds, Unix milliseconds, or an ISO 8601 date into UTC, local time, seconds, and milliseconds. Processing stays in the browser for safer log analysis.
Open tool →Create a lowercase SHA-256 digest from the exact UTF-8 bytes of a text block. Hashing runs through the browser Web Crypto API and does not upload the input.
Open tool →Prepare a text list or copied diagnostic block locally by trimming trailing spaces, compacting blank lines, removing duplicate lines, or sorting lines. Every action changes text, so review the result before replacing a source artifact.
Open tool →