Tech Stack Detector - BuiltWith & Wappalyzer Alternative avatar

Tech Stack Detector - BuiltWith & Wappalyzer Alternative

Pricing

from $0.70 / 1,000 website analyseds

Go to Apify Store
Tech Stack Detector - BuiltWith & Wappalyzer Alternative

Tech Stack Detector - BuiltWith & Wappalyzer Alternative

Find what any website is built with: CMS, ecommerce platform, analytics, ads, CDN, hosting, frameworks and email provider. 7,000+ technologies with versions, $1 per 1,000 websites, unreachable sites free. Bulk website technology lookup, no API key.

Pricing

from $0.70 / 1,000 website analyseds

Rating

0.0

(0)

Developer

Sumitr Mardy

Sumitr Mardy

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

an hour ago

Last modified

Features

Limited permissions

Share

Find out what any website is built with: CMS, ecommerce platform, analytics, ad pixels, marketing automation, live chat, payment processors, JavaScript frameworks, web server, hosting, CDN, and the company's email provider. Paste a list of domains and get one row per website, with versions where the site reveals them.

Matches against 7,000+ technologies (the open Wappalyzer rule set), where most detectors in the Store check 85–200. It also reads the domain's DNS, so you get the email provider (Google Workspace, Microsoft 365, Zoho…) and services the company has verified in DNS: SendGrid, Mailchimp, HubSpot, Atlassian, Zoom, DocuSign, Notion…

$1 per 1,000 websites, and you only pay for websites where something was found. Unreachable, blocked and empty sites are free. No API key, no browser, no login.

Built for:

  • Lead generation: every Shopify store, WordPress site or HubSpot user in a list.
  • Sales intelligence: who runs a competitor's product.
  • Agencies: audits before a pitch.
  • Market research: technology share across an industry.

What you get

FieldExample (hubspot.com)
domain, url, httpStatus, titlehubspot.com, https://www.hubspot.com/, 200, "HubSpot | Software & Tools for your Business"
technologyCount32
technologies[{"name":"HubSpot CMS Hub","version":"","confidence":100,"categories":["CMS","Blogs"],"website":"https://www.hubspot.com/products/cms"}, …]
technologyNames["Cloudflare", "HubSpot", "Linkedin Insight Tag", "Stripe", "Zapier", …]
cms["HubSpot CMS Hub"]
ecommerce["Shopify"]
analytics["Google Analytics", "Mixpanel", "Hotjar"]
advertising["Linkedin Ads", "Meta"]
tagManagers["Google Tag Manager"]
marketing["HubSpot", "Klaviyo", "Mailchimp"]
liveChat["Intercom"]
payments["Stripe"]
jsFrameworks["React", "Next.js"]
webFrameworks["PHP", "Ruby on Rails"]
webServers["Nginx"]
hosting["Vercel", "Amazon Web Services"]
cdn["Cloudflare"]
security["HSTS", "reCAPTCHA", "OneTrust", "Let's Encrypt"]
dnsVerifiedServices["Google Workspace", "Atlassian Cloud", "DocuSign", "Zoom", "Notion"]: tools the company verified its domain with, kept apart from what the website runs
emailProvider, mxRecordsGoogle Workspace, ["aspmx.l.google.com", …]
status, errorok, ""

The category columns are plain lists, so they export cleanly to CSV and Excel.

status is one of:

  • ok: billed.
  • no_technologies: the page loaded but nothing matched.
  • blocked: the site refused the request (401/403/429/503). Technologies seen in headers and DNS are still returned.
  • http_error, unreachable, duplicate, invalid_input.
  • max_cost_reached or free_work_limit.

Only ok is billed. Every row has every key, and lists are always lists.

How it detects

For each website the actor:

  1. Loads the home page and follows redirects.
  2. Reads robots.txt, the TLS certificate and DNS records (MX, TXT, NS).
  3. Matches all of it against the Wappalyzer rules: HTML, script URLs, meta tags, headers, cookies, robots.txt, certificate issuer and DNS.

There is no browser. That is why it is fast and cheap, and it also sets the limit described below.

How to use it

  1. Paste domains or URLs into Websites, one per line: shopify.com, www.example.co.uk, https://example.com/shop. A bare domain is tried over https, then with www., then over http.
  2. Keep Check DNS on. It adds the email provider and the DNS-verified services at no extra cost.
  3. Start the run. Large lists are fine: about 100 websites take 35 seconds at the default concurrency of 20.
  4. Download the results as CSV, Excel or JSON, or filter the table by any column.

