Download websites that use ExtJS

About ExtJS

Paying for a JavaScript framework is a choice most of the web stopped making. ExtJS still asks for it, and the sites that carry it are saying something about the kind of software they are. As of October 2026 we detect the framework on 866 sites.

The framework dates from 2007 and is sold by Sencha under a Commercial licence, and everything else follows from the licence. The library is a component toolkit rather than a rendering layer, offering grids that survive very large result sets, tree views, form engines, charting and layout managers, assembled into applications that behave more like desktop software than like pages. Organisations that buy a toolkit of that sort are building internal tools, administrative consoles, trading and logistics screens, government and utility portals. The code is JavaScript like its free competitors, but a purchase order exists behind each deployment, which is a fact about the organisation and not only about the page.

Public detection of an enterprise framework has an obvious blind spot. Applications built with it usually sit behind a login, on an intranet, or on a hostname nobody links to, so what a crawl reaches is the portion of the estate exposed to the open web, meaning customer portals, dealer and partner logins, public service applications and the marketing pages of firms that reuse the same bundle. Whatever the count says, the installed base behind it is larger and not observable from outside. We also do not resolve release versions for this framework, so presence is the extent of what the data supports for a given deployment.

The population still answers questions a single lookup cannot. Vendors of modern front end frameworks and of low code platforms treat a licensed legacy toolkit as a modernisation pipeline, and a pipeline is sized by counting organisations, not by checking one domain. Consultancies staffing migration work want to know where the skills are still in demand and in which countries. Diligence teams want to know whether a target company's public applications rest on a commercially licensed dependency, because a licence is a recurring cost and a renewal risk. Security teams want an inventory of long lived front end dependencies, and applications that are rarely rebuilt qualify twice over. Grouped by country and by top level domain, the list shows where a paid framework of this generation is still carrying production work, which is not something any one domain can tell you.