pwnmyvibecode_

full check

Scan your website for vulnerabilities

Everything in the quick check, plus leaked keys in your code, files that shouldn't be public and your database settings. Enter your site, add the tag the page gives you to your home page (your AI can do it for you), then run it.

what it adds

  • Keys and passwords in your site's code
  • Files like .env and .git that shouldn't be public
  • Your Supabase or Firebase setup
  • Whether other sites can read your pages as your logged in users
  • Server version info your site gives out

Plus everything in the quick check: https, headers and cookies.

What the full check looks for

Secret keys in your code

Your HTML and up to 12 of your own scripts are searched for secret keys: Stripe, OpenAI, Anthropic, AWS, GitHub, Slack, Supabase secret keys, private keys and more. Anyone can read what ships to the browser.

Leaked secret fixGemini key fixGoogle key fix

Files that shouldn't be public

It asks for /.env, /.env.local, /.env.production, /.git/config, /.git/HEAD and /config.json and checks whether a real file comes back.

.env file fix.git folder fixconfig.json fix

CORS that lets other sites read your data

It sends a test Origin header and flags a site that echoes it back while allowing credentials. It also notes a wildcard origin paired with credentials.

Reflected origin fixWildcard origin fix

Supabase and Firebase config

If your code carries a Supabase or Firebase config, you get a note to check your database rules. It never queries your database.

Check your rules fix

Version banners

Server, X-Powered-By and X-AspNet-Version headers that name your exact software version.

Version disclosure fix

Everything in the quick check

The HTTPS redirect, HSTS, Content Security Policy, frame protection, nosniff, Referrer Policy, Secure on your cookies and HttpOnly on login cookies, with an A to F grade.

HSTS fixCSP fixCookies fix

How to run it

  1. Enter your site's address above.
  2. Copy the tag you're given into the head of your home page, or add the DNS TXT record instead. Your AI agent can add the tag for you.
  3. Deploy, then start the check. It finds the tag and runs.
  4. Each finding links to a fix page with the change to make and a prompt for your AI agent.

Good to know

  • Your tag is made from a random key saved in this browser, so run full checks from the same one. Leave the tag in and every full check after that is one click.
  • It reads pages like a browser does: GET and HEAD requests only, no forms, no logins and 30 requests at most.
  • Checking a client's site? Add the tag with their go ahead, or send them the line to add.

What an outside scan can't see

The full check sees what anyone can see from outside your app. It won't catch:

  • Bugs in your own logic, like a page that shows one user another user's data.
  • Whether your Supabase RLS or Firebase rules actually block the wrong reads and writes.
  • Injection bugs such as SQL injection or XSS, since it sends no attack payloads.
  • Vulnerable packages in your lockfile. Stack alerts cover those.

For those, read the web security basics and the vibe coding security checklist, sign up for stack alerts and set up your own checks in CI.

Questions

How can I check my website for vulnerabilities?

Run the quick check from the home page for a grade on HTTPS, security headers and cookies. For leaked keys, public .env or .git files, CORS and your Supabase or Firebase config, run the full check on this page: enter your site, add the tag to your home page or a DNS TXT record, then start it.

Is this a free online website vulnerability scanner?

Yes. The quick check and the full check are both free and need no signup or account.

Is it safe to run on a live site?

Yes. It reads your site the way a browser does, with GET and HEAD requests only, two at a time and 30 at most. It sends no forms, logins or attack payloads and changes nothing on your site.

Does the tag expose anything about my site?

No. The tag holds a code made from your site's address and a random key saved in your browser. It holds no secret and gives no access to anything, so it's fine to leave in your page.

Can I remove the tag afterwards?

Yes, whenever you like. If you leave it in, every later full check from the same browser is one click. If you take it out, add it back before the next one.

What if I can't edit my home page?

Add a DNS TXT record instead. The check gives you the exact name and value to add at your DNS provider.

Can I run it on a client's site?

Yes, with their go ahead. Add the tag yourself if you manage the site, or send them the one line to add.

Does it find SQL injection or XSS?

No. It sends no attack payloads, so it can't test for injection bugs. It finds what's visible from outside: leaked keys, public files, loose CORS, missing headers and weak cookies. For injection testing, use a scanner built for it on a site you own.

Does it check my Supabase or Firebase security rules?

It spots your Supabase or Firebase config in your site's code and reminds you to check your rules, but it never queries your database. The Supabase RLS and Firebase rules explainers show how to test them yourself.

Just want a grade? Run the quick check. No tag needed. Comparing tools? See how free scanners compare.