Download websites that use DHL

About DHL

A shipping label is not a web technology, and yet DHL leaves marks on a storefront that a crawler can read. The marks record a decision about what happens after the customer clicks buy rather than a decision about how the page is built, which makes this a different kind of signal and useful to a different kind of researcher.

A carrier integration is never decorative. When a tracking widget, a rate calculator or a branded parcel status page shows up in a site's markup, somebody at that company has already opened a shipping account, mapped a warehouse to a fulfilment workflow and decided that shipping cost is worth quoting at checkout instead of hiding it until the invoice. The code is downstream of a commercial relationship, and the commercial relationship is usually what a researcher actually wants to find.

Our category placement says the rest. We file the integration under Shipping carriers, and the population behaves accordingly: online shops, manufacturers selling direct, spare part catalogues, wholesalers running a customer portal. Very few of them are large enough to appear in any published retail listing, which is precisely why a full crawl is the only practical way to enumerate them.

Geography sharpens the picture. Germany accounts for 14,789 of the sites we observe with the integration, well out of proportion to that country's share of the web overall, and the concentration reflects a home market where the carrier is the default rather than one option among several. The .com zone still leads the domain split, because an exporter selling across borders tends to register generically even when its logistics stay local.

Different readers want different slices of the same population. A competing carrier sees a map of accounts already committed elsewhere. A logistics software vendor sees a filtered universe of companies that ship physical goods and have already survived one integration project, which is the qualification step that is hardest to do by hand. An analyst watching the population change over time sees carrier switching in aggregate, which no carrier publishes about itself.

A per domain lookup answers whether one shop uses the integration. The question worth paying for runs the other way. Which shops in a country, a TLD or a product niche use it, and what else sits on those same sites. Inverting the question needs the whole population in a file you can filter locally, not an endpoint you query one hostname at a time.

Be careful about the edges of what this means. DHL operates through many national subsidiaries and product brands, and our detection keys on web assets and public endpoints rather than on the contract behind them, so a freight customer with no customer facing tracking will not appear anywhere in the data. The components are Proprietary and are distributed for use with an account, which makes their presence a firmer commercial signal than an open source library anyone can paste in, but what we publish is still the visible integration layer rather than the carrier's client list. The two are not the same size, and the gap runs in one direction only.