Download websites that use Blazor

About Blazor

Most browser frameworks tell you what a development team preferred. Blazor tells you what an organization already owned.

Microsoft shipped Blazor in 2018 and released it under the MIT license. The pitch was narrow and effective: write your interface components in C#, the language the backend is already written in, and skip the JavaScript toolchain entirely. Two very different runtimes deliver on that pitch. One compiles a .NET runtime to WebAssembly and executes component code inside the browser. The other keeps components on the server and pushes interface updates down a persistent socket, leaving the client as little more than a rendering surface. From the outside the two look similar enough that a crawler cannot always separate them, and our records do not attempt to.

The reason a researcher should care is not the framework itself. Behind almost every Blazor page there is an ASP.NET Core application, a C# team, a Visual Studio and Azure subscription, and often SQL Server underneath. Nobody adopts Blazor to be fashionable. Adoption follows an existing commitment to the Microsoft platform, which is why the framework clusters in corporate portals, logistics and insurance dashboards, industrial suppliers, healthcare back offices and business to business product sites rather than in publishing or consumer retail.

As of October 2026 we detect Blazor on 4,106 sites. The figure is honest about what a crawler can reach and quiet about where the framework actually lives. Server-hosted applications sit behind logins, on app subdomains and inside intranets that no public crawl ever touches, while the marketing homepage of the same company is frequently a static template with no trace of .NET on it at all. The count is best read as a visible floor rather than as a population.

A per-domain lookup answers whether one company chose Blazor. A list answers questions a lookup cannot reach: how far the Microsoft web stack spread beyond the accounts a vendor already sells to, which sectors it settled in, how the Blazor population overlaps with older ASP.NET sites that are candidates for a rewrite, and whether the footprint is growing in the markets where you plan to hire or sell. Component vendors, observability and error tracking companies, contract development shops and technical recruiters all buy the same domain list and read it for different things.

In the dataset every Blazor domain arrives with the rest of the stack detected on the same host, so the framework can be crossed against web server, CDN, analytics, payment and tag manager signals in one pass. A single site running the framework is rarely interesting on its own. The population, filtered down to the hosts that also run a competitor's product, is a working prospect list, and the same file read a quarter later shows which direction the footprint is moving.