Skip to content
ScanAnt

Replit security check for apps built or deployed on Replit

A Replit app is often a real server: a Node or Python backend that you or Replit Agent wrote, with its own routes, database and environment. That makes its mistakes different from a front-end-only app. ScanAnt checks the public side now and the server-side exposure once you prove the site is yours.

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.

  • Replit detection

    Quick scan

    We recognise .replit.app and .replit.dev addresses and Replit markers, and tune the report to a server-style app.

  • Secrets in the shipped front end

    Quick scan

    Keys that reached the browser even though Replit Secrets exist for the server side, shown masked.

  • Headers, cookies and HTTPS

    Quick scan

    Security headers, session cookie flags and mixed content on the public page.

  • Open API routes

    Verified scan

    Endpoints that return configuration, secrets or user lists without sign-in, and API documentation or GraphQL schemas open to anyone.

  • Debug pages and verbose errors

    Verified scan

    Stack traces on malformed requests and debug or admin pages that open without a login screen.

  • CORS policy

    Verified scan

    Whether any website can read responses or make signed-in requests to your API.

  • Server stack and ports

    Deep scan

    We detect Express, Flask, Django or similar, check it for known issues and look for app or database ports reachable directly.

  • Code issues in your repl

    Code scan

    Upload the project: routes without authentication, missing owner checks, SQL built from strings, unrestricted public endpoints and secrets written into files.

  • Quick scan: No signup. Reads only what every visitor receives.
  • Verified scan: After you prove you own the site. Read-only.
  • Deep scan: After you prove ownership and tick the deep option.
  • Code scan: You upload your project as a ZIP.

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

  • Hard-coding a key in a file instead of Replit Secrets

    Anyone who can view or fork the project, or find the key in a bundle, gets it.

  • Running a development server as the public one

    Debug mode shows stack traces and sometimes an interactive console.

  • CORS set to allow every origin with credentials

    Another site can act as your signed-in user.

  • An API route that lists users or config for testing

    Test routes survive into production and nobody remembers them.

  • No rate limit on login or forms

    Spam and credential guessing cost you nothing to start.

How to fix it

  1. Move every key into Replit Secrets and read it only on the server.

  2. Turn debug mode off in the deployment and run a production server.

  3. Restrict CORS to your own origins and avoid credentials with a wildcard.

  4. Add authentication and ownership checks to every route that returns user data.

  5. Add rate limits to sign-in and public forms, then rescan.

Questions

Can I scan a .replit.dev preview address?

Public-page checks work on any reachable URL. Ownership proof is per host, so use the address your users will actually visit when you want the full scan.

Does it read my Replit Secrets?

No. We cannot see them. We only look at what your site sends to a visitor and, if you upload the code, at what the files contain.

Will it slow down my deployment?

Scans use a small request budget, a clear User-Agent and a polite pace. Load and denial-of-service tests are never part of a scan.

What about my database?

Databases that are not reachable from the internet are not touched. We report database or admin ports that are open directly to the internet in the deep scan.

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 →