Home / Technologies / CDN & Hosting
Technology category
CDN & Hosting Providers
CDNs and hosting platforms leave asset-domain and header fingerprints (cloudfront.net, .vercel.app, cdn.jsdelivr.net) that indicate where a site is served from.
Content delivery networks distribute assets from servers near visitors, while hosting platforms serve application and website content. Their visible source signals often overlap: a single homepage can load images, scripts and fonts through several delivery services. Explore Cloudflare, Amazon CloudFront and jsDelivr to compare asset paths and domains associated with these services.
To find websites referencing a CDN, choose its technology page and run the documented query. A cloudfront.net asset URL identifies a different kind of evidence from a cdn.jsdelivr.net library reference. Open matching source and determine which resource uses that delivery domain. A third-party widget may introduce a CDN even when the website's main pages are hosted elsewhere. SearchWebCode examines stored homepage HTML; it does not infer the complete hosting setup from DNS or response headers.
Use these results to investigate asset delivery, integration dependencies or a particular distribution path. Avoid treating every asset-domain match as proof of the site's primary hosting provider. The frameworks category helps identify libraries loaded through public CDNs, and fonts and UI toolkits covers another common source of externally delivered assets. Review current requests separately when your question requires confirmation of an active delivery configuration.
- Websites using Akamaiakamaized.net
- Websites using Amazon CloudFrontcloudfront.net
- Websites using Cloudflare/cdn-cgi/
- Websites using Cloudinaryres.cloudinary.com
- Websites using Fastly.fastly.
- Websites using jsDelivrcdn.jsdelivr.net
- Websites using Netlify.netlify.app
- Websites using unpkgunpkg.com
- Websites using Vercel.vercel.app