Download websites that use Extendify

About Extendify

Extendify raises a question most technology detections do not: who actually chose it. The product is a design assistant and pattern library for the WordPress block editor, and a large part of its distribution arrives through hosting companies that pre install it in new accounts. A site can therefore carry the signature because the owner installed it deliberately, or because it came with the hosting plan and was never removed.

Both readings are useful and they answer different questions. Taken as an owner choice, the plugin marks a site built by somebody assembling pages from templates rather than commissioning a design. Taken as a hosting artifact, the plugin fingerprints the onboarding stack of a particular provider, and the population turns into a map of which hosts ship which tooling to new customers. Cross referencing the list against server, nameserver and DNS evidence usually separates the two groups, and doing exactly that is a large part of what makes a bulk extract more useful than a spot check.

Age narrows things further. Extendify Inc. shipped the first release in 2021, which is recent by WordPress standards, so a detection works almost as a date stamp and the site, or at least its current build, is unlikely to predate it. As of September 2026 we find the plugin on 42,198 sites, with 12,433 in United States and the domain mix weighted toward .com. Compared with plugins that have been in the ecosystem far longer, the installed base is young and skews toward sites built in the block editor era rather than toward legacy installs carried forward through redesigns.

The licensing detail is easy to skip and worth keeping. A Proprietary license on a plugin distributed through a free ecosystem means the free tier is an acquisition channel and the revenue sits in paid plans and in bulk agreements with hosts. Detection cannot tell a free install from a paid one, so nobody should read the population as a customer list. What the population does support is the reverse exercise, which is sizing how far a vendor of this model has reached into the WordPress base and how that reach is distributed across countries, suffixes and hosting providers.

Version data is where the plugin earns its place in an audit. We record 74 distinct releases in the wild and 4.1.24 sits at the head of that distribution. A spread that wide on a young plugin is a maintenance signal in itself. Sites pinned to old releases are usually sites where automatic updates are off, where a staging process has stalled, or where the plugin came bundled and nobody is watching it. For anyone selling security, maintenance or managed hosting, the release column is the qualifying field, since the domain list identifies the market while the version spread identifies the part of it with a problem worth paying to fix.

The implementation is PHP running inside WordPress rather than as a separate hosted service, so detection depends on markers the plugin leaves in the rendered page and in asset paths. A site that strips those markers through aggressive optimization or a full page cache rewrite escapes the count, which means the figure is conservative by construction. Even so, the list answers what a per domain lookup cannot: not whether one site uses the plugin, but which hosting populations, which agencies and which vintages of WordPress build carry it, and where an offer aimed at them would actually land.