Download websites that use Azure CDN

Content delivery is designed to be invisible, and a network doing its job well leaves nothing on the page announcing itself. Detection depends on accidents instead: an asset hostname still pointing at the provider's default domain, a header that survives to the client, a script reference nobody rewrote when the custom domain was finally set up.

Microsoft has offered Azure CDN since 2014 on Proprietary terms, sitting in front of storage buckets, hosted web apps and third-party origins. As of October 2026 we detect the service on 128 sites, and the figure is not an adoption estimate and should not be used as one. Sites that route the network behind their own domain, which is the configuration the vendor recommends, look like ordinary sites to a crawler, so the better a deployment is arranged the more likely it is to be missing here.

The places where evidence does survive share a profile. Default provider hostnames turn up on internal tools, documentation sites, media libraries, marketing microsites and applications built by teams who had no reason to dress the URLs up, so the visible population leans toward the functional end of a company's web estate rather than its flagship domain.

What a positive detection tells you is unusually specific, though. A site serving assets through this network almost always has more of its infrastructure in the same cloud, because a delivery network is rarely the first product a company buys from a hyperscaler and hardly ever the only one. Presence therefore reads as a vendor relationship rather than a technology choice, with procurement already behind it, an agreement in place and somebody internally accountable for the bill.

For a competing network or cloud vendor, a list built on that reading is a displacement target with the qualification already done. For a security researcher the interest runs the other way, toward origin exposure, subdomains pointing at storage endpoints that no longer exist and the takeover risks that follow. Both readings need a population rather than a single domain, and that is the gap a lookup tool cannot close.

We hold no version or geographic breakdown for Azure CDN, and for a managed edge service the absence is honest rather than a hole in the data. Customers do not run releases of a delivery network, and the edge locations serving a page have no fixed relationship to where the audience or the site owner is. Any country figure printed here would describe our crawl path more than the business behind the domain.