Free · about a minute · nothing to install

Is your AI-built app safe to launch?

Paste your app's address. We check it the way an attacker would, show you proof of every problem, and give you a fix to paste into Lovable, Bolt or Cursor.

The free scan runs 46 security tests on public pages, two scans a day. Nothing is written to your site. No sign-up.

See how it works

02 / 07How it works

Three steps. No code, no setup.

  1. Paste your app's address

    Your published link from Lovable, Bolt, Cursor or anywhere else. No sign-up, no SDK.

  2. See what's wrong, in plain words

    A clear verdict first, then each problem with what it means and proof of what we saw.

  3. Paste the fix into your builder

    Every problem comes with a prompt for your AI builder. Scan again to confirm it's fixed.

Next: what we check

03 / 07What we check

147 tests, in three plans

Free runs 46. Pro adds 84 more from the same URL. Deep adds 17 on your database and signed-in users, for sites you verify.

Free

46 tests

Security problems anyone could find on your live site.

  • Leaked keysStripe, OpenAI, Anthropic, AWS, Supabase, GitHub, Slack and more in your public code
  • Exposed files.env, .git, backups, source maps, config files, debug pages
  • HTTPS and headersRedirects, certificate, HSTS, CSP, clickjacking, mixed content
  • Locked origin (CORS)Other sites reading your API, with or without login cookies
  • Safe errors and redirectsError pages that reveal your code, links that forward to scam sites
  • Malware and spamHidden spam links, injected scripts, miners, card skimmers, cloaking
See all 46 Free tests by name

Pro adds

84 more

Hardening, launch, legal and compliance, from the URL alone. Every finding comes with an AI fix prompt.

  • More keys and filesTwilio, SendGrid, Resend, Discord, AI providers; .npmrc, database dumps, logs, open admin panels
  • HTTPS hardeningCookie flags, old TLS, Permissions-Policy, COOP, CSP strength
  • Email and sign-up safetySPF, DMARC, DKIM, security.txt, bot protection, HTTPS forms
  • Outdated librariesjQuery, React, Next.js, Vue, Angular, Bootstrap, CMS versions
  • SubdomainsTakeover risk, public staging copies, wildcard DNS
  • Speed and launch readinessResponse time, caching, title, favicon, robots.txt, sitemap, 404 page
  • Legal and business rulesPrivacy, terms, cookie consent, GDPR details, refunds, contact
See all 84 Pro tests by name

Deep adds

17 more

Real (harmless) tests on your database and signed-in users, only on sites you verify. Part of Pro: each deep scan uses two Pro scans.

  • Database accessSupabase tables and storage, Firebase and Firestore open to strangers
  • User isolationCan one user see another's data or files?
  • Privilege escalationCan users make themselves admin or upgrade for free?
  • Password reset linksDo they work once and expire? (from a link you paste)
  • Rate limits and injectionCan bots hammer your login? XSS, SQL and template injection
  • Edge Functions and indexesFunctions anyone can call, unindexed row-security columns

Coming soon: Google blocklist status, subdomains from certificate logs, admin-only functions.

See all 17 Deep tests by name

04 / 07The report

Every problem comes with proof and a fix

An example with made-up data, not a real customer's scan.

Fix these first3 to fix
  • Your Stripe secret key is visible to anyone

    Found in your site's code

    Critical
  • Other websites can read your app's data

    Your server trusts any website that asks

    Medium
  • No protection against injected scripts

    A security setting your host can add is missing

    Medium
One problem, opened Critical

Your Stripe secret key is visible to anyone

Anyone who opens your site can copy this key and use your Stripe account: give refunds, create charges or download your customer list.

Proof: what we saw
1. We opened your site's code file, like any visitor's browser does:
GET your-app.lovable.app/assets/index-4f2a.js
2. Inside it, your live secret key (we hide most of it):
Stripe("sk_live_51N••••••••••Qx2")
How to fix it: copy this into your AI builder

