PII 마스킹 도구

(문서는 영어)

What it does

The PII Redactor scans pasted text for seven kinds of personal data — email addresses, phone numbers (international formats), IPv4 and IPv6 addresses, US Social Security numbers, credit card numbers, and ISO dates (YYYY-MM-DD) — and masks each one with a token of your choice. Every candidate passes a structural check before it counts: IPv4 octets must be 0-255, card numbers must pass the Luhn

checksumchecksumA short digest computed from a block of data, compared after transfer or storage to detect corruption. Changing one bit changes the checksum.

, dates must be calendar-plausible, and phone numbers must fit the E.164 digit budget (7-15 digits). That keeps false positives low — 999.999.999.999, version strings like v1.2.3.4, clock times, and Luhn-invalid digit runs are all left alone. Everything runs 100% client-side — the text never leaves your browser.

How to use it

1. Paste or type text into Input (or hit Sample to load an example with every PII type).
2. Watch the Detected panel: each item is highlighted inline with a colored badge — blue for Email, purple for Phone, orange for IP, red for SSN and Card, gray for Date.
3. Toggle any PII type off (or on) with the chips to scan for exactly what you care about — counts update live.
4. Pick a mask — [REDACTED], ███, ***, or your own Custom string.
5. Copy the redacted output, or click the eye to peek back at the original.

Examples

Support ticket

Input: Reach me at jane.doe@example.com or +1 (555) 123-4567. Server 192.168.1.100 was slow on 2026-08-16. → 4 items found, output: Reach me at [REDACTED] or [REDACTED]. Server [REDACTED] was slow on [REDACTED].

Only mask emails

Same text with every toggle off except Email → only jane.doe@example.com is masked; phone, IP, and date pass through untouched.

Card numbers must be Luhn-valid

4111 1111 1111 1111 (a valid Visa test number) is detected and masked; 1234567890123456 is left alone.

Good to know

• Private: all detection is local regex +

  checksumchecksumA short digest computed from a block of data, compared after transfer or storage to detect corruption. Changing one bit changes the checksum.

  work — nothing is transmitted or stored.
• Heuristic, not legal: the detector finds data-shaped patterns; it cannot judge context or guarantee compliance with GDPR/CCPA on its own. Always review the output before sharing.
• Overlaps resolve sensibly: when one span could be two types (a date also looks like a phone number), the more specific type wins.
• Related tools: Credit Card Validator (the same Luhn check, in depth), Defang/Refang.