DataHow safe they are

How many .lt websites leave internal files public?

1,470.lt websites expose at least one internal file or page

That is 2.0% of 73,386 inspected sites. The most common finding is a readable WordPress debug.log (1,123 sites), followed by a downloadable backup (158) and an exposed .git directory (126).

What this number does not mean. File contents were not read or stored. Only the fact that the file opens without a login and starts with the expected format was recorded.

snapshot 16 November 2026DOI 10.5281/zenodo.24282573CC BY 4.0

Critical exposures (severity 3)

FindingWebsitesShare
Readable WordPress debug.log1,1231.5%
Downloadable site archive or database dump1580.22%
Exposed .git directory1260.17%
Public phpinfo() page980.13%
Readable .env file450.06%
Readable error_log370.05%
Exposed .svn directory210.03%
Readable copy of wp-config.php200.03%

Share of the 73,386 websites whose home page was inspected. File: summary_findings.csv

Other exposed files and logins (severity 2)

FindingWebsitesShare
Readable composer dependency file6530.89%
WordPress REST API lists user names2390.33%
Public phpMyAdmin login840.11%
Readable .DS_Store file490.07%
Public Apache status page400.05%
Readable package.json350.05%
ownCloud or Nextcloud discloses its version130.02%
Public Adminer login70.01%

Share of the 73,386 websites whose home page was inspected. File: summary_findings.csv

Method and limits

A backup's file type was confirmed from its first bytes, the whole file was not downloaded. No login to phpMyAdmin or Adminer was attempted.

Findings about particular websites are not published: the dataset holds no domain names, IP addresses or paths.

The host list comes from Common Crawl, not from the registry zone file, so it leans towards sites that are linked from elsewhere. This is the 16 November 2026 snapshot: 125,935 of about 136,000 listed hostnames were checked.

All files and the method

In the wiki

How does your own website look? Check your website →