Move the Stripe secret key out of the front end. Create a Supabase Edge Function that reads STRIPE_SECRET_KEY from environment secrets and creates the payment there. Call that function from the client instead of using the key. Then roll the exposed key in the Stripe dashboard, because it is already public.

View full sample report

05 / 07Pricing

Free to start. $10 when you want everything.

One payment, not a subscription.

Free

$0

  • 46 security tests on your public pages
  • Every finding with its severity and proof
  • 2 free scans a day, no sign-up
  • PDF report when you sign in (free)
Run free scan

Pro pass

30 days

$10 one time

  • All 130 tests from your URL: Free plus 84 Pro tests
  • A ready-to-paste AI fix prompt for every finding
  • 30 scans within 30 days, on up to 3 sites. Unused scans don't carry over; buying again adds 30 more.
  • Re-scan any time, a 30-day history and a PDF for every scan
  • Deep tests on sites you verify (17 more), two scans each
Get Pro

Chrome extension: scan the site you're on, right after you hit Publish. It only sends us the address you choose to scan; it never reads your pages or your history.

Coming soon

06 / 07FAQ

Before you paste your URL

Something else on your mind? Contact us.

Yes. It only reads what any visitor can load: your HTML, JavaScript bundles and source maps, plus your home page once more the way Google sees it. Nothing is written and nothing is brute-forced.

07 / 07Ready when you are

Launch day is a bad day to find out

Get your free result in about a minute. Scan right here.

Every test Securick runs

Free · 46 tests

Run on any public page, no sign-up. They only read what any visitor can load.

Leaked keys22 tests
  • #1Stripe live secret key exposed
  • #2OpenAI API key exposed
  • #3Anthropic API key exposed
  • #4AWS access key exposed
  • #5Supabase service key exposed
  • #6GitHub token exposed
  • #7Google/Firebase API key without restrictions
  • #8Private key exposed
  • #9Slack token or webhook exposed
  • #10Secret values in public env variables
  • #104Clerk secret key exposed
  • #105Shopify admin token exposed
  • #106GitLab token exposed
  • #107npm access token exposed
  • #108Telegram bot token exposed
  • #109Mapbox secret token exposed
  • #110Brevo (Sendinblue) key exposed
  • #111Supabase personal access token exposed
  • #112Database connection string with password exposed
  • #113Stripe webhook signing secret exposed
  • #114Payment webhook secret exposed
  • #115Stripe test secret key exposed
Exposed files9 tests
  • #11.env file public
  • #12.git folder public
  • #13JavaScript source maps public
  • #14Backup files public
  • #15.DS_Store public
  • #16Directory listing on
  • #17Debug or info pages public
  • #18Config files public
  • #116Development build in production
HTTPS and headers10 tests
  • #19HTTP redirects to HTTPS
  • #20SSL certificate valid
  • #21Certificate expires in more than 14 days
  • #22HSTS header
  • #23Content-Security-Policy present
  • #24Clickjacking protection
  • #25X-Content-Type-Options
  • #26Referrer-Policy
  • #27No mixed content
  • #28Server version hidden
CORS2 tests
  • #29Not open to every website
  • #30Not open to every website with login cookies
Safe errors1 test
  • #31Error pages hide code details
Open redirects1 test
  • #32Redirect links can't send users to outside sites
Malware and spam1 test
  • #33No hidden spam links or injected scripts

Pro adds 84 tests · 130 in all

From the same URL, with an AI fix prompt for every finding. Still read-only: nothing on your site is changed.

Leaked keys10 tests
  • #36Stripe restricted key exposed
  • #37Twilio credentials exposed
  • #38SendGrid key exposed
  • #39Mailgun key exposed
  • #40Resend key exposed
  • #41Google OAuth client secret exposed
  • #42Firebase service account exposed
  • #43Hugging Face token exposed
  • #44Other AI provider keys exposed
  • #45Discord bot token or webhook exposed
Exposed files5 tests
  • #46.npmrc with tokens public
  • #47Database dumps public
  • #48Log files public
  • #49Admin panel open without protection
  • #50API docs or GraphQL schema open to public
