Check your app's public page for free.
Paste your app's URL. In about ten seconds you see its security headers, response time, which flows it exposes and how testable the UI is.
Results appear here.
Try your staging URL, a competitor, or this site.
What the scan can see, and what it can't.
The free scan reads one public page from the outside. In a Launch Check our team signs in and uses your app the way your customers will, and the way someone trying to abuse it would.
| What gets checked | Free scan | Launch Check |
|---|---|---|
| HTTPS and security headers | ||
| Response time of your first page | ||
| Tech stack, forms, login and checkout detected | ||
| How testable your UI markup is | ||
| Can one user read or change another user's data? | ||
| Are admin actions protected at the API, not just hidden? | ||
| Do payments and webhooks survive retries and failures? | ||
| Signup, login and password reset on real phones and browsers | ||
| Secret keys exposed in your JavaScript bundles | ||
| Empty, huge and hostile input on every form | ||
| A fix prompt for every bug, ready for your AI tool |
About the scan.
Is the scan safe to run on my live app?
Yes. It makes one ordinary request for one public page, the same as a single visitor opening it in a browser. It never logs in, submits forms or follows links.
Why did my scan fail?
Usually bot protection, such as Cloudflare or Vercel, blocking automated requests. That is a sign your protection works, not a problem. A Launch Check tests your app as real users do, so it is not affected.
Do you keep my URL or results?
No. Nothing is stored. Your IP address is held in memory only to enforce the limit of three scans per hour.
What do I get from a Launch Check that the scan can't give me?
Our team logs in, uses your app like a real customer and like an attacker, and checks the flows that matter: signup, payments, permissions and data. You get every bug ranked by risk, with steps to reproduce and a fix prompt.
Want the full picture first? See how QABasic works.
