Cron Calendar
Explain cron expressions and preview the next run times in any timezone.
OpenStrip the obvious credentials and email addresses out of a log or .env paste before it goes into a ticket.
Logs, .env files, HTTP dumps or stack traces.
Bearer tokens, labelled secrets, AKIA, ghp_ and sk- keys, and emails.
Look for unlabelled tokens and keys the rules do not cover.
Share the redacted copy and keep the original private.
A vendor's support engineer wants the failing request log, and it includes an Authorization header, a database password and the customer's email address. Editing those out by hand is error-prone across fifty lines. Paste the log here, check the masked version, and send that instead.
Redaction runs as you type. The rules cover Authorization: Bearer headers, any key=value or key: value pair whose name ends in api_key, apikey, api-key, token, password or secret, AWS access key IDs starting with AKIA, GitHub personal tokens starting with ghp_, and sk- keys followed by 20 or more letters and digits, the classic OpenAI format. Matched values become ***REDACTED*** while the label or prefix stays, so the log still shows which credential was involved. Email addresses become ***@***.
It is a fixed list of patterns, so read the output before sharing. A JWT on a line of its own, a PEM private key block, a Slack token or an AWS secret access key without a recognised label will not be masked, and a value is masked only up to the first space. For a second opinion, the secrets scanner also flags private key blocks, and the PII detector looks for phone numbers, card numbers and other personal data.
Everything is replaced with regular expressions inside this tab, which is the point: the unredacted text never has to reach another service.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
A token is only masked when it follows a Bearer header or a label such as token= or secret:. A bare eyJ string on its own line is not recognised, so delete it by hand or put it after a label first.
Yes. Only the matched values change, so line order, timestamps and key names stay where they were and the log remains readable for whoever debugs it.
No. Values are replaced, not encoded, and nothing is stored. Keep your unredacted copy where it was if you will need it again.