What Redaxa detects

How to read these pages

• Severity is set by the engine for the kind of data. Critical: direct account or system compromise, as with keys, passwords and tokens. High: direct financial exposure or a strong identifier, such as a card or national number. Medium: a personal identifier with real but indirect harm, such as an email, phone number or address. Low: a weak identifier that depends on context, such as a name or an IP address.
• One engine everywhere. The Chrome extension's free checks run it in your browser; the web check and the Windows app run it on Redaxa's server without storing the text; repository checks run it on the files of a public repository.
• No check proves a text is safe. Detection can miss sensitive information or flag harmless text; each page lists the misses and false positives we know about.
• Nothing is verified with a provider. Redaxa never tests whether a key works.

Credentials and secrets

Keys, tokens, passwords and private keys: leaking one can hand over an account or a system.

Personal data

Identifiers of people: contact details, national numbers, names and addresses.

Financial data

Payment cards, bank accounts and wallet addresses.

Your own terms

Client and project names that only you know are confidential.

Try it

Pro and Business start with a 3-day free trial: a card or another payment method is needed, nothing is charged for 3 days, and you can cancel before it ends from Manage subscription.