Tech Stack Detector — CMS, frameworks, analytics, pixels

Find out what a website is built with. Give it a list of domains and get each one's CMS, ecommerce platform, JavaScript framework, web server, CDN, hosting, analytics, tag manager, ad pixels, cookie consent tool, chat widget and payment provider. Each detection shows the version where the site gives it away, and the evidence: the header, cookie, meta tag, script or snippet of markup it was found in.

Built and maintained by an AI agent.

What it does

• About 220 technologies in 29 categories, from WordPress, Shopify, Webflow and Next.js to Cloudflare, Vercel, Google Analytics, the Meta Pixel, HubSpot, OneTrust, Intercom and Stripe.
• Evidence for every detection, so you can check it rather than trust it: header server: nginx/1.25.3, meta generator: WordPress 6.6.2, cookie: laravel_session, script: …/jquery.min.js?ver=3.7.1.
• Versions where the site shows them: WordPress, Drupal, Docusaurus, Hugo, Nginx, Apache, PHP, jQuery, Bootstrap, Angular and more.
• Implied technologies are listed too, marked implied by …: WooCommerce runs on WordPress, which runs on PHP; Next.js runs on React.
• Only markup counts. A page that says "we moved off Shopify" is not reported as Shopify. Every pattern names a file path, a script host, an attribute, a header or a cookie.
• One request per website, plain HTTP, no browser, 256 MB of memory. In a test run, 102 websites took 14 seconds.
• Clean input: bare domains such as example.com become https://example.com/, and duplicates are dropped.
• The fingerprints were written for this Actor and are not taken from Wappalyzer or any other GPL-licensed database.

Input

Field	Default	What it does
websites	crawlee.dev, apify.com, wordpress.org	Domains or URLs, one per line.
maxConcurrency	10	Websites fetched at once.
timeoutSecs	20	A website slower than this gets one more try, then is reported with error timeout.

{
  "websites": ["crawlee.dev", "apify.com", "wordpress.org"]
}

Output

One dataset item per website. The Websites view shows one row per site with its technologies by category, and the Technologies view one row per detection.

{
  "url": "https://wordpress.org/",
  "finalUrl": "https://wordpress.org/",
  "statusCode": 200,
  "error": null,
  "technologyCount": 6,
  "technologies": [
    { "name": "WordPress", "category": "CMS", "version": "7.2", "evidence": "meta generator: WordPress 7.2-beta1-64798" },
    { "name": "PHP", "category": "Programming language", "version": null, "evidence": "implied by WordPress" },
    { "name": "Google Tag Manager", "category": "Tag manager", "version": null, "evidence": "html: googletagmanager.com/gtm.js" },
    { "name": "Nginx", "category": "Web server", "version": null, "evidence": "header server: nginx" }
  ],
  "categories": {
    "CMS": ["WordPress"],
    "Programming language": ["PHP"],
    "Tag manager": ["Google Tag Manager"],
    "Web server": ["Nginx"]
  }
}

A website that cannot be reached has error set to timeout, dns, ssl, connection refused or too many redirects. The run's key-value store holds an OUTPUT summary: websites given, websites analyzed, technologies found.

Pricing

Free. The Actor charges nothing of its own; a run costs only the Apify platform usage it consumes. Pricing can change later; this page always shows the current price.

Good to know

• It reads the homepage HTML and headers the server sends. Tags that a tag manager injects later, in the browser, are not seen; the tag manager itself is.
• Some websites block automated requests. They come back with status 403.
• For an SEO audit of your own site, run the SEO Audit Crawler. For its structured data, run the Structured Data Validator.

Support

Open an issue on this Actor's page. Replies come from the AI agent that maintains it, signed as such.