Download websites that use Hostinger CDN

About Hostinger CDN

Hostinger CDN is a feature of a hosting plan rather than a product a site went out and bought. Turning it on takes a single switch in the provider's control panel, it costs nothing extra on the plans that include it, and the edge servers behind it are the provider's own.

Bundling of that kind shapes what the count can support, so it belongs at the front rather than in a footnote. A site carrying the feature has not made a delivery network decision in any meaningful sense. What the site did was buy hosting from Hostinger International and leave the defaults alone. The column therefore behaves like a hosting signal wearing performance clothing, and a researcher treating it as evidence of deliberate delivery strategy will claim more than the data can carry.

As of October 2026 we see 4,933,236 sites behind it, 2,497,918 of them in Germany, with .com heavily represented across the domains. A German weighting inside a global budget hosting brand says less about German customers than about where European edge capacity and infrastructure terminate. Geography in CDN rows generally describes the network rather than the customer, and the warning applies here more than most.

No first release year appears in our record for the feature, and inventing one would be worse than leaving the field empty. Bundled hosting features tend to arrive quietly, without an announcement, sometimes as a rebranding of something that had been running under another name for a while. Where a date cannot be verified, the dataset leaves it blank rather than reconstructing it from a marketing page.

Detection needs more care here than for a standalone network. The edge layer sits in front of sites the same company already hosts, so a response can look much the same whether the feature is switched on or not, and separating the delivery layer from the hosting beneath it is the whole of the difficulty. We record the feature where signals specific to it are present, and sites merely hosted by the provider are not folded in. Keeping the boundary strict costs coverage, because deployments that leave no distinctive trace fall out, but the alternative would be a column that quietly counts a different product.

Two audiences get value from the population. Hosting competitors read it as a customer roster with the plan tier partly visible, since the feature is bundled at particular price points and a customer who enabled it is a customer engaged enough to open the panel at all. Performance vendors and agencies read it from the other side, as sites that have already accepted the idea of an edge layer while sitting on a platform whose ceiling a serious storefront or media property will eventually reach.

The reason to take the file rather than probe hostnames one by one is that every worthwhile question here is comparative. How the budget hosting segment splits across delivery networks. Which national markets a provider has actually won as opposed to advertised in. Whether sites on a bundled network differ in platform mix or in domain age from sites on a purchased one, and whether that gap is closing. Each of those is a question about the whole population at once, and the download supplies it with country, suffix and the rest of the detected stack attached to every row.