Skip to content
Secret Scan Lite

Secret scanner that never leaves your browser

Check a paste for leaked keys before anyone else reads it.

Paste logs, an env file or a git diff. Secret Scan Lite finds API keys, tokens, private keys and passwords, masks them, tells you how serious each one is and what to rotate, and gives you a clean copy that is safe to share.

See what it catches
Demo dossier. Every key on this page is generated and fake.

What it is

A free pattern scanner for pasted text. It knows the shapes of keys from AWS, GitHub, GitLab, OpenAI, Anthropic, Stripe, Slack, Google, SendGrid, npm, PyPI, Twilio, Discord and Telegram, plus private keys, database URLs, JWTs and password assignments.

Who it is for

Developers before a pull request, support teams who receive log dumps, founders about to paste an error into a group chat, and reviewers checking a diff.

What it solves

Secrets slip into logs, screenshots and commits all the time. Once shared, they are copied everywhere. A quick local check catches the obvious ones while you can still just delete the message.

Scan a paste

The scan runs in this tab. Nothing is uploaded, logged or stored.

Load a demo file
Logs, .env files, config, JSON or a git diff. Multiline private keys are fine.

No scan yet

Paste something, or load one of the demo files to see a full report.

Even a masked report reveals which services you use. Share it only with people who need it.

What it catches

Twenty four kinds of secrets, ranked by what an attacker could do with them.

Critical

Direct access to money, infrastructure or data.

  • Private key block
  • AWS access key ID
  • AWS secret access key
  • GitHub token
  • GitLab personal access token
  • Anthropic API key
  • OpenAI API key
  • Stripe secret key
  • Database URL with password
  • Wallet or signing private key
  • Seed phrase

High

Can post, send or read as you.

  • Slack token
  • Slack webhook URL
  • Google API key
  • SendGrid API key
  • npm access token
  • PyPI API token
  • Twilio API key
  • Discord webhook URL
  • Telegram bot token
  • URL with a password in it
  • Authorization header
  • JSON Web Token

Medium

Sensitive and often reusable.

  • Password or secret assignment

Low

Placeholders and examples. Worth a look, rarely a leak.

How to use it

  1. Paste before you share

    Logs, env files, stack traces or a diff. Use the demo files to see every kind of finding first.

  2. Read the verdict

    Critical and high findings mean do not share. Placeholders are listed separately so they do not drown out real problems.

  3. Rotate what leaked

    Each finding says where to revoke it. Removed lines in a diff still live in git history, so rotate those too.

  4. Share the masked copy

    Copy the masked text into the ticket or chat, and keep the report with fingerprints for the security thread.

Good to know

  • It matches known shapes. A custom token with no prefix and no label will not be found.
  • It cannot tell whether a key still works. Treat every real looking key as live until it is rotated.
  • Deleting a line in a new commit does not remove it from git history.
  • Values that point to a variable, like process.env or a dollar placeholder, are skipped on purpose.

Questions

Is my text sent anywhere?

No. The scan is plain code running in this page. You can load it, go offline and it still works.

Why is a test key not critical?

Stripe test keys cannot move money, so they are ranked lower. They still deserve a rotate if they were public.

What is the randomness number?

It estimates how random a value is. Real keys usually score above 4, words and placeholders score lower.

Can I scan a whole repository?

This tool is built for pastes. For full history scans use a dedicated scanner in your CI pipeline.

Talk to the builder

Questions, ideas or a job offer? Send a message on X or Telegram.

Support the builder

If this tool saved you time, you can send a tip to this EVM address from your own wallet.

0xd28Fd90eD69092bd01598f237aad33a0cc9c3EeA