Tools / Exposed files checker

Exposed files checker: .env, .git, backups & debug pages

Find out whether your website is serving files it should never serve: environment files with passwords and API keys, the .git folder with your source code, database dumps, site backups, phpinfo and debug consoles, and JavaScript source maps. One request per location; contents are never shown.

Why exposed files are so dangerous

Attackers do not need to break in when a website hands over its secrets. Automated bots request /.env, /.git/config and /backup.sql on millions of sites every day, because one hit gives them database passwords, cloud keys and payment API tokens. These leaks usually come from a deployment that copied the whole project folder into the web root, an editor backup, or a debug setting left on after launch.

What it checks

A location counts as exposed only when it returns 200 and its content matches that file type, so a site that answers every address with a page cannot produce false alarms. Findings name the file and the fix; file contents are never displayed.

If something is found

  1. Remove the file from the web root, or block the path in your web server (dotfiles, .git, backups).
  2. Rotate every secret it contained: removing the file does not help if a bot already downloaded it.
  3. Fix the deployment so only the public folder is published, then run the check again.

Frequently asked questions

Is it safe to run this on my production site?

Yes. It sends one ordinary GET request to each location, at most eight at a time, with no attack payloads, no password guessing and no form submissions. It is the same kind of request a search engine makes.

Why do I have to confirm I own the site?

The check looks for sensitive files, so it should only be run by the site owner or someone with permission. We ask for that confirmation and refuse government and other restricted domains.

The check found nothing. Am I safe?

It checks the most common leaks, not every possible file name, and it cannot see anything behind a login. It is a quick hygiene check; a penetration test goes much further.

Our server returns 403 for these paths. Is that good?

Yes. A 401 or 403 means the server blocks the path, which is exactly what you want for dotfiles and admin tools. The report counts how many were blocked.

Related checks