API Key Finder & Secret Scanner
Audit source code, environment variables, configuration files and project archives for leaked API keys, tokens, database URIs and private keys before committing or deploying.
Paste code or upload files and ZIP archives to scan for over 50 provider secret formats (AWS, OpenAI, Stripe, GitHub, Slack, Supabase, private keys, database URIs). All scanning runs 100% locally in your browser memory — nothing is ever uploaded or stored.
100% Client-Side Private · Zero Server Transmission
Files and pasted code are analyzed in your local browser memory. No secrets or tokens are ever sent to our servers.
Zero Server Uploads
Files process in local RAM
Instant WASM Speed
No waiting queues or lags
Unlimited Batching
Convert files without limits
What Does API Key Finder Do & How Does It Work?
Paste code or upload files and ZIP archives to scan for over 50 provider secret formats (AWS, OpenAI, Stripe, GitHub, Slack, Supabase, private keys, database URIs). All scanning runs 100% locally in your browser memory — nothing is ever uploaded or stored.
How to Use API Key Finder (Step-by-Step)
- 1Paste source code, upload files, or drop a project ZIP archive.
- 2Toggle placeholder filtering and generic secret scanning.
- 3Review detected credentials, severity levels, and code line context.
- 4Copy safe verification commands or export audit reports in JSON, CSV or Markdown.
Why Client-Side Secret Scanning Matters
Uploading unencrypted code or config files to third-party web scanners can accidentally leak the very credentials you are trying to protect. Our API Key Finder executes entirely within your browser using client-side pattern matching, Shannon entropy analysis and memory-only ZIP decompression. Your files and detected credentials never leave your machine.
We provide safe, masked previews by default (e.g. sk-proj-****...****3B12) so you can audit findings and share compliance reports without exposing raw secrets on screen.
Detection Rules & Entropy Analysis
The scanner combines 50+ high-precision provider regex patterns (AWS, OpenAI, Anthropic, Stripe, GitHub, Discord, Twilio, SendGrid, Supabase) with contextual assignment rules (api_key = '...') and Shannon entropy calculation. High entropy (>3.4 bits/char) isolates truly random credentials from normal English text and camelCase identifiers.
Built-in false-positive suppression automatically ignores UUIDs, Git commit hashes, SemVer strings, and common documentation placeholders such as YOUR_API_KEY, sample_token, and test_key.
Remediation Workflow for Leaked Secrets
If a real key is found in your code: 1) Immediately deactivate or revoke it in the provider's developer console; 2) Check provider audit logs (such as AWS CloudTrail or Stripe Logs) for unauthorized calls during the exposure window; 3) Inject replacement credentials via environment variables (.env) or a secret manager; 4) If committed to git, purge the repository history using git-filter-repo or BFG Repo-Cleaner before pushing.
Format Comparison Guide
Compare format differences, strengths, and optimal use cases.
Click to collapse
Format Comparison Guide
Compare format differences, strengths, and optimal use cases.
| Credential Category | Indicator / Prefix | Exposure Risk Level | Recommended Storage |
|---|---|---|---|
| AWS Access Key ID | AKIA / ASIA (20 chars) | Critical — IAM programmatic access | AWS Secrets Manager / IAM Roles |
| OpenAI API Key | sk-proj- / sk- (51+ chars) | Critical — Model inference & billing | Environment Variable (.env) |
| Stripe Secret Key | sk_live_ / rk_live_ | Critical — Financial charges & refunds | Server-side Secret Manager |
| GitHub Token | ghp_ / github_pat_ | Critical — Source code & repo push access | GitHub Actions Secrets |
| Database URI | postgres://, mongodb:// | Critical — Full direct database access | Private cloud VPC & dynamic secrets |
| Slack / Discord Token | xoxb-, xoxp-, Bot token | High — Message read/write, impersonation | Encrypted config / Vault |
Real credentials should never be committed into source code, repositories, or client-side web bundles.
Input & output compatibility
Accepts
- Pasted source code & configs
- .env / .json / .yaml / .toml / .ini
- JavaScript / TypeScript / Python / Go / PHP / Shell
- Project ZIP archives (up to 50MB)
Produces
- Interactive findings dashboard
- Surrounding code context snippets
- Masked credential exports (JSON / CSV)
- Markdown security audit summaries
100% client-side: all scanning and archive decompression runs strictly in your browser memory.
Common problems & solutions
A custom or internal API key was not detected
Enable the 'Scan generic secret assignments' option. Ensure your variable name matches standard patterns (api_key = '...', token = '...') and the key string has sufficient character randomness (Shannon entropy > 3.4).
A documentation placeholder was flagged
Ensure the 'Filter dummy placeholders' checkbox is active. The scanner automatically filters strings containing YOUR_API_KEY, example, dummy, xxxx, or repeated characters.
ZIP upload fails with an uncompressed size error
To protect your browser against Zip Bomb attacks and memory exhaustion, archives with more than 300 files or exceeding 50MB uncompressed are halted. We recommend scanning specific project subfolders or extracting locally first.
Is this private?
Local In-Memory Execution: Scanning runs entirely inside your browser's JavaScript and WebAssembly runtime. No code, filenames, or detected credentials are ever transmitted to our servers or stored in any database.
Masked Previews by Default: Discovered secrets are immediately masked (e.g. sk-proj-****...****A9f2) to prevent shoulder-surfing, accidental screenshot leaks, or screen-recording exposure during development.
Safe Offline Verification: Rather than making unauthorized network requests to third-party APIs from our domain, the tool generates copy-pasteable curl and CLI snippets so you can verify credential validity safely in your own isolated terminal.
Frequently Asked Questions
Is my source code or API key uploaded to any server?
No. The entire scan runs locally inside your browser's JavaScript and WebAssembly runtime. No code, filenames, or tokens are sent across the network.
Does this tool validate whether an API key is currently active?
For security and privacy reasons, we never make unauthorized network requests to third-party APIs on your behalf. Instead, we generate safe, ready-to-run curl and CLI verification snippets that you can execute in your own isolated terminal environment.
Which file types and project archives can I scan?
You can paste raw text or upload any text-based source file (.env, .json, .yaml, .js, .ts, .py, .go, .php, .rb, .sh, Dockerfile) or drop a project ZIP archive. Archives are uncompressed in browser memory with path traversal protection and zip bomb limits (up to 50MB uncompressed).
What should I do if an API key is detected?
Follow the remediation steps shown in the finding drawer: immediately revoke the credential in your provider's dashboard, issue a new key, and update your local .env file. Never commit keys to source control.
Is my data sent to your server?
No. This tool runs entirely in your browser using the Web Crypto API and JavaScript. Nothing you type or generate is uploaded, logged or stored.
Is it free? Do I need an account?
It's completely free with no sign-up and no daily credits.
Guides & Tutorials
Explore More Free Browser Tools
View All 290+ Tools Directory →All tools run client-side in your browser with zero data uploads, no sign-up, and zero tracking. Discover other popular converters and calculators:
Cryptographic Standards & Zero-Knowledge Privacy Architecture
API Key Finder is engineered to strict security and cryptographic specifications — guaranteeing zero data leakage, zero backend telemetry, and audited implementation:
- 1. 100% Zero-Knowledge Client Execution: Passwords, private keys, hashes, and API tokens are computed strictly in your browser's local memory via Web Crypto API (SubtleCrypto) and audited @noble/hashes. Nothing is ever sent to or stored on our servers.
- 2. Official RFC & NIST Compliance: Adheres to established security specifications including RFC 2104 (HMAC), RFC 6238 (TOTP), RFC 9106 (Argon2id), RFC 4122 (UUID v4), and FIPS 180-4 (SHA family).
- 3. Memory-Hard & Brute-Force Resilient: Incorporates robust hashing algorithms (Argon2id, bcrypt, PBKDF2) with configurable memory and iteration costs to defend against GPU-accelerated cracking.
- 4. Transparent & Inspectable: Every cryptographic calculation occurs visibly in client-side JavaScript. You can verify through your browser's Network tab that zero outbound requests are made with your sensitive inputs.
- 5. SSRF-Safe Diagnostic Probing: For internet-facing checks (SSL certificates, DNS records, HTTP security headers), handshakes run through isolated proxies that never log or store queried domains.
Suggest a Feature or Improvement for API Key Finder
Need custom options, higher limits, or extra format support? Let our engineering team know!