Download websites that use Atlassian Confluence

About Atlassian Confluence

Confluence is supposed to be private. A wiki holds runbooks, meeting notes, architecture decisions and half-finished policy, so the normal state of an instance is behind a login or a private network where no crawler will ever reach it. Every instance visible from the open internet is already unusual: either the organization publishes documentation deliberately, or a login page has been left facing outward, or something is open that was meant to be shut.

The next thing the record tells you is deployment model. Cloud tenants of Atlassian products live on the vendor's own domain, so a Confluence fingerprint on a company's own hostname points at a self-managed installation running on infrastructure that company controls. Self-managed means a Java application, a database, an upgrade schedule and somebody carrying responsibility for all three.

As of October 2026 we see Atlassian Confluence on 55 sites across 23 distinct versions, with 8.7.2 recurring more than any other in our data. Version spread that wide over a group that small is the whole story of self-hosted enterprise software. Upgrades are projects, projects get deferred, and instances drift apart from one another year by year. The version field is also what makes this particular record commercially interesting, because for a product with a long public advisory history the running release is a direct statement about exposure.

Being precise about that field matters more than quoting it. We read the version the application reports in its own markup or headers, which an operator can suppress, and we cannot see whether a vendor patch has been applied on top of the reported release. A reported version is evidence, not a verdict, and anyone acting on it should confirm against the host first. Instances behind a proxy that rewrites those hints are missing from our count altogether, so the visible population is smaller than the real one.

Three audiences want the list, for different reasons. Security teams and researchers want the population of publicly reachable self-managed instances, because a wiki is where an organization writes its internal detail down. Consultancies want it because every remaining self-managed instance is a migration project waiting to be quoted, and the version distribution tells them which quotes are urgent. Competitors want it as a map of accounts that already pay for a commercial documentation platform, which is a shorter conversation than persuading a company to buy one at all.

A per-domain check answers whether a single company runs it. The export answers what only exists in aggregate: how many self-managed instances remain visible, how the version distribution is shifting between refreshes, which sectors and hosting providers they cluster in, and how fast the group shrinks as organizations move to hosted editions. Sold under a Proprietary license since 2004 and priced per seat, the product leaves no public customer list, so an outside fingerprint census is the only view of the installed base available to anyone who does not work at the vendor.