Download websites that use otrs

About otrs

Finding Perl behind a public web application is unusual enough to be a signal by itself. The language largely stopped being chosen for new web projects a long time ago, so a Perl application still answering requests is almost always a system that was bought once, fitted into a company's processes, and kept running because replacing a ticket queue means retraining everyone who touches it. otrs is that kind of system, a service desk and ticketing product sold by OTRS AG under a Proprietary licence and on the market since 2001.

Our taxonomy files the entry under Issue trackers, which undersells it. A helpdesk suite of this shape handles incidents, change requests and service catalogues for internal IT as often as it talks to customers, so the presence of the software on a public hostname usually means something more specific than a support widget. Somebody runs their own service desk, on their own infrastructure, at a subdomain named support or helpdesk or tickets, with staff logging in through a form the rest of the internet can reach but not use.

Presence therefore implies an organisation large enough to have a service desk team, a preference for self-hosting over a subscription, and a procurement decision made deliberately rather than picked up as a bundled feature. Companies that install their own ticketing tend to have compliance reasons, data residency requirements or an integration with directory and monitoring systems that a hosted product would not accommodate.

The richest column on this entry is the version. We record 10 distinct release strings across the installs we detect, clustering on 6.0.28. A self-hosted application upgraded by hand produces exactly that distribution, a heavy cluster plus a long tail, where each release in the tail is an organisation that upgraded once and then left the system alone for years. For a researcher, the spread is the point, because a patch level is what separates an instance somebody still maintains from one nobody has logged into as an administrator in a long time.

Detection has clear edges that should be stated rather than smoothed over. What we read is the login page and the markup the application serves, so an instance published only inside a corporate network, or reachable only through a VPN or an address allowlist, never appears at all. An administrator who strips the release banner is counted with no version. As of October 2026 we detect otrs on 26 sites, which measures publicly reachable installations rather than licences sold, and no country breakdown exists for this entry, so geography has to be derived from the domains themselves.

Competing service desk vendors want a displacement list. Integrators and consultancies want the installations they could support. Security teams want the version distribution. Asking about a single domain answers whether one company runs the software. The downloadable file answers which companies do and on what release, and the second question is the one that cannot be assembled a domain at a time.