dnstrace.devRun lookup →

Managed WordPress hosting

Kinsta

Kinsta Inc. · Managed WordPress hosting. How DNSTrace.dev identifies it from public evidence.

Updated Sep 2026

What Kinsta is

Kinsta is managed WordPress hosting built on Google Cloud, with its own caching layer in front of each site and Cloudflare providing the delivery edge. Because the underlying infrastructure belongs to other companies, Kinsta is identified from its own application cache header rather than from the network announcing the address.

How DNSTrace.dev detects it

Detection correlates independent public signals. A single match is reported as strong evidence; agreement between a response header and the announcing network is reported as confirmed.

  • x-kinsta-cache — The cache outcome from Kinsta's page cache, and the primary identifying signal.
  • cf-ray alongside x-kinsta-cache — Kinsta fronts sites with Cloudflare, so both layers commonly appear together and are reported separately.
  • AS15169 — The Google autonomous system underneath Kinsta's compute, which cannot identify Kinsta on its own.

What a detection proves

The response was served by a Kinsta-hosted WordPress site and passed through Kinsta's page cache.

What it does not prove

Anything about the network owner, which is Google or Cloudflare rather than Kinsta, or which WordPress theme and plugins the site runs.

Common questions

Why does a Kinsta site report Cloudflare too?

Kinsta uses Cloudflare as its delivery edge. Both detections are correct: Cloudflare is the reverse proxy, Kinsta is the host behind it.

Is Kinsta detectable without the cache header?

Often not. If the cache header is suppressed, the visible layers are Cloudflare and Google, and DNSTrace.dev will not infer Kinsta from those alone.

Compare with

Managed web platformPantheon

Pantheon Systems, Inc.

Content management systemWordPress

Open source, WordPress Foundation

Website firewall and CDNSucuri

Sucuri, a GoDaddy brand

CDN, reverse proxy and WAFCloudflare

Cloudflare, Inc.

Check a domain

Run a full lookup to see the delivery layer, the detected application stack, live TLS and the announcing network side by side.

Check response headers Identify the announcing network

Run a lookup →Platforms →Evidence model →