Explore CDNs, website security services, application hosts and commerce platforms: what they offer, how they work and how to recognize them.
Updated 8 September 2026Why these pages exist
When a lookup reports a delivery platform, it is reporting an observed layer, not the whole story. A CDN, a security proxy, an application host and the network that announces the address are separate things, and one company can occupy several of those layers at once. These guides explain each platform’s features, common uses and operating model before examining its public detection signals. They include practical examples, questions to consider and links to official documentation.
Content delivery networks
Cloudflare, Inc.
Cloud, delivery and securityAkamai Technologies, Inc.
Edge cloud and CDNFastly, Inc.
CDNAmazon Web Services, Inc.
Global load balancer and CDNMicrosoft Corporation
Cloud application edgeGoogle LLC
CDNBunnyWay d.o.o.
Cloud, AI and edge platformGcore Luxembourg S.A.
Security edges and website firewalls
Application and frontend platforms
Vercel, Inc.
Frontend application platformNetlify, Inc.
Application platformFly.io, Inc.
Application platformSalesforce, Inc.
Static hostingGitHub, Inc., a Microsoft subsidiary
Managed commerce and website platforms
Shopify Inc.
Managed website platformWix.com Ltd.
Managed web platformPantheon Systems, Inc.
Managed WordPress hostingKinsta Inc.
How detection works
Every identification comes from public evidence: proprietary response headers, CNAME targets, published address ranges and the autonomous system announcing the route. DNSTrace.dev keeps the DNS operator, the reverse proxy, the application platform and the network owner as separate layers, and reports an origin as unknown when a proxy conceals it. The full policy is described in the evidence model.
The layer above
A delivery platform answers the request. The content management system, framework or runtime that produced the response is a separate question, documented in the application stack reference.