How to Tell If a Website Uses KeyCDN

KeyCDN is an affordable, developer-friendly pull-zone CDN that caches and delivers a site's static assets from the edge to speed up load times. Detecting it means looking in two places: the host assets load from (a *.kxcdn.com pull zone or a custom CNAME) and the response headers (notably Server: keycdn-engine). This guide covers every reliable signal, how pull zones work, the look-alikes to rule out, and what KeyCDN usage tells you about the site.

What is KeyCDN?

KeyCDN, founded in 2012, is a content-delivery network aimed at developers and cost-conscious site owners. It uses a pull-zone model: you point a zone at your origin (your website), and KeyCDN automatically fetches ("pulls") your static assets — images, CSS, JavaScript, fonts — the first time they are requested, caches them across its global edge network, and serves them quickly thereafter. It is known for transparent, usage-based pricing, real-time analytics and a straightforward setup, which makes it popular with small-to-mid-sized businesses, individual developers and performance-minded site owners who want CDN benefits without enterprise contracts.

For detection, the key context is that KeyCDN is part of the site's hosting-and-performance setup — it delivers the site's own static assets, unlike public library CDNs (jsDelivr, unpkg) that deliver third-party open-source packages. So finding KeyCDN tells you the site has deliberately offloaded asset delivery to an affordable CDN, a sign of performance awareness on a budget. Because sites usually serve KeyCDN assets from a custom subdomain, the most reliable confirmation often comes from response headers rather than the host alone.

How KeyCDN delivers assets

A KeyCDN pull zone is exposed by default on a *.kxcdn.com subdomain — something like zonename-1234.kxcdn.com. In production, most sites configure a custom CNAME such as cdn.brand.com or static.brand.com pointing at that zone, so static assets load from the brand domain while KeyCDN serves them behind the scenes. Either way, the assets are KeyCDN-served, and the response headers reveal it: KeyCDN typically returns Server: keycdn-engine, along with caching and edge headers such as X-Edge-Location (the edge node that served the request), X-Cache (hit/miss status) and standard Cache-Control/Age headers.

Because the pull-zone model caches the site's own files, you will see the site's images, stylesheets and scripts loading from the KeyCDN host or CNAME, not third-party libraries. The combination of the host (kxcdn.com or a CNAME) and the keycdn-engine server header is what confirms KeyCDN — and the header is especially important when a custom domain hides the kxcdn.com host. Knowing this pull-zone-plus-headers model makes detection reliable.

How to tell if a website uses KeyCDN

Confirm at least one strong signal (the host or the server header).

1. Check the Network tab for the host. Look at where static assets (images, CSS, JS) load from. A *.kxcdn.com host is a direct KeyCDN signal.

2. Inspect response headers. Click a static asset in the Network tab and read its response headers. Server: keycdn-engine is the definitive header signal, even behind a custom CNAME; X-Edge-Location and X-Cache corroborate.

3. View the page source. Search the HTML for kxcdn.com or the site's CDN subdomain in src/href attributes.

4. Read the zone name. The zone subdomain in zonename-1234.kxcdn.com identifies the KeyCDN configuration.

5. Confirm a custom CNAME. If assets load from cdn.brand.com, a Server: keycdn-engine header on those responses confirms KeyCDN behind the brand domain.

What the KeyCDN signals look like

GET https://acme-1234.kxcdn.com/assets/app.css      (default pull-zone host)
GET https://cdn.acme.com/assets/app.css             (custom CNAME)
Response headers:
  Server: keycdn-engine
  X-Edge-Location: us-ny
  X-Cache: HIT

A *.kxcdn.com host or a Server: keycdn-engine response header is conclusive, the latter even behind a custom CNAME.

KeyCDN versus other CDNs — avoiding false positives

