What actually built the page

A separate layer from delivery

The platform that answers a request and the software that produced the response are different things. A WordPress site can be served by Cloudflare, hosted by Kinsta and announced by Google's network, and every one of those statements can be true at once. These pages document the application layer only: what each system is, which public signals identify it, and what the detection cannot tell you.

What the evidence is

Application detection reads the final HTTPS response and the first bytes of its markup. That means response headers, cookie names, asset paths, hydration markers and the generator tag. One matching signal is reported as strong evidence; two or more independent signals are reported as confirmed. Nothing is inferred from one technology to another: a Next.js detection does not add React, and a Nuxt detection does not add Vue, unless their own markers appear.

Content management systems

Content management systemWordPress

Open source, WordPress Foundation

Content management systemDrupal

Open source, Drupal Association

Content management systemJoomla

Open source, Open Source Matters, Inc.

Content management systemGhost

Open source, Ghost Foundation

Content management systemCraft CMS

Pixel & Tonic, Inc.

Content management systemHubSpot

HubSpot, Inc.

Content management systemPayload

Payload CMS, Inc.

Content management systemStatamic

Wilderborn

Site builders and commerce platforms

Managed website platformSquarespace

Squarespace, Inc.

Managed website platformWebflow

Webflow, Inc.

Commerce platformMagento

Adobe Inc., and the open-source Magento project

Web application frameworks

Application frameworkNext.js

Open source, maintained by Vercel

Application frameworkNuxt

Open source, NuxtLabs

Application frameworkSvelteKit

Open source, Svelte project

Site frameworkAstro

Open source, the Astro Technology Company

Site frameworkGatsby

Open source, maintained under Netlify

Application frameworkLaravel

Open source, Laravel Holdings Inc.

Application frameworkDjango

Open source, Django Software Foundation

Application frameworkRuby on Rails

Open source, Rails Foundation

Application frameworkASP.NET

Microsoft Corporation

Application frameworkExpress

Open source, OpenJS Foundation

Browser frameworks and libraries

Frontend libraryReact

Open source, maintained by Meta

Frontend frameworkVue

Open source, the Vue project

Frontend frameworkAngular

Open source, maintained by Google

Frontend libraryjQuery

Open source, OpenJS Foundation

Languages and runtimes

Server languagePHP

Open source, the PHP Group

Application runtimeJava servlet container

Various, Jakarta EE standard

Python application serverGunicorn

Open source

Elixir application frameworkPhoenix

Open source

Application and frontend platforms

Frontend application platformCloudflare Pages

Cloudflare, Inc.

Additional signals without a page

These are detected and reported in results, but the public evidence for each is a single signal and does not need its own reference page.

• Statamic — Identified from an x-powered-by value naming Statamic. It is built on Laravel, so both can appear.
• Java servlet container — Identified from a JSESSIONID cookie, which names the servlet standard rather than any particular server or framework.
• Gunicorn — A Python application server named in the server header, most often running Django or Flask.
• Phoenix — Inferred from a server header naming Cowboy, the Erlang HTTP server that Phoenix runs on.
• webpack — Identified from bundle and runtime chunk filenames in the markup. It is build tooling, not a framework.
• Vite — Identified from /@vite/ paths in development output or hashed /assets/index-*.js filenames in a production build.
• jQuery — Identified from a versioned jQuery script filename. Its presence says nothing about the rest of the stack.
• Self-reported x-powered-by — Any x-powered-by value that matches no known signature is reported verbatim and labelled as self-reported rather than verified.
• meta generator — A generator tag that matches no detected technology is reported as declared by the page, not as confirmed evidence.

What none of this proves

A version number in a header or asset path is self-reported and can be stale, stripped or wrong. Absence of a signal is not absence of the technology: headers are commonly removed as a hardening measure, and several modern frameworks deliberately emit nothing. DNSTrace.dev reports what is publicly observable and labels the confidence rather than filling gaps with inference.

Run a lookup →Delivery platforms →Evidence model →