Download websites that use Divi

About Divi

The number worth reading first on this page is not how many sites run the product. As of September 2026 we see 1,218 distinct version strings in the wild, which is a remarkable spread for a single commercial product and says more about how the ecosystem behaves than any headline count could. Software distributed by subscription updates when the licence holder updates it, and on sites that were built once and handed over, nobody is holding that licence any more.

Version sprawl of that kind has a specific cause. Elegant Themes sells the theme and builder as part of a membership, and the update channel is tied to an active key. When an agency builds a client site, keeps the key on its own account and later ends the engagement, the site keeps working and stops receiving updates on the same day. The pattern repeats across thousands of handovers, and the visible result is a long tail of installations frozen at whatever release was current when the relationship ended. The version we log most often is 4.27.4, but the interesting rows are the ones far behind it.

For a security or risk team, that tail is the entire point of the dataset. A Page builders layer that renders the front end of a site carries a large amount of code, and outdated builder installations are a recurring source of exposure precisely because the owner has no reason to notice. Knowing which sites run an old release, and being able to filter to them by country, suffix or hosting provider, converts a general concern into a workable list. A per-domain lookup cannot do that, because it presumes you already suspected the domain.

For a commercial team the same tail reads as demand. A stale installation is a site whose original builder has moved on, which makes it a candidate for maintenance retainers, redesigns, migration offers or managed hosting. Sites that have kept current are a different segment, better suited to plugin vendors, integration sellers and anyone whose product depends on the platform being maintained. One file supports both segmentations, since the version column is what separates them.

Some caution about the numbers is warranted. Version detection depends on what the delivered page exposes, in asset paths, query strings and generated markup, and those can be stripped, rewritten or cached by optimisation plugins and delivery networks. Sites where the version is unreadable are still counted as installations but contribute nothing to the version breakdown, so treat the fragmentation picture as indicative of shape rather than exact in proportion. The direction of the bias is that heavily optimised sites, which skew newer and better maintained, are the likeliest to be missing from the version columns.

Everything else about the footprint follows from the same commercial model, in place since 2013 under a Proprietary licence. As of September 2026 we detect it on 1,261,125 sites, with United States accounting for 466,509 and .com the suffix we record most often, a distribution that tracks where subscription priced design tools sell rather than anything about the technology itself. The export is worth having because it turns a product with a very large install base into a set of addressable populations, split by how well maintained each site actually is, which is a question no single domain check will ever answer for you.