Skip to content
ScanAnt

A free website vulnerability scanner that explains every finding

ScanAnt starts with a passive look at your public pages, then goes further on sites you have proved you own: known framework CVEs, injection and redirect probes, exposed files and open services. Every finding comes with evidence, a severity and the shortest fix we can give you.

Free, no signup. We only read what your site already shows every visitor.

What we check

Each item is tagged with the scan that reports it. The quick scan is free and needs no signup. The others run only on sites you have proved you own.

  • Front-end code patterns

    Quick scan

    Page code that likely writes URL data into HTML (DOM XSS), redirects to any address from the URL, trusts postMessage from any origin or builds tokens with Math.random().

  • Vulnerable front-end libraries

    Quick scan

    Libraries in your public JavaScript that match published vulnerabilities, reported with the version we found.

  • Reflected XSS and SQL error probes

    Deep scan

    Harmless markers in GET parameters that show whether a value is echoed back unescaped or breaks a database query. No forms are submitted.

  • Template injection and path traversal

    Deep scan

    Safe probes for server-side template evaluation and file-path parameters. We record only that it happened, never file contents.

  • Open redirects

    Deep scan

    Whether a parameter can send your visitors to any other website, which phishing campaigns rely on.

  • Framework and server CVEs

    Deep scan

    We detect the framework or CMS and its version and compare it with known issues, including a harmless check for the Next.js middleware bypass CVE-2025-29927.

  • Exposed files and endpoints

    Deep scan

    Around 250 known paths: backups, configs, admin panels and debug pages, checked against signatures instead of guessed from status codes.

  • Login rate limit

    Deep scan

    With a separate level-3 opt-in, up to 10 attempts with random, non-existent credentials show whether your sign-in slows down guessing. Your own login may lock briefly.

  • Quick scan: No signup. Reads only what every visitor receives.
  • Deep scan: After you prove ownership and tick the deep option.

No scan can promise to find every problem. A clean result means no known problems were found on what the scan could see.

Common mistakes

  • Echoing user input back unescaped

    Reflected XSS lets an attacker run script in a victim's session through a crafted link.

  • Running software past its end of life

    Unsupported servers and frameworks get no security patches, so published exploits keep working.

  • Redirects that trust a URL parameter

    They turn your trusted domain into a launch pad for phishing.

  • Building SQL from pasted strings

    A single injectable parameter can expose the whole database.

  • Leaving admin and debug paths public

    They give attackers the version, the structure or the login for free.

How to fix it

  1. Fix the cause shown in the finding: escape output, use parameterised queries and validate redirect targets against an allow-list.

  2. Update the flagged framework or library, or move off a version that no longer gets patches.

  3. Remove or protect admin, debug and backup paths, and put the admin area behind a login and an IP rule.

  4. Rescan after each change to confirm the finding is gone.

Questions

Does it find every vulnerability?

No scanner does. ScanAnt reports what it can observe from outside and from the source you upload. Treat it as a fast first line of defence next to code review and, for critical systems, a human penetration test.

Which checks need me to prove ownership?

Everything that sends requests beyond your public pages: probes, path checks, CVE tests and rate limits. The server checks verification before each run. The passive scan needs nothing.

Will the probes break or change my site?

No. Probes are read-style GET requests with harmless markers. We never submit forms, delete data, guess passwords from a list or run load tests. Anything that could leave a trace is stated before you start.

Can it test an app behind a login?

The deep scan can use test accounts you provide to check that one account cannot read another account's records. Without them, the scanner sees only what an anonymous visitor sees.

Do I get a report I can share?

Yes. Reports have a share link and a PDF, and each finding lists evidence, severity and a fix.

Run the scan now

Free for any public site, no signup. Need the verified, deep or code scan? Choose the level on the scan page.

Choose a scan level →