Account

What new tool do you want?

Web & SEO

Website Technology Checker (Tech Stack)

Find out what a website is built with — CMS, e-commerce platform, JavaScript framework, CDN, hosting, analytics, payments and more.

How to use

  1. 1Enter a website.
  2. 2See the detected technologies grouped by category.

Frequently asked questions

How does detection work?

By matching the page's HTML, scripts, cookies and response headers against signatures of about 60 popular technologies.

Why is something missing?

Tools loaded only after JavaScript runs, server-side code and custom-built stacks can't always be seen from the outside.

Is this accurate?

Signatures are specific (e.g. /wp-content/ for WordPress, cf-ray for Cloudflare), so false positives are rare.

Why specific fingerprints beat guessing from general appearance

Detecting WordPress by looking for a generic 'blog-like' page structure would produce constant false positives against every other CMS with a similar layout — this tool instead looks for concrete, hard-to-fake signatures like a /wp-content/ path appearing in the HTML, or a cf-ray response header that only Cloudflare's infrastructure sets. Matching against roughly 60 specific signatures rather than general heuristics is exactly why the FAQ states false positives are rare: a site either has /wp-content/ in its markup or it doesn't, there's little ambiguity in that kind of check.

Worked example: Website Technology Checker

Checking an e-commerce site might surface Shopify as the platform (detected via Shopify's characteristic CDN paths and checkout URLs), Google Analytics and Meta Pixel under analytics, Cloudflare as the CDN (from the cf-ray header), and Stripe under payments (from script sources loading from Stripe's domain) — all pulled from markup, headers and cookies that are visible to any outside visitor, not from anything requiring access the site owner hasn't already made public by serving the page at all.

Why some technologies never show up no matter how thorough the signature list

Detection only works on what's visible in markup, response headers, cookies and loaded scripts — it has no way to see the actual backend language, database, or server-side framework processing requests behind the scenes, and tools that only load conditionally after specific user interactions or behind a feature flag may simply never fire during a single automated page load. A custom-built internal stack with no recognizable third-party service signatures at all would show up here as largely empty, which reflects the detector's visibility limits, not necessarily a lack of technology.

Three different clues, three different categories of technology

The roughly 60 signatures split across detection channels that each tend to reveal a different layer of a site's stack. A CMS like WordPress or a framework like Next.js usually leaves a trace directly in the HTML — a generator meta tag, a telltale script path, or a distinctive class naming convention baked into the rendered markup. CDNs and hosting providers are caught almost entirely through response headers, since infrastructure like Cloudflare, Vercel or Fastly stamps identifying headers (cf-ray, x-vercel-id) onto every response regardless of what the site itself is built with. Analytics and advertising tools are most reliably caught through cookies and the specific script domains they load from, since a Google Analytics or Meta Pixel snippet looks almost identical in markup across millions of unrelated sites but sets a recognizable cookie name. Reading all three channels together is why the tool can often identify not just that a site runs WordPress, but which CDN sits in front of it and which analytics platform it reports to, as separate findings rather than one guess.

Related tools

More: Web & SEO