Website Tech Stack Detector: BuiltWith/Wappalyzer Alternative avatar

Website Tech Stack Detector: BuiltWith/Wappalyzer Alternative

Pricing

$2.00 / 1,000 website analyzeds

Go to Apify Store
Website Tech Stack Detector: BuiltWith/Wappalyzer Alternative

Website Tech Stack Detector: BuiltWith/Wappalyzer Alternative

Find out what any website is built with: CMS, e-commerce, frameworks, analytics, ads, tag managers, payments, CDN, hosting, email provider & 7,500+ technologies with versions and confidence. Bulk-analyze thousands of domains. BuiltWith / Wappalyzer alternative.

Pricing

$2.00 / 1,000 website analyzeds

Rating

0.0

(0)

Developer

PulseData

PulseData

Maintained by Community

Actor stats

0

Bookmarked

6

Total users

3

Monthly active users

an hour ago

Last modified

Share

This actor finds out what a website is built with. You pass a list of domains or URLs and get, per site, the detected CMS, ecommerce platform, JavaScript frameworks, analytics and advertising tags, tag manager, payment processors, CDN, hosting, web server, programming language, email provider and security tools, matched against more than 7,500 technology fingerprints with versions and confidence scores. It costs $2 per 1,000 websites analyzed, and unreachable sites are not charged.

It works over plain HTTP and DNS, without a browser, so large domain lists finish quickly.

Features

  • Check what CMS a website uses (WordPress, Shopify, Webflow and others in the fingerprint set).
  • Find out if a website runs on Shopify or another ecommerce platform, for a whole list at once.
  • Bulk tech stack lookup for a list of domains, thousands per run.
  • See which analytics and ad tags a website uses, such as Google Tag Manager or ad pixels.
  • Detect a company's email provider and verified SaaS tools from DNS, such as Google Workspace or Microsoft 365.
  • Export tech stack data to CSV, Excel or JSON through the Apify dataset.

Use cases

  • Lead generation and sales intelligence: filter a domain list down to companies on Shopify, WooCommerce, HubSpot, Klaviyo or Intercom.
  • Market research: count technology usage across the sites of an industry.
  • Agency prospecting: spot old CMS versions, missing analytics, no cookie banner or no CDN.
  • Website audits and due diligence: inventory the third-party scripts, trackers and vendors on a site.
  • CRM enrichment: add a tech stack column to scraped or exported company domains.

Input

{
"urls": ["allbirds.com", "https://www.nytimes.com", "apify.com"],
"maxExternalScripts": 10,
"fetchDns": true,
"minConfidence": 50,
"includeDescriptions": false,
"concurrency": 10
}
FieldTypeDefaultMeaning
urlsarray(required)Domains or URLs, one per line
maxExternalScriptsinteger10External JavaScript files downloaded per site for deeper detection (0 to 50, 0 disables)
fetchDnsbooleantrueResolve MX, NS, TXT and CNAME records for email, DNS and verified SaaS services
minConfidenceinteger50Report only technologies at or above this confidence (0 to 100)
includeDescriptionsbooleanfalseAdd a short description to each technology
concurrencyinteger10Websites analyzed in parallel (1 to 50)
proxyConfigurationobjectno proxyUse Apify Proxy if target sites block datacenter traffic

A bare domain is fetched over HTTPS first and over HTTP if that fails.

Output

One item per website:

