HomeSensitive Info Scanner

Sensitive Info Scanner

Scan code and configs for API keys, passwords, tokens and database URLs with risk grading and location hints

Input code or text

Supported detections

  • API keys for payment and third-party services
  • JWT tokens (JSON Web Token)
  • Password fields like password/secret
  • Database connection strings and credentials
  • AWS Access Key / Secret Key
  • Private keys in RSA/PEM formats

Common leak patterns

API_KEY = "sk_live_..."
password = "12345678"
const SECRET = "abc123..."
export default "eyJhbGciOi..."
mysql://user:pass@host

Security tips

  • Store secrets in environment variables instead of hardcoding
  • Use .env files and add them to .gitignore
  • Enable git-secrets or similar scanners before commit
  • Scan repositories regularly for exposed credentials
  • Rotate keys or tokens immediately if leaks are found


Documentation

About Sensitive Info Scanner

This tool detects potential secret leakage in text with multi-rule scanning, risk levels, and detailed findings.

Key Features

  • Multi-type Detection: API keys, JWTs, passwords, DB strings, private keys, etc.
  • Risk Summary: High/medium/low counts and total findings.
  • Detailed Findings: Match content, location, and explanation.
  • Selectable Rules: Enable only relevant detectors.
  • Quick Workflow: Sample load and clear actions.

Steps

  1. Paste text to scan.
  2. Select sensitive rule types.
  3. Run scan and review findings.
  4. Remediate by risk priority.

Use Cases

  • Pre-commit secret checks.
  • Log/ticket content review before sharing.
  • Security checks for scripts and config snippets.

FAQ

Are false positives possible?

Yes. Pattern-based detection favors safety, so manual context review is still needed.

Can this replace full security auditing?

No. Use it as fast screening alongside repository scanning and formal audit processes.