What this tool checks
It runs the 22 leaked-key tests from our free scan:
- #1 Stripe live secret key exposed Free
- #2 OpenAI API key exposed Free
- #3 Anthropic API key exposed Free
- #4 AWS access key exposed Free
- #5 Supabase service key exposed Free
- #6 GitHub token exposed Free
- #7 Google/Firebase API key without restrictions Free
- #8 Private key exposed Free
- #9 Slack token or webhook exposed Free
- #10 Secret values in public env variables Free
- #104 Clerk secret key exposed Free
- #105 Shopify admin token exposed Free
- #106 GitLab token exposed Free
- #107 npm access token exposed Free
- #108 Telegram bot token exposed Free
- #109 Mapbox secret token exposed Free
- #110 Brevo (Sendinblue) key exposed Free
- #111 Supabase personal access token exposed Free
- #112 Database connection string with password exposed Free
- #113 Stripe webhook signing secret exposed Free
- #114 Payment webhook secret exposed Free
- #115 Stripe test secret key exposed Free
Any key we find is masked before it's shown (only the first and last few characters), exactly as in our reports. We don't store the result.
How keys end up in a website
Anything your front end needs in the browser is downloaded by every visitor. That includes keys written into components, and environment variables with a "public" prefix: frameworks such as Next.js (NEXT_PUBLIC_) and Vite (VITE_) write those values straight into the JavaScript at build time. Renaming a secret to fix an "undefined" error is one of the most common ways keys leak.
Not every key in your code is a problem. Some are designed to be public: the Supabase publishable (anon) key, a Firebase web API key, a Stripe publishable key (pk_). We don't flag those. We flag keys that give access on their own: Stripe secret keys (sk_live_), AI provider keys, cloud credentials, database connection strings and service keys.
Found one? Do this first
- Revoke or rotate the key at the provider. Deleting it from your code isn't enough: it's already in old builds, caches and other people's copies.
- Check for misuse in the provider's logs or usage page.
- Move the call to a server (an API route, an Edge Function or a serverless function) that reads the key from secrets.
For Stripe there's a step-by-step guide to a leaked Stripe key. Each run uses one of your 2 free scans for the day. The full free scan also checks for exposed .env and .git files.
Questions
Do you keep the keys you find?
No. Keys are masked in the result, and tool results aren't stored. Our scan reports also store only masked values.
My Supabase anon key showed up in my code. Is that a leak?
No. The anon or publishable key is meant to be public, so we don't report it. We report the service_role or secret key, which must never be in a browser.
Does it read code that's only on my server?
No. It reads what your site sends to visitors: the HTML and the JavaScript files it loads. That's exactly the code an attacker can see.