Keys in the browser bundle
Secrets embedded in the scripts your page loads.
Paste the URL of an app you own. One read-only pass checks for secrets in the bundle, open database tables, missing headers, and exposed paths, then ranks what it found by how much it can hurt you. Nothing is stored.
Waiting for a URL
Reads the page, its scripts, a few known paths, and public database tables, read-only. Looks for leaked keys, a service-role token, missing security headers, open CORS, exposed .env and .git, and Supabase tables readable with the public key.
Apps built fast, especially with AI app builders, tend to ship the same handful of problems. Owners rarely know until someone else finds them.
Secrets embedded in the scripts your page loads.
The one key that bypasses every rule in your database.
Supabase tables that answer to the public key.
The headers browsers use to block common attacks.
APIs that answer requests from any site.
Environment and git files left public.
An early version read a real row to show a table was open; the shipped version reads nothing and only checks whether the table answers. Acceptable-use terms went live before the route did.
You must own the site or app, or have written permission from whoever does. By running a scan you confirm that, and you are responsible for it.
It sends the ordinary requests a browser sends when it loads a page and its scripts. It writes nothing, changes nothing, and does not sign in as anyone.
It finds a specific list of common problems and misses everything else. A clean grade does not mean your app is secure.
We store nothing from a scan unless you ask us to email you the results.
Inherited or AI-built app that is not ready for real users? We review the code, rank what can hurt you, and fix it, keeping what works.