Download websites that use Joomla

About Joomla

Every long lived content management system eventually becomes two things at once. There is the project, with a current release and a roadmap, and there is the population of installations that stopped following it years ago and still serves pages perfectly well.

Joomla began in 2005 as a fork of an earlier project, is written in PHP, is published under the GPL v2 licence and is stewarded by Open Source Matters rather than by a company. Governance by a volunteer foundation shapes everything that follows. Nobody can force an upgrade, nobody operates a hosted edition that silently keeps every customer current, and the outcome is a long tail of installations running exactly as they were configured on the day somebody finished the site and moved on.

As of September 2026 we detect the system on 527,928 sites and resolve 51 distinct versions across them. The release we record most often is 1.5, a branch whose active development ended a long time ago. Fragmentation on that scale is what most buyers of this list actually come for, because it splits one label into groups that behave completely differently. A site on a current branch has someone maintaining it and a support contract somewhere. A site on a branch that stopped receiving fixes has an owner who is either unaware or unwilling, and the difference decides whether that domain is a support prospect, a migration prospect or a liability.

Geography adds a second split. Germany accounts for 134,713 of the installations, a distribution unlike that of most web platforms, reflecting where the system took root among agencies, associations, schools and public bodies. .com still leads the domain endings, so the audience is not confined to any national suffix. Where a platform is administered and where it sells turn out to be separate questions, and a list that carries both fields lets you ask them separately.

A lookup on one domain tells you a site runs the system. The downloadable list answers what needs the whole set: how many installations of a given branch exist in a given country, how fast the population migrates between branches from one export to the next, which hosting providers concentrate them, and how large the unmaintained segment really is. Extension vendors size their market this way, agencies find migration work this way, and security teams use it to bound exposure when an advisory lands on one specific branch.

Version detection deserves a plain caveat. Releases are exposed through files and markup that an administrator can remove and that hardening extensions routinely suppress, so a share of installations are recognised as the system without a resolvable version, and a smaller share are missed altogether. Reported versions can also lag reality where a site was patched without changing the fingerprints we read. We publish what the crawl observed with the date attached, we count what is visible rather than estimating what is hidden, and the version breakdown should be read as the shape of the visible population rather than as a complete inventory.