Skip to content
ScanAnt

What we check

Four layers, from what any visitor can already see to the server behind your CDN. Everything beyond the passive layer runs only on sites you have proved you own.

  • Passive scan

    Secrets in public JavaScript, security headers, source maps, HTTPS and mixed content, stack detection. Reads only what every visitor receives. No signup.

  • Verified deep scan

    After you prove ownership: exposed files and admin paths, known CVEs for your framework and libraries, XSS and injection probes, open redirects, Supabase and Firebase access rules, rate limits.

  • Code scan

    Upload your source as a ZIP: hard-coded secrets, vulnerable dependencies, unsafe patterns and access-control logic, with an optional AI review.

  • Server behind a CDN

    We look for your origin server's real address and test it directly, so a missing firewall rule does not leave the back door open.

  • Stack-specific checks

    We detect your framework, server, backend and CMS first, then run the checks that matter for that stack instead of a generic list.

  • Fixes you can use

    Every finding has an explanation, evidence and a fix: manual steps or a ready-to-paste prompt for Lovable, Cursor, Bolt and Replit.

Stack-specific guides with what we check, common mistakes and fixes.

Security checks →

How it works

  1. Paste your URL

    Enter the address of your live app. No account, no code access, nothing to install.

  2. Passive scan, instantly

    We load your public page and scripts like a normal browser, within a small request budget, and look for known problems.

  3. Prove ownership, go deeper

    Add a DNS record or file to show the site is yours, then run the deep scan. Get a report with evidence and a fix for every finding.

What happens during a scan

No magic and no guessing. Here is exactly what ScanAnt does with your site, step by step.

  1. 1

    Open the page

    We load your page once, like a visitor, with our own User-Agent (ScanAntBot). Only public addresses, a few redirects at most.

    GET only
  2. 2

    Read the code

    We download the JavaScript and source maps your page already serves and look for keys, API addresses and database config.

    public files
  3. 3

    Recognise the stack

    Next.js, React, Vue, Supabase, Firebase, WordPress and more: we work out what the app is built with and pick the checks that fit.

    automatic
  4. 4

    Run the checks

    Leaked secrets, security headers, HTTPS, exposed files. After you prove ownership: database tables, storage and login settings too.

    passive · full
  5. 5

    Write the report

    Each problem gets a severity, where it is, why it matters and a ready fix prompt for your AI builder. Secrets are shown masked.

    link · PDF

Passive scan

any site · no signup

What we do

  • Reads only what your site shows every visitor
  • Finds leaked keys, missing headers, HTTPS problems and exposed files
  • Recognises your stack and explains each finding

What we need

Just the address of the site

What we never do

No requests to your database, storage or login

Full scan

your sites only

What we do

  • Everything in the passive scan
  • Checks who can read your Supabase tables (at most 1–2 rows as proof; values are never stored)
  • Checks storage buckets, login settings and harmless probes you switch on

What we need

Proof that the site is yours: a DNS record or a file

What we never do

No changing or deleting data, no password guessing, found secrets are never used