Log Masker

How to use it

1. Paste logs into the left panel - application logs, stack traces, request dumps, anything textual.
2. Click Mask sensitive data, or just keep typing: the output refreshes as you edit.
3. The right panel shows the masked text; the line under it counts replacements per rule.
4. Click Copy to take the sanitized version into your issue tracker or chat.

Common use cases

• Filing bugs in public trackers - share a stack trace without leaking customer emails or IPs.
• Sharing logs with support - keep the debug value, drop the personal data.
• Screenshots of terminals - produce a clean text version to paste into docs instead of blurring images.
• Teaching data hygiene - show a team which patterns leak most often in raw logs.

Why it stays private

Matching and replacing happen with in-page regular expressions only. The text is never uploaded, and the counts you see are computed from the same local run.

FAQ

Q: A card number was not masked - why? A: Candidate 13-19 digit runs must pass the Luhn checksum before they are treated as card numbers, which avoids mangling order IDs or timestamps that happen to be long. A mistyped or fake number can legitimately fail.

Q: Which phone numbers does it catch? A: The built-in rule targets mainland Chinese mobile numbers (11 digits starting with 1, optionally with a +86 prefix). Other formats are left untouched - review the output before sharing.

Q: Can it mask IPv6, JWTs or session cookies? A: Not in this version. The rule set is deliberately small and verifiable; extend carefully if you need more, because over-eager masking destroys the log's usefulness.