Download websites that use imperia CMS

About imperia CMS

A content management system that has been shipping since 1995 and is written in Perl tells you most of what you need to know about the organizations that run it. imperia CMS comes from imperia AG, a German software house, and is sold under a Proprietary license into institutions rather than downloaded by hobbyists. Buyers are corporations, public sector bodies and financial institutions with editorial approval chains, retention rules and multilingual publishing obligations, and the system is built around workflow, role separation and publishing the same content repository out to websites, portals and other digital channels.

Software bought that way is chosen once and then lived with for a decade, which is why the deployment pattern looks nothing like a mass market platform. The version data shows it directly. We resolve 22 distinct version strings across the installed base, and the stamp that recurs most in our fingerprints is 11.4.5_1. A spread that wide is not neglect. Nothing here updates itself. Each customer upgrades on its own schedule, usually as a funded project with an integrator involved, so the version field is effectively a map of upgrade budgets and contract cycles rather than a measure of how fast the vendor ships.

For a security or procurement researcher, that map is the useful part. Public sector and enterprise sites running an older release of a Perl publishing system are a defensible research target, and the version string attached to each row is what makes the question answerable at all.

As of October 2026 we identify imperia CMS on 235 sites. Comparing that number against open source platforms is the wrong instinct. An installation here is typically one large organization publishing many sections, subsites and language variants behind a handful of domains, so the site count understates both the volume of content managed and the size of the contract behind it. Detection also depends on markers that hardened deployments strip. An install sitting behind a reverse proxy with rewritten paths and no generator hint can run for years without being visible to us, so the real base sits above what we publish.

The people who want the whole list are competing CMS vendors and integrators building replacement pipelines, security teams assembling an exposure inventory for one specific stack, and analysts tracking where Perl still runs production publishing in Europe. A per domain lookup answers none of those questions, because each of them is a question about a population and not about a site.

The download gives that population in one file, with the resolved version beside each domain and country and top level domain fields to segment on. Two snapshots compared show which installs were upgraded, which were replaced outright, and which have not moved at all, which is the difference between guessing that an old enterprise system is still out there and knowing exactly where.