Technology Stack Detector

How it works

What we check

• CMS / site generator — Reads the page's generator meta tag and known markup fingerprints to identify the content management system or builder behind the site — for example WordPress, Shopify, Wix, Squarespace, Webflow, Drupal or Joomla. This is usually the single most telling fact about how a site is built.
• JavaScript frameworks & libraries — Looks for signatures of front-end frameworks and libraries such as React, Vue, Angular, Next.js, jQuery and Bootstrap. These reveal how interactive the front end is and how the site is likely rendered and maintained.
• Analytics & tag tools — Detects common measurement and tag-management signatures in the page, such as tag managers and analytics snippets. It tells you whether and roughly how a site is tracking its visitors and marketing.
• CDN & performance signals — Picks up signs that a content delivery network or edge layer is in front of the site. A CDN affects how fast and how reliably content is served and is a common part of a modern, scaled stack.
• Web server & powered-by — Reads the server response header and any x-powered-by header the site exposes, which can name the underlying web server or application platform. Many sites hide these, so a blank here simply means the server isn't advertising them.
• UI & utility libraries — Surfaces front-end utilities like CSS frameworks and icon sets (for example Tailwind, Bootstrap or icon libraries) that show up in the page source. These hint at the design system and developer tooling in use.

Common issues we catch

• A near-empty result on a big-name site — Some sites strip generator tags, hide server headers and bundle their code so signatures don't appear in plain HTML. A short result doesn't mean a simple site — it can mean the team deliberately removed the fingerprints this kind of check relies on.
• Detection reads the homepage, not the whole site — The check inspects the page you give it. A site can run different technology on its blog, store or app subdomains than on its homepage, so one URL is a snapshot of that page rather than a guaranteed map of the entire property.
• A revealing server or powered-by header — Servers that advertise their exact software and version in headers hand attackers a head start on known vulnerabilities. Finding a detailed powered-by or server header on your own site is a quiet security hygiene flag worth tidying up.
• Frameworks that render after load — Heavily client-rendered sites build much of their markup with JavaScript after the first response. Some signatures still appear in the initial HTML, but a check that reads the first response will naturally see less of a script-built page than a server-rendered one.
• Stale tools still loading on the page — Old analytics snippets, abandoned chat widgets and retired marketing pixels often stay in the page long after they're needed. Spotting them in the stack is a prompt to remove dead weight that's still costing requests on every visit.
• Shared fingerprints across platforms — Some signals — a common JavaScript library, a popular CSS framework — appear on sites built many different ways. They tell you a library is present, not that the whole site is built around it, so read individual entries rather than assuming one defines the architecture.
• A CDN masking the true origin — When an edge or CDN layer fronts a site, the headers you see can describe the edge rather than the origin server behind it. That's useful to know, but it means the server header may not reflect the actual application platform.

Where this matters

• WordPress, Drupal & Joomla — Traditional content management systems leave clear footprints in markup paths and generator tags. Identifying them tells you how content is managed and what plugin ecosystem and update cadence a site is likely working with.
• Shopify, Wix, Squarespace & Webflow — Hosted site builders and commerce platforms have distinctive asset domains and markup. Recognising them tells you a site is on a managed platform with that platform's constraints, themes and app marketplace.
• React, Vue, Angular & Next.js — Modern JavaScript frameworks signal a component-based, often app-like front end. Spotting them tells you how interactive a site is and how it's likely built, rendered and maintained by its development team.
• Analytics & tag managers — Measurement and tag-management snippets reveal how a site tracks visitors and deploys marketing tags. Their presence — or absence — is a quick read on how data-driven a site's marketing operation is.
• CDNs & edge layers — Edge and delivery layers in front of a site point to a performance- and scale-minded setup. They influence load speed and reliability and are a common ingredient in stacks built to handle real traffic.