Website leak check

Paste the address of your own website or app. In about a minute we look at what any visitor’s browser receives: secret keys in the page code, exposed source code and security headers. We don’t try to break in, we don’t touch your database, and we don’t store the keys we find.

Works for apps built with Lovable, Bolt, Replit, Cursor and v0, and for any other site. No sign-up. Up to 3 checks per hour.

What we check

  • The home page and the scripts it loads, exactly as a browser does
  • Keys: OpenAI, Anthropic, Supabase (we tell the public key from the service key), Firebase, Stripe, AWS, GitHub, Slack, SendGrid, Telegram bots, private keys, database passwords in URLs
  • Exposed source maps
  • HTTPS and security headers
  • In the detailed check: up to 10 pages, the certificate, cookies, SPF and DMARC

What we don’t do

  • We don’t guess hidden paths or files
  • We don’t log in to your database or try the keys we find
  • We don’t store keys: the report shows only the last 4 characters
  • We don’t publish results: only you see the report; after a detailed check our team receives only the types of issues

Questions

Is this safe for my site?

Yes. The check makes the same requests a visitor’s browser makes when it opens the page: it downloads the HTML and scripts. The detailed check also reads robots.txt and the sitemap, as a search engine does. We don’t submit forms, guess paths or contact your database.

Why is a public Supabase key a warning, not an error?

The public key (anon or publishable) is meant to be in the browser. The danger is tables without Row Level Security (RLS): anyone with that key can read and change them. The database itself can’t be checked from outside; the owner does that in the Supabase dashboard, or we do it during a diagnosis.

If nothing was found, is my site secure?

Not necessarily. It only means the public part of the site has no common leaks. Data access rules, payment checks and backups are visible only from inside the project, and they are checked during a diagnosis.

Can I check someone else’s site?

Only with the owner’s permission. The check looks only at public data, but deciding what gets checked is the site owner’s call.

What should I do if a secret key was found?

First revoke the key in the service’s dashboard and issue a new one, then review usage and logs there, remove the key from the page code and move the requests to a server. Deleting the key from the code is not enough: it may already have been copied.