{
"url": "allbirds.com",
"finalUrl": "https://www.allbirds.com/",
"statusCode": 200,
"title": "Allbirds: Comfortable, Sustainable Shoes & Apparel",
"technologyCount": 6,
"technologyNames": ["Shopify", "Cloudflare", "Google Tag Manager", "Apple Pay", "PayPal", "HSTS"],
"technologies": [
{ "name": "Shopify", "slug": "shopify", "categories": ["Ecommerce"], "version": null, "confidence": 100,
"website": "https://shopify.com", "icon": "https://raw.githubusercontent.com/enthec/webappanalyzer/main/src/images/icons/Shopify.svg",
"saas": true, "oss": null, "pricing": ["low", "recurring"], "evidence": ["scriptSrc", "meta"] }
],
"saasServicesFromDns": ["DocuSign", "Miro"],
"categories": { "Ecommerce": ["Shopify"], "CDN": ["Cloudflare"], "Payment processors": ["Apple Pay", "PayPal"] },
"summary": {
"cms": null, "ecommerce": "Shopify", "framework": null, "programmingLanguage": null,
"webServer": null, "cdn": "Cloudflare", "hosting": null, "analytics": [], "advertising": [],
"tagManager": "Google Tag Manager", "payments": ["Apple Pay", "PayPal"], "marketingAutomation": [],
"liveChat": null, "crm": null, "emailProvider": "Microsoft 365", "security": ["HSTS"],
"cookieCompliance": null, "abTesting": null
},
"dns": { "mx": ["allbirds-com.mail.protection.outlook.com"], "ns": ["..."], "cname": [], "txt": ["v=spf1 ..."] },
"headers": { "server": "cloudflare", "x-powered-by": null, "via": null },
"scrapedAt": "2026-09-25T08:00:00.000Z"
}
  • technologies: every match with categories, version when the site exposes one, confidence, vendor website, icon, SaaS and open-source flags, pricing hints and the evidence type (url, html, scriptSrc, scripts, css, text, headers, cookies, meta, dom, dns, or implied by another technology).
  • summary: the first match per key category, or a list for analytics, advertising, payments, marketing automation and security.
  • saasServicesFromDns: services detected only from DNS TXT verification records.
  • dns.txt: only SPF, site-verification and a few vendor records (Google, Facebook, HubSpot, Stripe), up to 20.

A site that cannot be reached produces an item with an error field and zero technologies, and is not charged.

How it works and limitations

The actor downloads each site's HTML, headers and cookies plus up to maxExternalScripts JavaScript files (same host first), resolves DNS, and matches everything against the open-source webappanalyzer fingerprint database, the community continuation of the Wappalyzer rules. Technologies that reveal themselves only through JavaScript globals are matched from script code at reduced confidence (25).

Because there is no browser, single-page apps that render everything client-side can show fewer technologies than a browser-based tool. Only the page you pass is analyzed; the actor does not crawl other pages of the site. A site that answers with an error page or a bot challenge is still analyzed and charged; check statusCode.

Pricing

$0.002 per website analyzed (website-analyzed event). Worked example: a list of 1,000 domains where 950 respond costs 950 × $0.002 = $1.90.

FAQ

How is this different from BuiltWith or Wappalyzer? Same idea (fingerprints from HTML, scripts, headers, cookies and DNS), but pay per site with no subscription, and you get raw JSON for your own pipeline. There is no historical data; each run reads the site as it is now.

How many technologies can it detect? The bundled database has about 7,500 fingerprints across CMS, ecommerce, frameworks, analytics, ads, tag managers, payments, CDN, hosting, email and more.

Does it work on JavaScript-heavy sites? Partly. It reads the external scripts a page loads, which catches many frameworks and tags, but it does not execute JavaScript.

What is the confidence score? Each fingerprint adds confidence up to 100. Raise minConfidence to hide weak matches such as a lone cookie name.

Can I run thousands of domains? Yes. Paste the list into urls and raise concurrency. If the run migrates to another server mid-way, domains already processed are skipped.

Do I need proxies? Usually not. Turn on Apify Proxy if many target sites block datacenter IPs.

Can I schedule it or call it via API? Yes. Save a task, add an Apify schedule, and export the dataset as JSON, CSV or Excel via API, or send it to Google Sheets, Make, Zapier or n8n.

License

The source is licensed under GPL-3.0 and includes the webappanalyzer fingerprint database (GPL-3.0).