Pricing

EventPriceWhen
website$0.001the home page loaded and at least one technology was found

That is $1 per 1,000 websites, cheaper on higher Apify plans. Rows with any other status are free. Apify adds its standard tiny start event per run, and the run stops cleanly at your Max cost per run.

Speed and accuracy

Measured on Apify at 1 GB with 112 websites (100 small businesses from the UK and US plus well-known sites):

  • 99 websites analysed in 34 seconds. 5 were blocked, 5 unreachable and 1 empty, all free.
  • Median 12 technologies per website, up to 33.
  • CMS found on 61 of the 99, analytics on 53, CDN on 60.
  • Email provider found on 84 of 99.

Honest limits

  • No browser. Technologies that only show up after JavaScript runs (some tag-manager-loaded pixels, single-page apps that render everything client-side) can be missed. Server-rendered sites, which are most CMS and ecommerce sites, are covered well.
  • Home page only. A tool used only on /checkout or a subdomain is not seen unless you pass that URL.
  • Bot protection. Sites behind aggressive bot protection return blocked. You still get what headers and DNS reveal, free.
  • DNS-verified services (Zoom, DocuSign, Atlassian…) mean the company verified its domain with that service. That is a strong sign it uses the service, but not proof of how much.
  • Versions appear only when the site shows them, so version is often empty.

What can you do with tech stack data?

  • Build lead lists by technology: every Shopify store, WordPress site or Klaviyo user in a list of domains, ready for outreach.
  • Qualify leads before a call: know a prospect's CMS, email provider and marketing tools before the first email.
  • Track competitors and market share: see which analytics, chat or payment tools an industry has adopted.

How to check what a website is built with

  1. Open the actor and paste your domains into Websites.
  2. Keep Check DNS on to get the email provider.
  3. Click Start and wait about 35 seconds per 100 websites.
  4. Export the table to CSV, Excel or JSON, or connect it to Google Sheets, Zapier or Make.

How much does it cost to detect a website's tech stack?

$1 per 1,000 websites, and only for websites where something was found. Apify's free plan includes $5 of monthly credit, enough for about 5,000 websites a month.

The actor reads only what every visitor's browser receives: the public home page, robots.txt and public DNS records. It never logs in or collects personal data. Respect each site's terms and your local law when you use the results.

Use it from AI agents (MCP)

Hosted, with OAuth sign-in:

{
"mcpServers": {
"tech-stack": {
"url": "https://mcp.apify.com/?tools=sumitr_mardy/tech-stack-detector"
}
}
}

With an API token instead of OAuth:

{
"mcpServers": {
"tech-stack": {
"url": "https://mcp.apify.com/?tools=sumitr_mardy/tech-stack-detector",
"headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }
}
}
}

Local stdio:

{
"mcpServers": {
"tech-stack": {
"command": "npx",
"args": ["-y", "@apify/actors-mcp-server", "--actors", "sumitr_mardy/tech-stack-detector"],
"env": { "APIFY_TOKEN": "YOUR_APIFY_TOKEN" }
}
}
}

Agent tip: pass several domains in one call, because a run costs the same start fee for 1 or 1,000. When only names are needed, read technologyNames and the category columns instead of the full technologies objects.

Run it from code

Python:

from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("sumitr_mardy/tech-stack-detector").call(run_input={
"websites": ["allbirds.com", "gymshark.com", "wordpress.org"],
})
for x in client.dataset(run["defaultDatasetId"]).iterate_items():
print(x["domain"], x["ecommerce"], x["cms"], x["emailProvider"])

cURL (waits for the run and returns the rows):

curl -X POST "https://api.apify.com/v2/acts/sumitr_mardy~tech-stack-detector/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"websites":["stripe.com","notion.so"]}'

FAQ

How is this different from BuiltWith? BuiltWith keeps a historical index and charges for API access. This actor checks each website live, right now, at $1 per 1,000. It does not have BuiltWith's history of past technologies.

Can I find all Shopify stores in a city or niche? Start from a list of websites, for example from Google Maps Scraper, then filter this actor's results on ecommerce.

Where do the technology rules come from? From the community-maintained Wappalyzer rule set (enthec/webappanalyzer, GPL-3.0), plus the actor's own DNS-based email provider detection.