Next.js: Application framework

What Next.js is

Next.js is a React framework that renders on the server, prerenders at build time or streams from the edge depending on how each route is configured. It is maintained by Vercel but runs anywhere Node.js runs, including on other hosts and inside containers.

How DNSTrace.dev detects it

Detection reads the final HTTPS response and the first bytes of its markup. One matching signal is reported as strong evidence; two or more independent signals are reported as confirmed.

x-nextjs-cache — The outcome of the framework's own data and route cache.
x-nextjs-prerender — Set when the route was prerendered rather than rendered per request.
x-nextjs-matched-path — The route pattern the request matched.
x-nextjs-stale-time — Revalidation timing for an incrementally regenerated route.
x-powered-by naming Next.js — Emitted by default and often disabled in production.
/_next/static/ and __NEXT_DATA__ in markup — The fixed build output path and the serialised props block.

What a detection proves

The page was produced by Next.js.

What it does not prove

That the site is hosted on Vercel. Next.js runs on any Node.js host, and DNSTrace.dev reports the delivery platform as a separate layer.

Common questions

Does Next.js mean the site is on Vercel?

No. Vercel maintains Next.js but the framework is commonly self-hosted or run on other platforms. The delivery layer is detected independently.

Why do some Next.js sites show no framework headers?

The x-powered-by header is frequently disabled, and the cache headers only appear on routes that use those features. The /_next/static/ asset path usually remains.

Is React reported as well?

Next.js renders React, but DNSTrace.dev only reports React separately when React's own markup markers are present.