Every check / git-directory-exposed
Can anyone download your website's source code from the .git folder?
On a domain you have proved is yours, we ask for /.git/HEAD and /.git/config, the files a developer's change history starts from.
How it decides
The check speaks up only when what comes back looks like the real thing, a ref line or a [core] section, so a server that answers every address with a page of its own is not reported.
Why it matters
With that folder, anyone can rebuild your website's source, including every password and key that was ever written into it, even ones deleted later.
In more detail
Free tools do it in about a minute. Blocking it is quick; every credential that was ever committed then needs changing.
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
git-directory-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.