Skip to content

Free tools

Eight front doors.One engine behind them.

85 checks, one report, and a page for whichever word you searched — security, SEO, AI visibility, or the tool that generated your app. None of them is a separate product with its own scanner.

  • 85 checks per scan
  • No agent to install
  • Free account, no card
  • One runs without an account

A tool page is a search result. The scan behind all eight is the same one.

Runs without an account

The Supabase
RLS checker

Paste a project URL and the publishable (anon) key your frontend already ships, and the same Level-1 engine asks what that key can read. Severity counts and finding titles come back; the descriptions, evidence and remediations are what a connected account opens. Nothing is stored — the key you type is never written down, because nothing on this endpoint writes to a database at all.

10
tables probed per run
5
checks per project a day
20
checks per address a day
0
keys stored
Check a projectThe daily caps exist because this endpoint probes third-party backends by design, and a free scanner must not become a paid one for somebody else.

Shared by all eight

What every tool
here has in common

The parts that do not change whichever page you came in through.

  • Read-only, every time

    A scan requests pages the way a browser and a crawler do. It never logs in, never submits a form of yours, never calls a state-changing endpoint, and refuses private and metadata addresses before a request leaves. The two checks that touch a backend run against a project you pasted the key for, or one you have connected.

  • A free account, no card

    Scanning needs an account; the account needs a code to your email and nothing else — no password to invent, no payment details to hand over. What a report looks like to someone without one is on the privacy and sharing pages.

  • Every number here is derived

    85 checks, and the per-pillar counts above, are read from the check registry at build time. A check that stops existing leaves these pages in the same commit; nothing here can advertise coverage the engine does not have.

  • Engine 1.24.12, and honest about failures

    Every scan records the engine version it was measured with, so score changes can be told apart from coverage changes. If a check errors, it is recorded as our failure rather than your finding, and the pillar it belongs to is marked provisional.

Pick whichever
describes your site

They all run the same 85 checks and produce the same report. The URL you came in through only decides which findings get explained first.

Scan your site

ScanlyFix

Security, SEO and AI-answer-engine scanning for anything you put on the internet. Paste a URL, read the evidence, run the fix.

Home