Download websites that use Zend

About Zend

Zend is a brand that was stretched across several products at once, and a detection hit does not tell you on its own which of them is on the page. An application framework, a commercial PHP application server and a set of runtime accelerators all shipped under the same name, and a site can carry traces of any of them. Our record credits the vendor as Perforce, carries the license BSD, dates the technology from 2006 and names PHP as the language behind it. Ownership of the commercial side of the brand has moved on since those products were launched, so the vendor field is best read as a historical attribution rather than as the company selling under the name today.

As of October 2026 we detect Zend on 139 sites. Server side software is only visible when it leaves something behind, a response header, a cookie name, a predictable asset path under a directory nobody renamed. Nothing forces a careful deployment to advertise any of that, so the figure is a floor rather than a census, and the sites that stay hidden are disproportionately the well administered ones. A count of this kind measures what is exposed, which is a different thing from what is installed, and any serious use of it has to start from that distinction.

Version data is where the record turns interesting. We hold 24 distinct version strings, and the value that recurs most often is 5.0. Version strings scattered across a codebase whose active development moved on years ago, into community stewardship and a new project identity, describe an installed base that is not moving in step with anything. Part of it is frozen inside applications that were shipped once and then left to run. Part of it is bundled by hosting panels and appliance images that upgrade on a schedule of their own, if at all. A framework rarely leaves a site because the framework got old. A framework leaves when the application around it is rewritten, and rewrites are budgeted, not automatic.

For a researcher the practical question is who still has PHP of this vintage in production and what it is doing there. Software of this generation turns up in enterprise intranet tools, in vendor appliances with a web console bolted on, in government and university systems that were commissioned once, and in agency built applications that were handed over and never touched again. A list of those domains reads as a prospecting list for a modernization practice, an addressable market for a commercial PHP support vendor, an exposure map for a security team, and a starting population for anyone studying how long a superseded framework survives after its successor arrives.

A per domain lookup answers whether a particular site runs Zend today. The download answers the questions that only exist at population scale, which versions cluster together, what web server and hosting they sit on, what else those sites run alongside them, and whether the count is thinning or holding steady between refreshes. Sorting by version, filtering on the other columns in the export and then verifying a sample by hand is the work the file is built for. None of it is reachable by checking domains one at a time, and the sample is the part most people skip.