Tech Stack Detector: Website Technology Lookup in Bulk

Tech Stack Detector finds out what a website is built with. Give it a list of domains or URLs and get back, for each site, the CMS, ecommerce platform, JavaScript frameworks, analytics and marketing tools, CDN, web server, hosting and email provider it uses. Each detection comes with a version where one is visible, a confidence score and the evidence behind it.

• ~3,600 technology fingerprints in 100+ categories.
• $0.01 per website analyzed. Sites that fail aren't charged: DNS errors, timeouts, HTTP errors, bot walls and robots.txt blocks are all free.
• Evidence for every result, e.g. meta generator = WordPress 6.4.2 or MX = aspmx.l.google.com, so you can check it.
• Clean JSON for agents and pipelines. One item per site, a flat technologyNames list for spreadsheets, and a categories map for quick filtering.

How to look up a website's tech stack

1. Paste domains or URLs into URLs, one per line. Thousands per run are fine.
2. Optional: pick categories with Only these categories (e.g. CMS, Ecommerce) or raise Min confidence.
3. Click Start. Download the table as CSV/Excel, or call the Actor from the API, Make, Zapier or an AI agent (MCP).

Use cases

• Lead lists and sales prospecting: find Shopify stores, WordPress sites, HubSpot users or Google Workspace companies in a list of domains.
• Competitive and market research: see what your competitors run, from analytics to payments.
• AI agents (MCP): answer "what CMS does example.com use?" in one cheap call.
• Security and IT inventory: you get CPE identifiers for known software and visible versions (e.g. an old jQuery).

Input

Field	What it does	Default
urls	Domains or URLs. A bare domain gets its homepage fetched over HTTPS, falling back to HTTP.	required
minConfidence	Hide detections below this confidence (0–100).	50
onlyCategories	Return only these categories, e.g. CMS, Ecommerce, Analytics.	all
includeEvidence	Include the matched signal for each detection.	true
checkDns	Look up MX/TXT/NS/SOA/CNAME records to find email, DNS and verified SaaS providers.	true
respectRobotsTxt	Skip pages that robots.txt disallows (skipped sites aren't charged).	true
maxConcurrency	Sites analyzed in parallel (1–20). The same host is never hit more than once a second.	5
timeoutSecs	Per-site timeout.	20

{ "urls": ["https://www.python.org", "apify.com", "example.com"], "onlyCategories": [], "minConfidence": 50 }

Output example (one item per site; real output for python.org, shortened)

{
  "input": "https://www.python.org",
  "finalUrl": "https://www.python.org/",
  "domain": "python.org",
  "status": "ok",
  "httpStatus": 200,
  "title": "Welcome to Python.org",
  "techCount": 13,
  "technologyNames": ["Nginx", "Varnish", "jQuery", "Modernizr", "Mailgun", "..."],
  "categories": { "Web servers": ["Nginx"], "Caching": ["Varnish"], "JavaScript libraries": ["jQuery", "jQuery UI", "Modernizr"] },
  "technologies": [
    {
      "name": "jQuery", "version": "1.8.2", "confidence": 100,
      "categories": ["JavaScript libraries"], "groups": ["Web development"],
      "website": "https://jquery.com", "cpe": "cpe:2.3:a:jquery:jquery:*:*:*:*:*:*:*:*",
      "saas": null, "oss": null, "pricing": [],
      "evidence": [{ "type": "scriptSrc", "match": "jquery" }, { "type": "scriptSrc", "match": "/1.8.2/jquery.m" }]
    }
  ],
  "dnsChecked": true,
  "error": null,
  "checkedAt": "2026-10-03T12:00:00+00:00"
}

status is ok (analyzed and charged), failed or blocked (both free). The Overview dataset view shows one row per site.

How it works

For each site the Actor makes one page request, plus a robots.txt request and DNS lookups. It then checks the response headers, cookies, HTML, script URLs, inline scripts and styles, meta tags, DOM selectors, visible text and DNS records against the fingerprint database. Implied technologies are added too: WordPress implies PHP and MySQL. Plugins whose platform wasn't found are dropped. Confidence is the sum of the matched signal weights, capped at 100.

Limits (please read)

• No JavaScript rendering. About 380 fingerprints can only be seen in a live browser (JavaScript variables, XHR calls), so they are never detected here. Single-page apps that render everything client-side will show fewer technologies than a browser extension would. In exchange, the Actor is fast and cheap.
• One page per site. Tools that only load on checkout, blog or login pages won't be seen unless you pass that URL.
• Fingerprint data is a January 2023 snapshot. It's the last openly licensed (MIT) release of the community fingerprint set, so very new products, or ones that have changed their markup since, may be missed. We add and fix fingerprints over time.
• DNS TXT verification records (e.g. stripe-verification=) show a service was connected to the domain at some point, not that it's in active use. Their evidence is labelled dns.
• Bot protection: sites behind challenge pages or rate limits answer with 403/429/503. Those sites come back failed and aren't charged. No proxies or evasion are used.
• Detection is heuristic. Treat low-confidence results (25–50) as hints.

Responsible use

• Only public pages are requested, with an identifying user agent (TechStackBot).
• robots.txt is honored by default, and requests to the same host are spaced at least 1 second apart.
• Private and internal network addresses are refused.
• No personal data is collected. Output describes software, not people.

Pricing

Pay per event: $0.01 per website analyzed (site-analyzed). Failed and blocked sites are free. Your run stops cleanly when it reaches your maximum total charge.

Attribution

Fingerprint data comes from the Wappalyzer project, as of git commit aff18ef (2023-01-25), the last version released under the MIT licence. See src/data/LICENSE-fingerprints.txt. The data was merged and reformatted, and no icons were copied. The detection engine is our own code. This Actor is not affiliated with or endorsed by Wappalyzer.

FAQ

What technologies can it detect?

About 3,600, in 100+ categories: CMS (WordPress, Drupal, Wix, Squarespace), ecommerce (Shopify, WooCommerce, Magento, BigCommerce), JavaScript frameworks and libraries, analytics and tag managers, advertising pixels, CDNs, web servers, hosting, payment providers, live chat, and email providers from DNS records.

How does it compare with BuiltWith or Wappalyzer?

It uses the same open fingerprinting approach as the Wappalyzer browser extension, from that project's last MIT-licensed data release (see Attribution). It makes one live page request per site, with no historical data and no JavaScript rendering. BuiltWith's database also includes historical and spend data that this Actor doesn't have. In exchange you pay $0.01 per site with no subscription. This Actor isn't affiliated with either company.

Can I find all Shopify (or WordPress) sites in my list?

Yes. Set onlyCategories to ["Ecommerce"] or ["CMS"] and filter the technologyNames column.

Related Actors

• Bulk WHOIS Domain Lookup with DNS, SSL & Security Headers: domain age, registrar, email provider and SSL for the same list.
• PageSpeed Insights Bulk Checker: Core Web Vitals and Lighthouse scores.
• Sitemap URL Extractor: every URL of a website.

Support

Open an issue on the Actor page with the site URL and what you expected to see. False positives and missed technologies get fixed.