Why 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 pages record what each platform is, which public signals identify it, and where the evidence stops.
Content delivery networks
Cloudflare, Inc.
CDN and edge platformAkamaiAkamai Technologies, Inc.
Edge cloud and CDNFastlyFastly, Inc.
CDNAmazon CloudFrontAmazon Web Services, Inc.
Global load balancer and CDNAzure Front DoorMicrosoft Corporation
Cloud application edgeGoogle Front EndGoogle LLC
CDNBunny CDNBunnyWay d.o.o.
CDN and edge cloudGcoreGcore Luxembourg S.A.
Security edges and website firewalls
Application and frontend platforms
Vercel, Inc.
Frontend application platformNetlifyNetlify, Inc.
Application platformFly.ioFly.io, Inc.
Application platformHerokuSalesforce, Inc.
Static hostingGitHub PagesGitHub, Inc., a Microsoft subsidiary
Managed commerce and website platforms
Shopify Inc.
Managed website platformWixWix.com Ltd.
Managed web platformPantheonPantheon Systems, Inc.
Managed WordPress hostingKinstaKinsta 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.