Download websites that use Laravel

About Laravel

Server side frameworks are the hardest thing on a website to observe from outside. A browser receives HTML, and whatever produced that HTML has usually finished its work and closed the connection before anything reaches the network. Laravel is a case where the gap between what exists and what can be measured deserves stating before any figure is quoted.

Laravel is a PHP framework released in 2011 under the MIT licence, and it became the default choice for a large share of professional PHP work by bundling routing, authentication, queues, an object relational mapper and a deployment ecosystem into one opinionated package. Applications built on it look like ordinary web applications from the street. The evidence is indirect: a session cookie naming convention, particular header patterns, default error pages, asset build paths, and the fingerprints of tooling that usually ships alongside.

As of October 2026 we record the framework on 532,259 sites, with United States contributing 227,166 and .com leading the domain endings. The figures are a floor rather than a measurement. A carefully configured deployment can suppress every signal listed above, and teams that treat framework disclosure as an information leak do exactly that. What the observed set gives you is a large, honestly labelled sample of applications where the stack is still visible, which is enough for most commercial questions and not enough for a census.

The people who want the list are rarely curious about the framework itself. Recruiters and consultancies use it to find companies whose engineering is in house or contracted to a PHP shop. Vendors selling monitoring, managed hosting, security scanning and developer tooling use it to size an addressable market and to aim at the part of it that will understand the pitch without education. Security teams use it to bound the population touched by a framework level advisory, which is a question a single domain lookup cannot answer at all.

Framework presence also carries information about the age and habits of a codebase. A domain where the framework appears alongside a modern front end build is usually maintained by an active team. A domain where the only trace is an untouched default page tends to be abandoned or minimally supported. Because the downloadable dataset carries the surrounding signals for every domain, the framework works as a filter rather than as the whole answer, and the population can be narrowed down to the segment that actually matters to you.