Cloud and provider keys
AWS access keys, Google API keys, and OAuth tokens. These unlock real infrastructure and real bills, and they get scraped from public repos within minutes of being pushed.
Free tool
Paste code, a config file, or a .env and find leaked keys, tokens, and passwords before they ship. It runs in your browser, so nothing you paste is ever uploaded.
Built on the same leak patterns our own pre-push checks use. Nothing is stored.
What we look for
These are the credential types that get scraped, abused, and turned into a bad day. We flag them, mask them, and tell you what to do next.
AWS access keys, Google API keys, and OAuth tokens. These unlock real infrastructure and real bills, and they get scraped from public repos within minutes of being pushed.
Stripe secret and webhook keys, GitHub and GitLab access tokens, and Slack tokens. One of these in the wrong place can drain an account or expose your whole codebase.
SSH and TLS private key blocks, and database connection strings with the password baked right into the URL. Both are full-access credentials hiding in plain sight.
Assignments like password = "..." and long random-looking hex or base64 values that look like keys. We flag them so you can decide, and we never echo the value back.
Questions
Finding a leaked key once is good. Never shipping one again is better. UpperLevel sets up secret handling properly, and a real person answers in under five minutes when something needs eyes.