SimplyScan logoSimplyScan
What We ScanPricingFree ToolsBlogCreate AccountLog In
  1. Home
  2. Free Tools
  3. Exposed Files Scanner
Free Tool

Free Exposed Files Scanner

Check whether your site accidentally exposes .env, .git/config, backup archives, or other high-risk files.

Free account required to run the check. What you type here is kept through sign-in.

How to use it

  1. Enter your site's URL, for example https://example.com.
  2. Run the check. SimplyScan requests a list of high-risk paths at the site root and app folder.
  3. Read the result for each path. Only a response containing that file's real signature counts as exposed, so a fallback page that answers 200 for every path doesn't count.
  4. Remove anything exposed from the deployed files, rotate any secret it contained, and check again.

Example

Input

https://example.com

Result

Grade D · 1 exposed

✗ /.env               exposed (environment file signature)
✓ /.git/config        not exposed
✓ /.git/HEAD          not exposed
✓ /backup.zip         not exposed
✓ /terraform.tfstate  not exposed
… and the remaining paths

What the paths reveal

.env
Environment files often hold database passwords and API keys. Anyone who downloads one has them.
.git/config and .git/HEAD
An exposed .git folder can let someone download your whole source history, including secrets committed and later deleted.
Backups (backup.zip, wp-config.php.bak)
Archives and editor backups are served as plain downloads and often contain configuration.
terraform.tfstate, docker-compose.yml, Dockerfile
Infrastructure files list servers, internal names and sometimes credentials.
.npmrc, .yarnrc.yml, composer files, swagger.json
Package-registry tokens, dependency lists and API maps that help an attacker plan.
Unverified
A path didn't answer completely, so the tool can't say either way. Run the check again later.
Grades
A means nothing exposed, D means one file, and F means two or more.

Stop serving the files

Every platform: first rotate the secrets

1. Create new keys/passwords in each provider's dashboard.
2. Update them in your host's environment settings.
3. Revoke the old ones.
4. Then remove the file from the deployed output.

Once a file has been public, assume someone has a copy. Deleting it isn't enough.

Nginx

location ~ /\.(?!well-known) {
  deny all;
}

Blocks every dot-file and dot-folder except /.well-known/.

Static hosts (Vercel, Netlify, Lovable)

# Keep secrets out of the published folder
.env
.env.*
*.bak
*.zip

Add these to .gitignore and set real secrets in the host's environment variables, never in a file inside public/ or dist/.

Go deeper

  • How to Check Your Website for Env-Var Leaks and Exposed Files
  • Environment Variables Security: Stop Leaking Secrets to Production
  • How to Remove Secrets from Environment Variables and Git History

Page updated 21 November 2026

Frequently asked questions

Do you download the file contents?

The tool reads at most 200 KB per response to verify a file-specific signature. It never returns file contents or credentials. HTTP 200 alone does not prove a file is exposed.

Which paths are checked?

Environment and Git files, backups, API schemas, Docker and Compose configuration, npm and Yarn configuration, Composer manifests and lockfiles, Terraform state, and node_modules or .terraform directory listings. Paths are checked at the site root and the app folder.

Does the tool download my files?

It reads at most 200 KB of each response to look for the file's signature. Contents and secrets are never shown in the result.

My host shows the homepage for every path. Is that a problem?

No. That's a fallback page, and the signature check recognises it as not exposed.

Want the full picture?

This tool covers one narrow check. A full SimplyScan runs 60 checks across 14 categories · exposed keys, RLS, XSS, auth, and speed · in 30 seconds.

Run a full security scan

Related tools

Supabase RLS Checker

Discover tables advertised by your public API and check whether anonymous reads return rows.

SSL Checker

Instantly verify a site's SSL certificate · trusted chain, hostname match, issuer and days until it expires.

Security Headers Checker

Get an A-F grade on your site's HTTP security headers, including CSP, HSTS, and cross-origin isolation policies.

SimplyScan logoSimplyScan

Security Scanner for Vibe-Coded Apps.

Product

See What We ScanHow It WorksView Pricing

Resources

Security BlogSecurity ChecklistTrust BadgeUptime MonitoringIntegrationsMCP Server (Claude, Cursor & Windsurf)API DocumentationBackend Audit GuideThreat Detection GuideFAQTerms of ServicePrivacy Policy

Platforms

All platforms →Lovable ScannerBolt.new ScannerCursor ScannerReplit Scannerv0.dev ScannerWindsurf ScannerBubble Scanner

Free Tools

All free tools →SSL CheckerSecurity HeadersDNS Security CheckerCORS TesterJWT DebuggerCSP EvaluatorHash GeneratorSEO Checker

Account

Create AccountLog In

© 2026 SimplyScan. All rights reserved.