Every check / env-file-exposed
Is the file that holds your website's passwords published for anyone to read?
On a domain you have proved is yours, we ask for /.env and /.env.local, the files many sites keep their passwords and keys in.
How it decides
The check speaks up only when what comes back is written like one, NAME=value, and it says what kinds of secret the file holds without ever recording a value.
Why it matters
Anyone who types that address gets whatever the file holds, often the database password, payment keys and an email login, in plain text.
In more detail
Every value in it has to be treated as public and changed, starting with the database.
Who fixes it, and where it runs
- Who usually fixes it
- Your hosting company
- Which plan runs it
- The Business plan
- Proof you own the site
- Needed. It asks your server for things an ordinary visitor never requests, so it waits until you prove the domain is yours.
More about this check
- Who it is about
- An intruder
- Listed under
- Things that should not be public
- Its name in a report
env-file-exposed
See what the free scan finds
The free scan runs 62 checks on any address, and this is not one of them: it runs on the Business plan, once you prove the domain is yours.