Skip to content
ScanAnt

Firebase security check: Firestore, Realtime Database and Storage

A Firebase web config is public by design, so security lives entirely in your rules. A rule left in test mode or written as "any signed-in user" quietly exposes everything. ScanAnt detects your Firebase project and checks what an anonymous visitor can reach, and what your rules say if you upload them.

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.

  • Firebase config detection

    Quick scan

    We find your project settings in the page. They are public by design and are labelled as normal.

  • Firestore collections

    Verified scan

    Whether collections found in your bundle can be read without signing in. We save names and counts, not documents.

  • Realtime Database

    Verified scan

    Whether the database root or paths answer a plain read request from anyone.

  • Firebase Storage

    Verified scan

    Whether anyone can list the files in your bucket. Only names are noted, never contents.

  • Remote Config

    Deep scan

    Whether the Remote Config template is readable by any client, since it may include feature flags or values you thought were private.

  • Auth providers

    Deep scan

    Which sign-in methods your project exposes, so you can compare them with what you intend to offer.

  • Rules in uploaded code

    Code scan

    In firestore.rules, database.rules.json and storage.rules we flag rules that let anyone read or write, rules that let any signed-in user reach everyone's data and rules still in test mode until a date.

  • Keys and headers

    Quick scan

    Leaked secret keys in bundles and the usual header and cookie checks on the public page.

  • 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

  • Leaving rules in test mode

    Test-mode rules are open to everyone until a date, and many projects never change them.

  • Writing allow read, write: if request.auth != null

    Every signed-in user, including a throwaway account, can reach every document.

  • Storing sensitive fields in publicly readable documents

    Rules apply per document, not per field.

  • A Storage bucket that lists all files

    File names alone can reveal customers, invoices or internal structure.

  • Trusting client-side checks

    The browser can be edited, so only server rules count.

How to fix it

  1. Replace test-mode rules with rules that compare request.auth.uid with the document owner.

  2. Split public and private data into separate collections so rules can differ.

  3. Restrict Storage rules by path and owner, and never allow list for public users.

  4. Test your rules in the Firebase emulator or Rules Playground before deploying.

  5. Rescan and review the Remote Config template for values that should not be public.

Questions

Is the Firebase API key a secret?

No. Web API keys identify the project and are meant to be in your front end. What protects your data is the security rules and, where relevant, API restrictions.

Does the scan read my documents?

It requests at most a couple of items to prove access and stores only the fact of access, names and counts. Document contents are never saved.

Do you test Firebase Auth sign-up?

We report which sign-in providers the project exposes. We do not create accounts or try to register users in your project.

Can I check rules before I deploy?

Yes. Upload the project as a ZIP and the code scan reads your rules files without touching the live database.

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 →