Tech Stack Detector - Wappalyzer & BuiltWith Alternative

Find out what any website is built with. Paste a list of domains and get, for each one, the CMS, ecommerce platform, analytics and marketing tools, payment providers, CDN, frameworks and hosting — plus the SaaS products the company itself uses, read from its public DNS records.

A fast, affordable alternative to Wappalyzer and BuiltWith lookups for lead qualification, market research and competitor analysis.

• 7,600+ technologies in 109 categories, with versions and confidence scores
• Bulk: thousands of websites per run, analysed in parallel
• Beyond the page: email provider and verified SaaS tools from DNS (Google Workspace, Microsoft 365, Atlassian, HubSpot, Stripe, OpenAI and hundreds more)
• Evidence included: every detection says what it was based on (headers, cookies, HTML, scripts, DNS…)
• Fair billing: websites that cannot be reached are listed separately and never charged

Who uses it

• Sales and lead generation — qualify a prospect list by platform ("all Shopify stores using Klaviyo", "companies on Microsoft 365")
• Agencies — find sites on outdated or end-of-life versions
• Market research — measure technology adoption across an industry or a competitor set
• Security and IT — inventory the software exposed by your own domains

Example output

{
  "url": "https://allbirds.com",
  "finalUrl": "https://www.allbirds.com/",
  "statusCode": 200,
  "technologyCount": 13,
  "summary": "Shopify, Microsoft 365, Apple Pay, Cloudflare, Google Tag Manager, HSTS, Swiper, DocuSign, HTTP/3, Miro, Open Graph",
  "technologyNames": ["Shopify", "Microsoft 365", "Apple Pay", "Cloudflare", "Google Tag Manager"],
  "categories": {
    "Ecommerce": ["Shopify"],
    "Email": ["Microsoft 365"],
    "Payment processors": ["Apple Pay"],
    "CDN": ["Cloudflare"],
    "Tag managers": ["Google Tag Manager"]
  },
  "technologies": [
    {
      "name": "Shopify",
      "categories": ["Ecommerce"],
      "groups": ["Sales"],
      "version": null,
      "confidence": 100,
      "detectedBy": ["cookies", "meta", "scriptSrc"],
      "website": "https://shopify.com",
      "description": "Shopify is a subscription-based software that allows anyone to set up an online store…",
      "saas": true,
      "openSource": null,
      "pricing": ["low", "recurring"],
      "cpe": null
    }
  ],
  "analysedAt": "2026-09-20T15:41:12Z"
}

summary and technologyNames are there for spreadsheets; technologies carries the full detail.

Input

{
  "urls": ["shopify.com", "https://www.nike.com/de", "wordpress.org"],
  "includeDns": true,
  "minConfidence": 50,
  "categories": ["CMS", "Ecommerce", "Analytics"]
}

Field	What it does
urls	Domains or full URLs, one per line. Duplicates are removed.
includeDns	Also read the domain's MX, TXT, NS and SOA records (on by default, no extra charge).
minConfidence	Hide detections below this confidence. 50 removes weak single-hint matches.
categories	Optional: keep only technologies in these categories.
maxConcurrency, timeoutSecs	Tuning for very large or very slow lists.
proxyConfiguration	Optional. Most websites answer without a proxy.

Pricing

Event	Price
Website analysed	$0.01
Actor start	$0.00005 per run

$10 per 1,000 websites. Invalid addresses and websites that could not be reached are not charged; they are listed under Websites that could not be analysed in the run's output. Set Maximum cost per run to cap your spend — the run stops cleanly at the limit and tells you how many websites are left.

How detection works, and its limits

The Actor requests each website once, like a browser would, and matches the response — HTTP headers, cookies, HTML, meta tags, script URLs, inline scripts, page structure and the final URL — plus the domain's DNS records against open-source technology fingerprints.

Stated plainly:

• No JavaScript is executed. About 87% of the fingerprints (6,670 of 7,628) can be matched this way. Technologies that only reveal themselves through JavaScript variables in a running browser may be missed; frameworks on heavily client-rendered sites are the usual case.
• One page per website. The URL you give is the page that is analysed (the home page for a bare domain). Tools loaded only on checkout or login pages will not be seen — add those URLs if they matter.
• Bot-protected sites still return results. When a site answers with a block page (HTTP 403), you still get what its headers and DNS reveal — typically CDN, bot protection, email provider and verified SaaS tools — and statusCode tells you it happened.
• DNS detections describe the company, not the page. A detectedBy: ["dns"] entry such as Atlassian or DocuSign means the company verified its domain with that product.
• Speed: about 1,000 websites per hour at the default 1 GB of memory. Detection is CPU-bound, so raising the run's memory to 4 GB makes it roughly three times faster.

Fingerprints come from the community-maintained webappanalyzer project (the open continuation of Wappalyzer's rule set, GPL-3.0), refreshed regularly, with local corrections for rules that produce false positives.

FAQ

Can I run it on a schedule to track changes? Yes — add it to a Schedule and compare technologyNames between runs.

Can I use it from my own code or an AI agent? Yes. Use the API tab for ready-made JavaScript, Python and cURL snippets, or the MCP tab to give it to an AI agent.

A technology is wrong or missing. Open an issue on the Issues tab with the website URL. False positives are fixed in the Actor's own rule corrections, which survive fingerprint updates.