Plainmend

What the scan looks at.

A free scan reads what a visitor can already fetch. Database probes wait until the site is yours.

Secrets

  • Stripe, OpenAI, AWS, GitHub, Slack, and SendGrid keys in the page and its scripts.
  • A Supabase service_role or sb_secret_ key. The anon key is noted, not treated as a leak.

Files

  • A public /.env, /.env.local, or /.env.production.
  • /.git/config and /.git/HEAD.
  • JavaScript source maps that hand back the original files.

Transport

  • Whether the page actually loads over HTTPS.
  • Content-Security-Policy, HSTS, frame protection, nosniff, referrer policy, and permissions policy.

Database

  • After you verify ownership: whether the public anon key can read rows.
  • Whether an empty insert is blocked by Row Level Security.
  • We store a count, not the rows, and we never send a service_role key.

A prompt, not a lecture.

Copy it into the editor that built the app. Then rescan.

The browser bundle includes a Supabase service_role key.
Remove it from every file the visitor downloads, including
NEXT_PUBLIC_ and VITE_ variables. Rotate the key in the
Supabase dashboard. Keep the anon key in the browser, and
the service role on the server only. Turn on Row Level
Security for tables that hold a person's data.

We look. We do not break in.

  • No password guessing, exploit payloads, or port scans.
  • A service_role key is reported and never used.
  • If a table returns rows, we store the count, not the data.
  • Read the acceptable use rules.

Email the short checklist

Five things to look at before real users show up.