ProductChecks
We ask your app the questions a stranger would.
Anyone can try to open someone else’s order, change a price or download a backup. We ask your app 129 questions like that, in plain words.
- Are backups, database exports or folder listings reachable?
- Can customers choose what they pay?
- Can someone send email that claims to come from you?
- Can anyone change or delete data without signing in?
- Can strangers use your AI features on your bill?
- Are secret keys written into your repository?
- Are search engines told what they may list?
- Can a visitor choose the commands your server runs?
- Can your database tables be read without signing in?
- Do customers who cancel keep paid access?
- Can passwords and codes be guessed without limit?
- Do secure pages load anything over an insecure connection?
- Are admin panels or status pages open to anyone?
- Can reset links or invite codes be guessed?
- Can paid features be switched on without paying?
- Can a visitor rewrite what your app asks the database?
- Are secret keys or passwords in what browsers download?
- Can signed-in users reach other customers’ records?Found
- Could someone fake a “payment received” message to your app?
- Is your domain registration close to expiring?
- Can a link on your domain send visitors elsewhere?
- Can users give themselves more rights?
- Is your app running in development mode?
- Can a visitor open files outside the folder they belong in?
- Do passwords, keys or sign‑in details end up in your logs?
- Does your file storage list its files to anyone?
- Do the libraries you install have known flaws?
- Are passwords stored so they can be read or cracked?
- Can files with passwords or keys be downloaded?
- Can text your AI reads make its tools do harm?
- Is the certificate valid, trusted and far from expiring?
- Can anyone start your scheduled jobs?
- Can people upload files without signing in?
- Are keys or database dumps in the folder your site publishes?
- Do your pages ask browsers to protect them?
Five ways an app gets hurt.
Told with Wool & Co, a shop we made up. Its customers and numbers are made up too.
Someone pays less than they should.
Strangers make your app work for them.
AI usage this month
Your site shows more than it should.
2,318 customers
Secrets sit in your code.
.env3 weeks ago
1DATABASE_URL=postgres://shop:••••@db
2STRIPE_SECRET_KEY=sk_live_51N8x••••••
3SHOP_NAME="Wool & Co"
4CURRENCY=EUR
Vallit found all five.
- HighOrder #1043Signed-in users can reach other customers’ recordsYour order page, line 14 of its code
- Critical€0.01Customers can choose how much they payYour checkout, line 22 of its code
- High$482Strangers can use your AI features on your billYour AI chat, line 9 of its code
- Criticalbackup.sqlA database export is downloadable by anyoneYour website, /backup.sql
- Criticalsk_live_51N8x…Secret keys are committed to your repositoryThe file .env, line 2
Watch a check run.
You decide how far we look.
Your address is enough to start. The more you let us see, the more of your report fills in.
Your website
- Is the certificate valid, trusted and far from expiring?Clear
- Are secret keys or passwords in what browsers download?Clear
- Do forms send passwords unencrypted or in the address?Clear
Left open on your website
- Can anyone download files like .env or .git?Waiting
- Are backups, database exports or folder listings reachable?Waiting
- Are admin panels or status pages open to anyone?Waiting
Waiting: these checks run once the domain is confirmed.
Who can reach which data
- Can anyone change or delete data without signing in?Not checked
- Can signed-in users reach other customers’ records?Not checked
- Can users give themselves more rights?Not checked
Not checked: these checks need access to your code, which comes with a plan.
Look up any question.
Every check is a question, and some answer more than one. Search all 129 of them, and open any to see what it means.
129 questions
What could happenCritical
A stranger or another customer reads, changes or deletes data that is not theirs.
How we check
The check follows every way into your app to each database call. Those are route handlers, API routes, Server Actions, Express and Hono routes, and Supabase Edge Functions.
Vera, our AI, reads every finding of this check again and leaves out the false alarms it can rule out.
Read the whole checkWhat could happenCritical
People get paid features for free or for less, or real payments fail to count.
How we check
The check follows every checkout, every payment webhook (the address your payment provider calls to report a payment) and every place that grants paid access. It knows the events Stripe, Lemon Squeezy, Paddle and Polar send.
Vera, our AI, reads every finding of this check again and leaves out the false alarms it can rule out.
Read the whole checkWhat could happenHigh
Anyone uses your app as a free AI service and runs up your provider bill.
How we check
The check follows every call to a paid AI model: the AI SDK, OpenAI, Anthropic, Google, Replicate, fal, or a direct request to a model API.
Vera, our AI, reads every finding of this check again and leaves out the false alarms it can rule out.
Read the whole checkWhat could happenCritical
Visitors meet an error page, or leave before the page appears.
How we check
The check loads your homepage. If it answers, the check asks twice more and uses the middle of the three response times.
Read the whole checkHow we check
The check reads the exact version of every library your app runs on from the lockfile (npm, pnpm, Yarn or Bun) and looks it up in the OSV vulnerability database.
Read the whole checkWhat could happenHigh
A stranger or another customer reads, changes or deletes data that is not theirs.
How we check
The check follows every way into your app to each database call. Those are route handlers, API routes, Server Actions, Express and Hono routes, and Supabase Edge Functions.
Vera, our AI, reads every finding of this check again and leaves out the false alarms it can rule out.
Read the whole checkWhat could happenCritical
People get paid features for free or for less, or real payments fail to count.
How we check
The check follows every checkout, every payment webhook (the address your payment provider calls to report a payment) and every place that grants paid access. It knows the events Stripe, Lemon Squeezy, Paddle and Polar send.
Vera, our AI, reads every finding of this check again and leaves out the false alarms it can rule out.
Read the whole checkWhat could happenMedium
Anyone uses your app as a free AI service and runs up your provider bill.
How we check
The check follows every call to a paid AI model: the AI SDK, OpenAI, Anthropic, Google, Replicate, fal, or a direct request to a model API.
Vera, our AI, reads every finding of this check again and leaves out the false alarms it can rule out.
Read the whole check
A check tells you what it saw that day. Finding nothing doesn’t prove a problem can’t exist.
See what your app shows to anyone.
Start with a free check. You don’t even need an account to see the result.
See plans