Tools › Entity types

Redact private keys from text, JSON, and CSV

A private key block is trivially detectable by its header, which makes it one of the few secrets you can catch with certainty. Redactly flags the BEGIN header, then extends the span to the matching END marker so the key material goes with it.

How Redactly detects private keys

• Matched by regex on the BEGIN header for RSA, EC, OpenSSH, and PGP private keys.
• The whole PEM block is replaced when the matching END marker is present, and the header alone is caught when a paste was truncated.
• Runs independently of the model, so no context is required.

Why redact private keys?

A private key compromises every signature and handshake it backs, retroactively and prospectively.

Example request

curl -X POST https://api.bitbanger.in/v1/redact \
  -H "X-API-Key: rdct_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"text": "Key loaded: -----BEGIN RSA PRIVATE KEY----- MIIEowIBAAKCAQEA...", "style": "replace"}'

Every hit in the response carries entity, text, start, and end. The offsets index into the text you sent, so you can apply the redactions to your own copy of the document. The full response schema is in the API reference.

Questions

Related entity types

• API keysRedact AWS, OpenAI, Anthropic, GitHub, Google, Slack, and Hugging Face API keys from logs and pasted text.
• PasswordsRedact plaintext passwords from configuration dumps, tickets, and transcripts before they are shared.
• Database connection stringsRedact connection strings containing embedded credentials for Postgres, MySQL, MongoDB, Redis, and AMQP.