Guides

Practical guide: Exposed Files Checker

Check common .env, Git configuration and backup paths on your authorized website.

Understand the limits

Requires a domain authorization file. Matches content signatures on five fixed paths, rather than treating every HTTP 200 as a leak. No sensitive content is returned.

What to change

Move backups and environment files outside the public directory. Restrict access at the origin and CDN, then retest the authorized paths. Rotate exposed secrets if a real leak is confirmed.

How to use it

  1. Enter the URL of a public website.
  2. Run the check and read the evidence alongside its coverage.
  3. Review the recommendation, back up your configuration and test changes before publishing.
Exposed Files Checker