Match the host and header to keep CDNs distinct. KeyCDN uses kxcdn.com and Server: keycdn-engine; Cloudflare uses Server: cloudflare and a cf-ray header; Fastly uses x-served-by/Via: ... varnish and Fastly headers; Amazon CloudFront uses x-amz-cf-id and Via: ... cloudfront; BunnyCDN uses *.b-cdn.net and a Server: BunnyCDN header; StackPath/MaxCDN has its own markers. Each leaves distinct host and header fingerprints. The key is to read the response headers of static assets, since custom CNAMEs hide the underlying CDN host across all of these providers. Do not confuse KeyCDN (a pull-zone CDN for the site's own assets) with public library CDNs (jsDelivr, unpkg) that deliver third-party packages.

How reliable is each KeyCDN signal?

A *.kxcdn.com host is definitive, as is a Server: keycdn-engine response header — and the header is the more robust signal because it survives custom CNAMEs. The X-Edge-Location and X-Cache headers are strong corroboration. The zone name reliably identifies the configuration. The weakest situation is a site whose CDN host is fully custom and whose headers a proxy has stripped or normalised — uncommon, but there you may need deeper inspection. As a rule, read the static-asset response headers first; the keycdn-engine server header settles it regardless of the host.

What KeyCDN usage reveals about a site

Finding KeyCDN signals a cost-conscious, performance-aware site that has deliberately offloaded static-asset delivery to an affordable CDN. Its transparent, usage-based pricing and developer-friendly setup mean its users skew toward small-to-mid-sized businesses, individual developers, agencies and performance-minded owners — people who wanted CDN benefits without an enterprise contract or the all-in-one bundling of a platform like Cloudflare. The cache headers in evidence (high X-Cache: HIT rates) indicate an effective configuration. If you sell performance, hosting or web-optimisation services, a KeyCDN site marks an owner who already values speed and is comfortable configuring infrastructure, which is useful qualification. The choice of a focused, affordable CDN over a bundled platform also hints at a pragmatic, hands-on technical approach.

What finding KeyCDN means for sales, agencies and competitive research

For sales and prospecting, KeyCDN marks a performance-aware, cost-conscious site owner — a fit for performance tooling, hosting, and web-optimisation services aimed at SMBs and developers who make deliberate infrastructure choices.

For agencies and consultants, finding KeyCDN tells you the client already runs a CDN, so performance conversations can move beyond "you need a CDN" to optimising cache configuration, asset strategy and Core Web Vitals. It signals a client comfortable with infrastructure.

For competitive and market research, the CDN a competitor uses (read from headers) reveals part of their performance and cost strategy. Spotting KeyCDN versus an enterprise CDN tells you roughly their scale and budget approach, useful when benchmarking performance and infrastructure maturity.

KeyCDN in the wider stack

KeyCDN sits within a site's hosting-and-performance layer. It typically fronts a conventional origin server or hosting account, delivering static assets while the origin handles dynamic requests. You may find it alongside a caching plugin (on WordPress), an image-optimisation step, and standard analytics. Unlike all-in-one platforms that bundle CDN, security and DNS, KeyCDN is a focused CDN, so the rest of the stack (DNS, security, origin hosting) is handled separately and worth mapping. For an auditor, the valuable details are the zone or CNAME, the cache hit rate from X-Cache headers, the edge location, and the origin hosting behind it; together these reveal a deliberate, budget-aware performance setup with KeyCDN as the delivery layer.

A quick KeyCDN confirmation walkthrough

Open the site with developer tools on the Network panel and reload, then click a static asset (a CSS file, image or script) and open its Headers. Look at the request host — a *.kxcdn.com domain is a direct signal — and read the response headers for Server: keycdn-engine, X-Edge-Location and X-Cache. If assets load from a custom domain like cdn.brand.com, the keycdn-engine server header confirms KeyCDN behind it. View the source for the CDN subdomain in src/href attributes. The kxcdn.com host or the keycdn-engine header is enough to confirm KeyCDN.

A quick KeyCDN detection checklist

• Check static-asset hosts for a *.kxcdn.com pull-zone domain.
• Inspect response headers for Server: keycdn-engine — conclusive even behind a CNAME.
• Note X-Edge-Location and X-Cache headers as corroboration.
• Read the zone name from the kxcdn.com subdomain.
• Confirm a custom CNAME via the keycdn-engine header.
• Distinguish KeyCDN (site's own assets) from public library CDNs (jsDelivr, unpkg).

Detecting KeyCDN at scale

Checking one site is quick, but mapping CDN usage across many domains — to understand performance and infrastructure choices in a market — calls for automation. StackOptic detects KeyCDN and thousands of other technologies from a real browser, reading response headers to identify CDNs even behind custom domains. For related reading, see our guide to telling if a website uses Cloudflare or another CDN and the full KeyCDN technology profile.