Free Secret Scanner · Find API Keys in Code
Paste any code, config, or bundle excerpt and get flagged secrets · AWS keys, Stripe live keys, OpenAI keys, GitHub tokens, JWTs, private key blocks and more.
Pasted and uploaded code stays in your browser. URL and repository scans fetch source on SimplyScan servers; private connections use your temporary GitHub token.
Preview · sign in with a free account to run it
Scan a live URL or repository
The SimplyScan Security Engine fetches public source on the server. Only masked findings are returned. Paste mode below stays in your browser.
Scan a current build file or an exported git-history patch locally. Export history with git log --all -p --format=fuller > history.patch, then choose the patch below. Split large exports into chunks: the input limit is 200,000 characters.
Pasted and uploaded text stays in this browser. The URL and repository modes above fetch public source on the server.
How to use it
- Paste code, config or a bundle excerpt, or upload a file or an exported git-history patch. These stay in your browser.
- Or enter a live URL, or connect a GitHub repository, to have SimplyScan fetch the source and scan it on the server.
- Read each finding: which key type matched, and where.
- Rotate every real key you find before you remove it from the code.
Example
Input
const stripe = new Stripe("sk_live_51H…");
const openai = new OpenAI({ apiKey: "sk-proj-…" });Result
2 findings CRITICAL line 1 Live Stripe secret key sk_liv…abcd Revoke this key in the Stripe dashboard immediately, move it to a server-side secret store. CRITICAL line 2 OpenAI API key sk-pro…GhIj
What it detects
- Provider key formats
- AWS (AKIA…), Stripe (sk_live_, rk_live_), OpenAI (sk-, sk-proj-), GitHub (ghp_, gho_), Google (AIza…), Slack (xox…) and others with a recognisable prefix.
- JWTs
- Including Supabase service_role tokens, which bypass row level security entirely.
- Private keys
- PEM blocks that begin -----BEGIN … PRIVATE KEY-----.
- High-entropy assignments
- Long random strings assigned to names like secret, token or password.
- Git history
- A key deleted from the latest code is still in every earlier commit. Export your history and scan the patch to find it.
Go deeper
Page updated
Frequently asked questions
Which secret formats are detected?
High-signal prefixes and structures: AKIA (AWS), sk_live_/rk_live_ (Stripe), sk- and sk-proj- (OpenAI), ghp_/gho_ (GitHub), AIza (Google), xox (Slack), eyJ JWTs including Supabase service-role tokens, PEM private key blocks, and generic high-entropy assignments.
I found a real key in my code · what now?
Rotate it immediately (the finding means it's compromised, not just risky), move the new key server-side, and scrub git history if it was committed. Then scan your deployed app · the same key may be live in your bundle right now.
I found a key. Is deleting it enough?
No. Treat it as compromised: create a new key, deploy it, then revoke the old one. Deleting the code doesn't remove it from Git history or from anyone who already copied it.
What's the input limit for pasted text?
200,000 characters. Split larger history exports into chunks.
Want the full picture?
This tool covers one narrow check. A full SimplyScan runs 60 checks across 14 categories · exposed keys, RLS, XSS, auth, and speed · in 30 seconds.
Run a full security scanRelated tools
.env File Linter
Paste your .env and get instant findings · secrets that will ship to the browser, duplicate keys, quoting problems · plus a generated .env.example.
JWT Debugger
Paste a JSON Web Token to decode its header and payload · and get flagged for alg:none, weak algorithms, missing expiry, and sensitive claims.
CSP Evaluator
Paste a Content-Security-Policy and get an A-F grade · with specific fixes for unsafe-inline, unsafe-eval, wildcards, and missing directives.