Download websites that use WEBDEV

About WEBDEV

The name reads like a category rather than a product, which is the first thing to get wrong about it. Applications built with the PC SOFT toolchain leave build stamps in their generated output, which is why our records for it carry a version breakdown at all, and why the technology repays a kind of analysis that a hosted site builder never allows.

As of October 2026 we detect WEBDEV on 529 sites, spread across 55 distinct versions. A build such as 29.0.560.5 sits at the recent end of that spread, while stamps from long-superseded releases are still answering requests today. Spread of that width is normal for a licensed development product rather than a hosted service, because nothing forces an upgrade on anybody. An application compiled once for a client stays on the release it was built against until somebody is paid to move it, so the version string works as a rough proxy for when the project last had a budget behind it.

The product is not a site builder in the drag-a-block sense, and reading it as one leads to wrong conclusions about the sites in the list. Rather, it is the web half of a rapid application development suite that PC SOFT has sold since 1996, Proprietary throughout, built on the company's own language and its own visual environment. What gets deployed is a business application that happens to be reachable through a browser, which is why detected sites lean toward customer portals, member areas, booking and quotation systems and internal tools exposed to the outside, rather than toward marketing pages. Adoption has always concentrated in the French-speaking market, where the vendor's training, certification and integrator network are based, so the domain endings and countries in the file are worth checking before assuming a global spread.

One honest caveat belongs with the version data. A build stamp is emitted by the deployed runtime, not declared by the site owner, so it is good evidence of what is running and no evidence of what is licensed, patched behind a proxy or reverse-proxied from an older tier. Some deployments strip the markers entirely, which means the detected total is a floor.

The version column is what makes the list actionable. A security team assessing exposure across a portfolio needs to know which deployments sit on builds that predate a given fix, and needs it as a table rather than as a series of guesses. An integrator or a competing vendor reads the same column the other way, since a site still serving a stamp from several release cycles back belongs to an owner with no active development contract, and an owner like that is a maintenance or migration conversation waiting to happen. Neither reading survives a per-domain lookup, which describes one deployment on one day. A downloadable set of every detected site, with build stamp, country and domain ending attached, lets the question be asked across the whole installed base at once.