Payload Masker | Local Masking

FREE

More actions

Text-mode masking is best effort and does not guarantee that all sensitive data is removed. Review the output before sharing.

Input payload

Payload type

Sensitive keys to mask: password, passwd, pwd, secret, token, access_token, refresh_token, id_token, api_key, apikey, apiKey, authorization, proxy_authorization, auth, bearer, client_secret, private_key, credit_card, card_number, iban, cbu, cuit, dni, ssn, email

Advanced options

Sensitive keys to mask

Masked output

The masked payload will appear here.

Found something we could improve?

Practical usage guide

A practical workflow for Payload Masker

Mask selected sensitive values in JSON, XML or text before sharing; text-mode masking is best effort and does not guarantee sanitization.

1. Prepare

Select JSON, XML or text and configure keys or patterns to mask. Example JSON: {"email":"ana@example.invalid","order":"4500"}.

2. Review

Check that email becomes ***MASKED*** while order remains 4500. Inspect nested values and compare the remaining structure with the source.

3. Apply

Configured keys and patterns do not guarantee removal of every secret or personal detail. Inspect the entire output before sharing a diagnostic sample.

Verification before operational use

Use a representative case with the inputs needed to reproduce it.
Confirm the result in the authorized target environment when runtime versions, namespaces, extensions, permissions or system configuration can change the outcome.
Record the source, assumptions, tool settings and expected result so another reviewer can reproduce the check and distinguish verified facts from recommendations.