Website Tech Stack Detector – BuiltWith Alternative avatar

Website Tech Stack Detector – BuiltWith Alternative

Pricing

from $2.00 / 1,000 website analyzeds

Go to Apify Store
Website Tech Stack Detector – BuiltWith Alternative

Website Tech Stack Detector – BuiltWith Alternative

Find the tech stack of any website: CMS, ecommerce platform, analytics, CDN, hosting, frameworks and 7,600+ tools. Scan thousands of sites or a Google Maps dataset. Unreachable sites are free.

Pricing

from $2.00 / 1,000 website analyzeds

Rating

0.0

(0)

Developer

David Simpkins Jr.

David Simpkins Jr.

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

9 hours ago

Last modified

Categories

Share

Website Technology Detector – BuiltWith & Wappalyzer Alternative

Find out what any website is built with. Paste a list of websites (or a Google Maps / Google Search dataset) and get back each site's CMS, ecommerce platform, analytics and ad tags, CDN, hosting, web server, programming language, JavaScript frameworks, payment providers, chat widgets and more, from a library of 7,600+ technology fingerprints.

Built for:

  • Sales and lead generation: build lists like "Shopify stores using Klaviyo" or "WordPress sites without Google Analytics", then add emails and socials in the same run.
  • Agencies: check a prospect's stack before the first call, or find every site in a city still on an old CMS.
  • SaaS market research: measure adoption of your product and your competitors' across thousands of domains.
  • Security and IT: inventory web servers, frameworks and versions across a domain portfolio.

Features

  • 7,600+ technologies in 109 categories, using the open-source Wappalyzer-format fingerprint database (see Credits).
  • Reads everything a server sends: HTTP headers, cookies, HTML, script URLs, inline scripts, meta tags, CSS and static page elements.
  • DNS checks (on by default): DNS hosting (Route 53, Cloudflare DNS…), email provider (Google Workspace, Microsoft 365) and SaaS domain verifications (Atlassian, Stripe, HubSpot, Zoom…) that a page scan can't see.
  • Versions where the site reveals them (e.g. WordPress 6.9, jQuery 3.5.1, Yoast SEO 25.1).
  • Confidence score per technology, plus implied technologies (WordPress → PHP, MySQL; Next.js → React).
  • Ready-made columns: cms, ecommerce, analytics, tagManagers, cdn, hosting, paas, server, programmingLanguages, javascriptFrameworks, webFrameworks, paymentProcessors, liveChat, crm, marketingAutomation, email, and a full byCategory map.
  • Filters that save money: output only sites in a category (e.g. Ecommerce) or using a named technology (e.g. Shopify). Filtered-out sites are not charged.
  • Optional contacts: emails, phone numbers and social profiles from the same pages, at no extra cost.
  • Chains with other Actors: give it a dataset ID and the column name with the website URL; the source row is kept in source.
  • Fast: a plain HTTP scan takes about 0.5 seconds per site, so 10,000 sites finish in well under an hour.

Input

FieldWhat it does
WebsitesURLs or bare domains (example.com). Duplicates are removed.
Or: Apify dataset ID + website fieldScan every row of another run's dataset, e.g. a Google Maps scraper (website).
Pages per site1 = homepage (default). 2–3 also scans a shop, pricing, blog or about page.
Only output sites using these categoriese.g. Ecommerce, CMS, Live chat.
Only output sites using any of these technologiese.g. Shopify, WordPress, HubSpot.
Minimum confidenceDefault 50. Set 0 to see weak hints too.
Check DNS recordsDefault on.
Include contactsDefault off.
Include detection evidenceAdds the matched rule and text for each detection.

Output example

Data below is made up for illustration.

{
"inputUrl": "examplestore.com",
"url": "https://www.examplestore.com/",
"domain": "examplestore.com",
"status": "ok",
"title": "Example Store – Wool Sneakers",
"technologyCount": 14,
"technologies": [
{
"name": "Shopify",
"version": null,
"categories": ["Ecommerce"],
"confidence": 100,
"website": "https://shopify.com",
"icon": "https://raw.githubusercontent.com/enthec/webappanalyzer/main/src/images/icons/Shopify.svg",
"detectedVia": ["headers", "scriptSrc", "meta"]
},
{
"name": "jQuery",
"version": "3.5.1",
"categories": ["JavaScript libraries"],
"confidence": 100,
"website": "https://jquery.com",
"icon": "https://raw.githubusercontent.com/enthec/webappanalyzer/main/src/images/icons/jQuery.svg",
"detectedVia": ["scriptSrc"]
}
],
"byCategory": {
"Ecommerce": ["Shopify"],
"CDN": ["Cloudflare"],
"Email": ["Klaviyo"],
"Payment processors": ["PayPal", "Apple Pay"],
"Tag managers": ["Google Tag Manager"]
},
"cms": [],
"ecommerce": ["Shopify"],
"analytics": [],
"tagManagers": ["Google Tag Manager"],
"cdn": ["Cloudflare"],
"hosting": [],
"paas": [],
"server": [],
"programmingLanguages": [],
"javascriptFrameworks": [],
"paymentProcessors": ["PayPal", "Apple Pay"],
"domainVerifications": ["Atlassian Cloud", "DocuSign", "Zoom"],
"pagesScanned": ["https://www.examplestore.com/"],
"scannedAt": "2026-10-21T14:00:00.000Z"
}

domainVerifications lists services found only through DNS TXT verification records. They tell you which SaaS accounts the company has (useful for sales), but they are kept out of technologies because the website itself doesn't run them.

Sites that can't be reached come back as {"status": "error", "error": "http-403"} (or unreachable: ENOTFOUND, http-404, …) and are free.

Pricing

$0.002 per website analyzed ($2 per 1,000 sites), no start fee. You are not charged for:

  • sites that are down, don't exist or block the request,
  • sites removed by your category or technology filters.

Contacts and DNS checks are included in the same price.

Limits

  • This Actor reads what the server sends; it does not run a browser. Fingerprint rules that need JavaScript to execute (js globals, network requests made after load) are skipped. We added static rules for the most common cases (Next.js, Nuxt, Remix, SvelteKit, Squarespace, Framer, Google Ads, Klaviyo and others), so popular stacks are still detected. A site that renders everything client-side may show fewer tools than a browser extension would find.
  • Some large sites block automated requests (http-403). Turn on Apify Proxy and run those again. Sites behind an interactive bot challenge may stay blocked.
  • Versions only appear when the site exposes them (in a header, generator tag or file name).

Tips

  • For lead lists, combine a Google Maps scraper (e.g. "dentists in Austin") with this Actor via dataset ID, then filter by category.
  • Keep Pages per site at 1 for large lists; use 2–3 for deeper audits of fewer sites.
  • Turn on Include detection evidence if you want to see exactly why a technology was reported.

Credits and license

Technology fingerprints come from webappanalyzer by Enthec, the community continuation of Wappalyzer's open-source rules, licensed under GPL-3.0. The rules file and its license ship with this Actor (src/fingerprints/). We fixed a few rules that caused false positives and added static rules for browser-only fingerprints; those changes are listed in src/supplements.js. Icons link to the same project.

Questions, or a technology we miss? Open an issue on the Actor page.