Guide
Is your .env or .git folder public? How to check
Files that are meant for you can end up published with your app, and anyone who knows or guesses their address can open them. It takes a minute to check, and it is one of the most useful minutes you can spend.
Each check below is an ordinary address typed into a browser, on your own app only. You should see a “not found” page every time. You do not need to be a developer.
1The .env file
A .env file holds the keys and passwords your project needs to run. If it is published with the app, anyone who opens its address can read all of them.
Check it yourself: Open yourapp.com/.env in your browser, with your own address. A “not found” page is what you want. If you see lines of settings or keys, it is exposed.
What to do: Take the file out of what is published, and tell your AI builder to make the app answer “not found” for it. Treat every key that was in it as leaked and replace each one.
2The .git folder
The .git folder is the project's whole history. If it is published, a person can download the project's code, including old versions with keys that were later deleted.
Check it yourself: Open yourapp.com/.git/config. “Not found” is right. If you see text that mentions a repository, the folder is exposed.
What to do: Take the folder out of what is published, and make your host answer “not found” for it. Replace every key that was ever in the project.
3Backups and test pages
Database exports, backup files and test pages that show your server's settings are easy to leave in a published folder. They can hold personal data, keys and the details of your setup.
Check it yourself: Try a few names you may have used, with your own address, such as yourapp.com/backup.zip and yourapp.com/phpinfo.php. Each should answer “not found”.
What to do: Delete the file from the published folder, replace anything secret that was in it, and keep backups outside the folder your host publishes.
4Folders that list their files
If a folder has no front page and your host lists what is inside, anyone can see every file name, including ones you did not know were there.
Check it yourself: Open the address of a folder that holds files, such as yourapp.com/uploads/, with your own address. You should see a page or “not found”, not a list of file names.
What to do: Switch off folder listing in your host's settings, or ask your AI builder to do it, and look again.
What a check can and cannot tell you
Passing these checks does not prove an app is safe. It means these problems were not found. A full review also looks at how your app handles each person's data, and that takes someone who reads the code or tries to get past the sign-in.
Check them all from the outside
Hardex scans a live app the way a stranger on the internet would, with nothing to install. By default it only reads: it never changes anything in your app. It looks for the problems above where they apply to your app, and more, then reports what it found.
What each plan includes is on the plans page.
Scan your app