All Tools View Categories About Contact Privacy

.env Secret Scanner

Find API keys, tokens, passwords and embedded credentials by key name and value pattern — masked output.

Runs entirely in your browser — nothing is uploaded.

About .env Secret Scanner

Secrets do not announce themselves. STRIPE_KEY=sk_live_9f2a... is obvious; SETTING_12=u7g3Kp9Q...QnZ is not. The .env Secret Scanner looks for both signals at once — telling key names and credential-shaped values — and flags them by line with a masked value and a risk level.

It is a triage tool for the moment before you paste a .env into a ticket, a screenshot, or a commit: run the scan, see what it would expose, and rotate anything that looks live. It detects Stripe-style sk_live_ keys, AWS access keys, OAuth-style tokens, generic high-entropy strings, and credentials embedded in URLs.

The scan never uploads anything, and it shows only masked values so the result itself is safe to share.

Features

  • Key-name rules: KEY, SECRET, TOKEN, PASSWORD, PASSWD.
  • Value patterns: sk_live_, AKIA, Bearer, base64-like.
  • URL credentials: scheme://user:pass@host caught.
  • Risk levels: high / medium / low per item.
  • Masked values: output never leaks full secrets.
  • Line numbers: exact locations in the file.
  • Summary: counts by risk tier.
  • Private & free: all in-browser.

How to Use

  1. Paste your .env into the input, or load the sample with realistic-looking secrets.
  2. Click Scan. Every suspected secret is listed with a risk level.
  3. Review masked values and rotate anything that looks live.
  4. Export the report or clear it when done.

Examples

Example 1 — Live key leak. A developer pastes a .env into a GitHub issue to ask for help. The scan surfaces sk_live_... with high risk, and the key gets rotated that day.

Example 2 — Anonymized screenshot. A config panel screenshot is going into docs; the scanner shows the screenshot would reveal a bearer token.

Example 3 — Neutral name. OPTIONS_X=eJw...A3 holds a long token under an innocent name; the value pattern catches it.

Example 4 — Embedded URL credentials. DATABASE_URL=postgres://admin:hunter2@db/prod is flagged so the password stops living in plain text.

Example 5 — Pre-commit ritual. The scan becomes the 30-second habit before any commit that could touch .env.

Benefits

  • Two-way detection: name and value signals.
  • Risk triage: prioritize what to rotate.
  • Share-safe output: only masked values shown.
  • Fast: instant in-browser scan.
  • Private: nothing is uploaded.
  • Free: use whenever you need it.

Frequently Asked Questions

How does it find secrets?
It uses two signals: key names that imply secrets (KEY, SECRET, TOKEN, PASSWORD, PASSWD) and value patterns that reveal credentials regardless of the name (sk_live_, AKIA, long base64-looking strings, URL credentials).
What does risk mean?
High risk is a live-looking key pattern such as sk_live_ or AWS AKIA. Medium risk is a secret-named key holding a non-empty value. Low risk is an entry that merely looks sensitive. It is triage, not a guarantee.
Are values shown?
No. Only masked values like sk_live_**** appear, and the scanner also suggests that live keys be rotated immediately if they look real.
Is a long random string always a secret?
A value that looks like base64 or a high-entropy token and has a neutral key name is flagged as a possible secret, because that is exactly what leaked tokens look like.
Is anything uploaded?
No. Detection runs fully client-side; your .env never leaves the page.