Home › Log Redactor
Redact a log before you share it
Direct answer: paste the excerpt below and press Redact secrets. Cloud keys,
tokens, passwords, session IDs, emails, IPs and checksum-valid card numbers are replaced with typed placeholders
like <token> — locally, in your browser. For whole files, the
Error Grouper's "download redacted log" action streams instead.
Redact this log excerpt
Redacted output
What was replaced
| Pattern class | Replacements |
|---|
Redaction is pattern-based: it catches known secret shapes (keys, tokens, cards that pass a checksum). It cannot catch a secret in an unusual shape — read the output once before sharing.
Why this exists as its own tool
The moment a log leaves your machine — into a support ticket, a team chat, a GitHub issue, a forum post — its secrets leave with it, and logs are dense with secrets: authorization headers, session IDs in URLs, the API key someone helpfully logged at startup. The full checklist of what to look for, and where logs hide it, is in redact logs before sharing. This tool is the fast path for the common shapes; the checklist is the safety net for the rest.
Frequently asked questions
What exactly gets replaced?
Private-key headers, JSON Web Tokens, AWS-style access keys (AKIA/ASIA), Bearer and Basic/Digest authorization values, key=value pairs for password/passwd/pwd, api-key, secret and token fields, session IDs in URLs and key=value form, email addresses, IP addresses (toggleable, on by default), phone-number shapes, and card numbers — but only when they pass the Luhn checksum, so order numbers and other long digit strings are left alone.
Why the checksum test for card numbers?
Because blindly masking every 13–19 digit run would eat order IDs, build numbers and timestamps that a reader of the ticket legitimately needs. A real card number passes the Luhn checksum by design; a random long number almost never does. It is a deliberate false-positive guard, and the trade-off is stated here rather than hidden.
Is redaction a guarantee the excerpt is safe to post publicly?
No, and any tool that promises that is overselling. Redaction catches known secret shapes. A secret in an unusual shape — a key split across lines, a password inside a sentence — can survive. The counts table shows what was caught; read the output once yourself before sharing. Never post production logs with real customer data to a public forum, redacted or not.
Does redaction also apply inside the other tools?
Yes — the same redaction runs everywhere on this site. Board samples are redacted on screen by default, saved board data is redacted before it is stored, and every export (incident report, redacted log download, copied summary) is redacted unconditionally, even if you switched the on-screen raw view on.