Every check / secrets-in-frontend
Is a secret key published in the code your website sends to every visitor?
We read the code your homepage runs and look for keys and tokens from services such as Stripe, Google, GitHub, Slack, OpenAI and Anthropic.
How it decides
That means the scripts in the page and the script files it loads from your own site. The check speaks up for each kind of key it finds, names the file and shows only a masked start of the key. On a domain you have proved is yours, we also ask the provider whether the key still works, and one it has already cancelled becomes a minor note.
Run this check on any website
Free, with no account. It sends the site nothing an ordinary visitor would not.
Why it matters
Every visitor downloads that code by design, so a key in it is already public and nobody has to break in to use it.
In more detail
A live payment or AI key can run up charges or reach your customers' data in your name. It has to be cancelled and replaced, not only deleted.
Who fixes it, and where it runs
- Who usually fixes it
- Whoever built your site
- Which plan runs it
- The free scan, on any website
- Proof you own the site
- Not needed. It sends your site nothing an ordinary visitor would not.
More about this check
- Who it is about
- An intruder
- Listed under
- Things that should not be public
- Its name in a report
secrets-in-frontend