Log Scrubber & Anonymizer
Redact IP addresses, emails, and hostnames from pasted log text before sharing it.
Full redaction replaces every match with a fixed token — e.g. [REDACTED_IP] or [REDACTED_EMAIL] — leaving no trace of the original value.
How the log scrubber works
Server logs are one of the easiest ways to accidentally leak personal data — customer IP addresses, staff email addresses, and internal hostnames end up in support tickets, bug reports, and screenshots shared with third parties. This tool runs entirely in your browser: it scans the pasted text with regular expressions for IPv4 addresses (including CIDR-safe octet ranges), IPv6 addresses, email addresses, and fully-qualified hostnames, then replaces each match either with a fixed placeholder token ([REDACTED_IP], [REDACTED_EMAIL], [REDACTED_HOST]) or a partially masked version that keeps enough of the original shape to stay useful for debugging (e.g. 203.xxx.xxx.xxx or ja***@***.com). Toggle each category independently, switch between full redaction and partial masking, and copy or download the cleaned result. Since everything runs client-side, your raw logs are never uploaded anywhere.
Built and maintained by Meet Shah · Last updated
What this tool is used for
- Redacting addresses and hostnames from a log before attaching it to a ticket.
- Masking part of an identifier so records can still be correlated.
- Preparing a log sample for a vendor without the personal data.
- Checking which categories of data a log actually contains.
- Producing a sanitised excerpt for documentation.
Frequently Asked Questions
- What does it detect?
- IPv4 and IPv6 addresses, email addresses, and bare hostnames or FQDNs. Each category can be switched off independently, so you can strip addresses from a log while leaving the service names that make it readable.
- Why does the order of the patterns matter?
- Because they overlap. IPs are consumed first so a dotted quad is never read as a hostname, and emails before hostnames so an address's own domain is not redacted twice. Running hostnames first would eat the tail of every email in the file.
- What is the difference between full and partial masking?
- Full replaces the match with a token such as `[REDACTED_IP]`. Partial keeps a fragment — `203.xxx.xxx.xxx`, `ja***@***.com`, `***.example.com` — which preserves enough shape to correlate events without disclosing the value.
- Is partial masking safe to publish?
- Treat it as obfuscation, not anonymisation. A retained first octet plus a timestamp can still identify a host within a small network, and a two-character local part narrows an email considerably. Use full redaction for anything leaving your organisation.
- Does the log leave my browser?
- No. Scrubbing runs locally and the log text is deliberately kept out of the URL — only the toggle settings are shareable, because putting raw log content in a link would leak it into history, bookmarks and any referrer header.
- What will it miss?
- Anything not in those three shapes: usernames, session tokens, bearer credentials, phone numbers, account ids, and internal single-label hostnames with no dot. Read the output before sharing it — this reduces the manual work, it does not remove the need to check.
Common errors and gotchas
- Assuming pattern matching finds everything, when free-text fields and unusual formats defeat it.
- Using a consistent full-token replacement, which preserves the ability to link records back.
- Masking the obvious fields and leaving a user agent or a referrer that identifies the same person.
- Treating redaction as anonymisation, since surrounding context often re-identifies.
- Sharing the original by mistake because the scrubbed copy was saved separately.