Quick check
$0
Everything on this page's free check: public keys, exposed files, source maps, headers.
Check my appPaste your app's address. In about 20 seconds you'll see every secret key, open config file and missing protection that any visitor to your site can already see.
Made for apps built with Lovable, Bolt, v0, Replit, Cursor, Windsurf and Claude Code.
They need a deeper look at your database rules or code. The paid reports cover them.
AI coding tools optimize for "it works." These are the mistakes we see them ship most.
People are getting wary of apps built in a weekend. A live badge tells them someone is watching the doors.
Run a report on your live app or your code.
Every finding comes with the exact steps, or a prompt to paste into your AI tool.
We re-check every day. Your badge links to a public page with the latest result, and it turns grey if something new breaks.
Start free. Pay only when you want the deep check or the badge.
$0
Everything on this page's free check: public keys, exposed files, source maps, headers.
Check my app$19 one time
Tests your Supabase Row Level Security and Firebase rules from the outside, plus fix steps for every finding. Requires proof you own the app.
$49 one time
Read-only GitHub access. Finds secrets in your code and history, API routes without login checks, and unsafe database policies.
$9 per month
Daily re-checks, an alert when something breaks, and the live badge with its public status page.
Yes. It loads your page and its JavaScript the way a browser does, and requests two well-known paths (/.env and /.git/HEAD) to see if they're exposed. It never logs in, never writes data and never uses any key it finds.
No. The free check runs, shows you the result and forgets it. We keep only a daily count of how many checks ran. Found keys are always shown cut short, never in full.
The free check only reads public information, the same as visiting the site. The paid reports go further, so they require proof that you own the app before they run.
No. It means none of the problems we check for were visible from the outside. The free check can't see your database rules or server code, so a clean result is a good start, not a guarantee.
Rotate it first: create a new key in that provider's dashboard and delete the old one. Removing it from your code isn't enough, because copies of the old version may still be out there. Then move the call that needs it to your server.
Yes. Agents can call GET /api/v1/check?url=<address> and get JSON back. Instructions for agents are in llms.txt.