HTTPS and headers8 tests
  • #51Permissions-Policy
  • #52Cookies: Secure flag
  • #53Cookies: HttpOnly flag
  • #54Cookies: SameSite
  • #55Old TLS versions turned off
  • #56CSP not weakened
  • #57HSTS covers subdomains / preload
  • #58Cross-Origin-Opener-Policy
Email safety4 tests
  • #64SPF record
  • #65DMARC record
  • #66DKIM record
  • #67security.txt file
Sign-up safety7 tests
  • #68Bot protection on sign-up form
  • #69Sign-up and login forms use HTTPS
  • #117Sign-ups confirm the email address
  • #118Phone sign-ups confirm the number
  • #119Anonymous sign-ins are treated differently
  • #120Social login only returns to your own site
  • #121Auth Site URL isn't localhost
Outdated libraries7 tests
  • #70jQuery with known flaws
  • #71React / Next.js with known flaws
  • #72Vue / Angular with known flaws
  • #73Bootstrap with known flaws
  • #74Other common libraries with known flaws
  • #75CMS (WordPress etc.) out of date
  • #122CDN scripts have integrity checks
Subdomains3 tests
  • #77Subdomain takeover risk (dangling DNS)
  • #78Staging or dev subdomains public
  • #79Wildcard DNS
Speed and caching5 tests
  • #80Server response time
  • #81Compression on
  • #82Cache headers on static files
  • #83No oversized images or scripts
  • #123No render-blocking scripts
Launch readiness9 tests
  • #84Page title, description, favicon
  • #85robots.txt
  • #86sitemap.xml
  • #87Custom 404 page
  • #88Social share tags
  • #124Mobile viewport set
  • #125Error monitoring in place
  • #126Health check endpoint
  • #127Rollback plan for your host
Legal pages14 tests
  • #89Privacy policy page
  • #90Terms of service page
  • #91Cookie consent when trackers are used
  • #128Legal pages readable without JavaScript
  • #129Cancellation policy for subscriptions
  • #130Shipping and returns for physical products
  • #131Impressum where required
  • #132AI chat says it's AI
  • #133"Do Not Sell or Share" link (CCPA)
  • #134Accessibility information
  • #135Children's privacy (COPPA)
  • #136Copyright takedown contact
  • #137No template placeholders in legal pages
  • #138Legal links aren't broken
Privacy policy3 tests
  • #92Lists the data collected and third parties
  • #93Explains deletion and contact rights (GDPR/CCPA)
  • #139Google Fonts loaded from your own server
Business rules9 tests
  • #94Refund and pricing page for paid apps
  • #95Business contact details shown
  • #140Subscription renewal terms
  • #141EU withdrawal information
  • #142EU withdrawal function
  • #143Digital content consent
  • #144Delivery times shown
  • #145Affiliate links disclosed
  • #146Health data rules

Deep adds 17 tests · 147 in all

Real, harmless tests on your database and signed-in users, only on sites you verify and with your consent.

Blocklist0 tests + 1 coming soon
  • #34Not on the Google blocklist (Google Web Risk)coming soon
Database access6 tests
  • #59Supabase tables not readable with the public key
  • #60Supabase storage buckets not listable
  • #61Firebase Realtime Database not open to read
  • #62Firestore not open to read
  • #63Firebase Storage not open to list
  • #147Database functions not callable by anyone
Subdomains0 tests + 1 coming soon
  • #76Subdomains found in public certificate logscoming soon
Access control5 tests + 1 coming soon
  • #96Data isolation between users
  • #97User files and profiles isolated
  • #98Normal users can't reach admin functionscoming soon
  • #148Users can't make themselves admin
  • #149Users can't upgrade their own plan
  • #150Users can't approve themselves
Abuse protection2 tests
  • #99Login and sign-up rate limits
  • #151API rate limits
Input handling1 test
  • #100Forms and inputs handle unsafe input safely
Backend1 test
  • #101Edge/serverless functions require login where needed
Database1 test
  • #102Missing indexes (from owner-supplied schema)
Account safety1 test
  • #103Password reset links expire and work once