Download websites that use GLPI

About GLPI

GLPI was never designed to be seen from the outside. Teclib maintains it as an IT asset management and service desk system, the software an organisation uses to track its own hardware, software licences, incidents, and change requests, and the natural home for such a tool is an internal network that staff can reach and the public internet cannot.

As of October 2026 we detect GLPI on 213 sites, and that figure has to be read with its origin in mind. A public web scan can only see the instances that face the public web. What we measure is therefore not the installed base of GLPI but the reachable subset of it, which is a different quantity and, for several kinds of reader, a more interesting one.

Version data points the same way. Our records carry 4 distinct version strings for GLPI, a narrow spread for a project released in 2003 and developed continuously since, and the string we record most often is 0.83.6. A service desk that old sitting on the open internet is not a neutral fact. GLPI holds asset inventories, ticket histories, and staff accounts, so an exposed and unpatched instance is at once a finding for a security researcher and a lead for anyone selling managed ITSM, upgrade work, or hosting to organisations that clearly run their own infrastructure.

An internet-facing instance also implies a particular kind of organisation. GLPI is normally paired with network discovery agents that inventory machines automatically, which means an installation exists because somebody had enough hardware to be worth tracking. Reaching it from outside usually points to distributed staff, remote sites, or field technicians who needed access, and that is the profile of an organisation past the size where spreadsheets work and inside the range where IT services are actually purchased.

Licensing shapes who appears in the list too. GLPI is distributed under GPL v2, which means there is no purchase record to correlate against, no vendor customer roster, and no reseller channel that covers adoption. For an open source tool the detected footprint is often the only view of the market that exists, and that is why the raw list matters more here than any headline figure.

Some limits are worth stating plainly. Our Issue trackers records for GLPI do not currently carry a country concentration we would stand behind, so a reader assuming a particular regional profile should treat the assumption as untested. Detection itself reads markers in the delivered login page and asset paths, so a deployment behind a VPN, an SSO portal, or a renamed install directory falls out of scope entirely. What survives those filters is still the thing no per-domain lookup can produce: the full set of organisations exposing an instance to the internet, in one file, ready to be sliced by top level domain or joined against the rest of a stack.