Tech Stack Detector avatar

Tech Stack Detector

Pricing

from $1.20 / 1,000 url analyzeds

Go to Apify Store
Tech Stack Detector

Tech Stack Detector

Affordable BuiltWith and Wappalyzer alternative. Detect 85+ technologies on any website — CMS, e-commerce, payments, ad pixels, analytics, marketing automation, live chat, frameworks, CDN and hosting — with evidence for every match. Bulk lead qualification; failed URLs are not charged.

Pricing

from $1.20 / 1,000 url analyzeds

Rating

0.0

(0)

Developer

Automation Lab

Automation Lab

Maintained by Community

Actor stats

3

Bookmarked

428

Total users

36

Monthly active users

2 days ago

Last modified

Features

Limited permissionsMulti-tenantServer interface

Share

Tech Stack Detector identifies the technologies used on any website — including frameworks, CMS, analytics, CDN, and hosting providers. WordPress powers 43% of all websites, React runs on 4.5 million sites, and Shopify hosts 4.6 million online stores. This actor detects all of these and 120+ other technologies — including e-commerce platforms, payment providers, ad pixels, marketing automation, live chat and cookie consent tools — plus the company's email provider (Google Workspace, Microsoft 365, Zoho Mail…) and SaaS tools from its public DNS records, from a single HTTP request and a few DNS lookups. A fast and affordable alternative to BuiltWith and Wappalyzer for website technology lookup.

What does Tech Stack Detector do?

Tech Stack Detector fetches a website and analyzes its HTML, scripts, meta tags, and HTTP headers to identify the technologies it uses. It detects 125+ technologies across categories like JavaScript frameworks, CMS platforms, e-commerce, payments, advertising pixels, analytics, marketing automation, live chat, CDN and hosting providers. It also reads the domain's MX, SPF and TXT records to find the email provider, email-sending services (SendGrid, Mailchimp, HubSpot…) and SaaS accounts verified on the domain (Atlassian, Slack, Zoom, DocuSign…). Versions are reported when the site exposes them (for example WordPress 6.9, jQuery 3.7.1, nginx 1.25).

Use it for competitive analysis, lead qualification (find companies using specific technologies), security audits, or technology market research. Each detection includes a numeric confidence score and the exact HTML, script, meta, or header evidence behind it, while technologies are grouped by category for easy filtering.

Who is it for?

  • Sales teams -- qualify leads by identifying companies using specific technologies (e.g., find all Shopify stores or WordPress sites)
  • Competitive analysts -- discover what frameworks, analytics, and hosting competitors rely on
  • Security auditors -- identify outdated or vulnerable technologies across a portfolio of websites
  • Market researchers -- survey technology adoption trends across industry verticals
  • Developers -- quickly understand the tech stack of any website before starting a project or integration
  • Agency teams -- profile client websites to recommend technology improvements or identify compatibility requirements

Why use Tech Stack Detector?

  • 125+ technologies detected -- covers frameworks, CMS, e-commerce, payments, ad pixels, analytics, marketing automation, live chat, cookie consent, CDN, hosting, and more
  • Email provider and SaaS from DNS -- Google Workspace, Microsoft 365, Zoho Mail and 9 more mailbox hosts, email security gateways, email senders and domain-verified SaaS tools, at no extra charge
  • Versions -- from generator tags, script URLs and server headers when the site exposes them
  • Strict signatures -- detections rely on vendor loader URLs, framework markers and response headers, not on a brand name merely appearing in page text
  • Batch processing -- analyze hundreds of websites in a single run
  • Auditable confidence scoring -- each detection includes a numeric score from 0 to 1 plus the signal evidence behind it
  • Categorized output -- technologies grouped by category for easy filtering
  • Fast and lightweight -- HTTP-only requests, no browser overhead
  • Pay-per-event pricing -- $0.0023 per analyzed URL on the Free plan, down to $0.00056 on higher Apify plans; unreachable, blocked or malformed URLs are not charged

Detected technologies

CategoryTechnologies
JavaScript FrameworkReact, Next.js, Vue.js, Nuxt.js, Angular, Svelte, Remix, Gatsby, Astro
CMS / Site builderWordPress, Drupal, Joomla, Ghost, Webflow, Wix, Squarespace, Framer, Hugo, Elementor, Yoast SEO
E-CommerceShopify, WooCommerce, Magento, BigCommerce, PrestaShop, Salesforce Commerce Cloud
PaymentStripe, PayPal, Klarna
AdvertisingMeta Pixel, Google Ads, LinkedIn Insight Tag, TikTok Pixel, Microsoft Advertising
AnalyticsGoogle Analytics, Google Tag Manager, Hotjar, Segment, Mixpanel, Plausible, Microsoft Clarity, Matomo, Heap, Amplitude
MarketingHubSpot, Mailchimp, Klaviyo, Marketo, Salesforce Pardot, ActiveCampaign
Customer Support / Live chatIntercom, Zendesk, Crisp, Drift, Tawk.to, LiveChat, Tidio, Freshchat
Cookie consent, A/B testing, monitoringOneTrust, Cookiebot, Optimizely, Sentry
CDN / Cloud / HostingCloudflare, Vercel, Netlify, AWS, Google Cloud, Microsoft Azure, Heroku, GitHub Pages, Fastly, Akamai
Web Server / BackendNginx, Apache, IIS, LiteSpeed, PHP, Express, ASP.NET
CSS Framework / FontsTailwind CSS, Bootstrap, Google Fonts, Font Awesome
SecurityreCAPTCHA, hCaptcha
Email hosting (DNS MX/SPF)Google Workspace, Microsoft 365, Zoho Mail, Proton Mail, Fastmail, Yandex 360, iCloud Mail, Amazon WorkMail, GoDaddy Email, IONOS Mail, OVHcloud Mail, Namecheap Private Email
Email security (DNS MX)Mimecast, Proofpoint, Barracuda, Cisco Secure Email, Trend Micro Email Security
Email delivery (DNS SPF)SendGrid, Mailgun, Amazon SES, Postmark, SparkPost, Mailjet, plus Mailchimp, HubSpot, Marketo, Pardot, Klaviyo, Brevo, Constant Contact, Salesforce, Zendesk, Freshdesk, Help Scout, Intercom
SaaS verified on the domain (DNS TXT)Google Search Console, Microsoft 365, Meta Business Suite, Apple Business, Atlassian, Slack, Zoom, Miro, Dropbox, Webex, DocuSign, Adobe, Stripe, OpenAI, OneTrust, KnowBe4, Yandex Webmaster

A TXT verification record shows the domain registered an account with that service; it can outlive the account, so its confidence is lower (0.85) than an MX or SPF signal.

How do I detect a website's tech stack?

ParameterTypeRequiredDefaultDescription
urlsstring[]Yes--Website URLs to analyze. Domain names without protocol are auto-prefixed with https://
checkDnsbooleanNotrueRead the domain's MX, SPF and TXT records for the email provider and SaaS tools. No extra charge. DNS is read for the host you enter without www.; a subdomain such as shop.example.com usually has no mail records of its own.

Example input

{
"urls": ["apify.com", "techcrunch.com", "hubspot.com"],
"checkDns": true
}

Recurring technology monitoring

Technology stacks change when competitors redesign, migrate platforms, add analytics, or change hosting/CDN providers. Save your urls input and schedule monthly runs for competitor watchlists, or weekly runs for vendors and high-priority accounts.

Example monthly monitoring input:

{
"urls": ["apify.com", "github.com", "shopify.com"]
}

Export each run to Google Sheets or your CRM and compare detections over time. For a broader site-audit bundle, combine this actor with Sitemap XML URL Extractor for URL inventories, SSL Certificate Checker for HTTPS health, Domain Age Checker, and Font Detector for design-system monitoring.

What technologies can Tech Stack Detector identify?

{
"url": "https://vercel.com",
"finalUrl": "https://vercel.com/",
"statusCode": 200,
"technologies": [
{
"name": "React",
"category": "JavaScript Framework",
"version": null,
"confidence": 0.96,
"evidence": ["HTML contains \"/_next/\""]
},
{
"name": "Next.js",
"category": "JavaScript Framework",
"version": null,
"confidence": 0.96,
"evidence": ["HTML contains \"/_next/\""]
},
{
"name": "Vercel",
"category": "Hosting",
"version": null,
"confidence": 0.98,
"evidence": ["Header x-vercel-id is present"]
},
{
"name": "Google Workspace",
"category": "Email Hosting",
"version": null,
"confidence": 0.97,
"evidence": ["DNS MX record aspmx.l.google.com", "DNS MX record alt1.aspmx.l.google.com"]
}
],
"technologyNames": ["React", "Next.js", "Vercel", "Google Workspace"],
"emailProvider": "Google Workspace",
"mxHosts": ["aspmx.l.google.com", "alt1.aspmx.l.google.com"],
"categories": {
"JavaScript Framework": ["React", "Next.js"],
"Hosting": ["Vercel"],
"Email Hosting": ["Google Workspace"]
},
"server": "Vercel",
"error": null
}

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

EventCostDescription
Run start$0.035One-time per run
Per URL analyzed$0.0023 (Free plan)Per website analyzed successfully

The per-URL price is lower on paid Apify plans: Bronze $0.002, Silver $0.00156, Gold $0.0012, Platinum $0.0008, Diamond $0.00056. The run start fee is $0.035 on every plan.

From December 2, 2026 the per-URL price will be: Free and Bronze $0.002, Silver $0.0018, Gold, Platinum and Diamond $0.0016. The run start fee stays $0.035.

Websites that cannot be analyzed — unreachable domains or HTTP error/blocked responses (statusCode 400 or higher) — still get a row with the reason in error, but are not charged. Malformed entries (for example https://[invalid or an ftp:// address) are rejected before the run starts: if no entry is a valid website, the run fails immediately without any charge; otherwise malformed entries are skipped without a charge and named in the run's status message and log. An empty input fails immediately without any charge. Each website is charged before its row is saved, and the run stops cleanly at your Maximum charge per run: no row is saved without its charge and no charge goes past the limit. DNS checks are included in the per-URL price.

Example costs on the Free plan (all URLs analyzed successfully):

  • 10 URLs: $0.035 + 10 x $0.0023 = $0.058
  • 100 URLs: $0.035 + 100 x $0.0023 = $0.265
  • 1,000 URLs: $0.035 + 1,000 x $0.0023 = $2.335

On the Gold plan, 1,000 URLs cost $0.035 + 1,000 x $0.0012 = $1.235.

How to detect a website's tech stack

  1. Go to Tech Stack Detector on Apify Store
  2. Click Try for free
  3. Enter one or more website URLs or domain names
  4. Click Start and wait for the analysis to complete
  5. Download results as JSON, CSV, or Excel

How to find out what technology a website uses

There are several ways to identify what technology a website runs on, ranging from free manual methods to automated bulk detection:

Method 1: Use Tech Stack Detector (fastest for any volume)

Tech Stack Detector analyzes any website and returns a structured list of detected technologies in seconds. It covers 125+ technologies, the email provider from DNS records including JavaScript frameworks, CMS and e-commerce platforms, payment providers, ad pixels, analytics and marketing tools, CDNs, and more. No browser extension or manual inspection needed.

  • Single site: Enter the URL and get results in under 5 seconds.
  • Bulk detection: Paste a list of 100–1,000+ URLs and analyze them all in one run.
  • API integration: Connect to your CRM, lead enrichment pipeline, or competitive monitoring system.

Method 2: Check HTTP response headers (free, manual)

Open your browser's developer tools (F12), go to the Network tab, reload the page, click the first request, and look at the Response Headers. Useful headers include:

  • Server: nginx or Server: Apache — reveals the web server
  • X-Powered-By: PHP/8.1 — reveals the backend language or framework
  • X-Generator: WordPress 6.4 — CMS signature
  • Via: cloudflare — CDN provider

Method 3: Inspect page source (free, manual)

Right-click any page and choose View Page Source. Search for:

  • wp-content/ → WordPress
  • Shopify.theme → Shopify
  • _next/static/ → Next.js
  • __nuxt → Nuxt.js
  • ng-version attribute → Angular

Method 4: Browser extensions

Tools like Wappalyzer (browser extension) detect technologies on the active tab. Useful for one-off lookups, but not practical for analyzing lists of websites. Tech Stack Detector is the better choice when you need to profile more than a handful of sites.

Which method should you use?

GoalBest method
Check one site quicklyBrowser extension or Tech Stack Detector
Analyze 10–1,000 websitesTech Stack Detector
Integrate into a sales/CRM pipelineTech Stack Detector API
Understand what you foundManual header/source inspection

API usage

Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: '<YOUR_API_TOKEN>' });
const run = await client.actor('automation-lab/tech-stack-detector').call({
urls: ['apify.com', 'github.com'],
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient
client = ApifyClient('YOUR_TOKEN')
run = client.actor('automation-lab/tech-stack-detector').call(run_input={
'urls': ['apify.com', 'github.com'],
})
items = client.dataset(run['defaultDatasetId']).list_items().items
for item in items:
print(f'{item["url"]}: {[t["name"] for t in item["technologies"]]}')

cURL

curl -X POST "https://api.apify.com/v2/acts/automation-lab~tech-stack-detector/runs?token=YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"urls": ["apify.com", "github.com"]}'

Integrations

Tech Stack Detector integrates with your existing workflow through the Apify platform. Connect it to Make (formerly Integromat), Zapier, or n8n to automate technology profiling across lead lists. Export results to Google Sheets for team analysis, send notifications to Slack when a target website changes its tech stack, or use webhooks to enrich CRM records with technology data automatically.

Common integration patterns include:

  • Lead enrichment -- trigger a detection run from your CRM whenever a new lead is added, and write the tech stack back to the lead record
  • Competitive monitoring -- schedule monthly runs on competitor websites and alert your team in Slack when technology changes are detected
  • Market research pipeline -- combine with a web scraping actor to build a list of company websites, then profile their tech stacks in bulk

Tips and best practices

  • Use domain names -- you can pass just apify.com instead of https://apify.com; the actor auto-prefixes the protocol.
  • Combine with lead lists -- feed a list of prospect websites to identify companies using a specific technology for targeted outreach.
  • Schedule regular runs to track technology changes over time, such as competitors migrating from one framework to another.
  • Filter by confidence -- use the numeric confidence score (0 to 1) and inspect evidence before acting on a detection.
  • Pair with Website Contact Finder -- detect the tech stack first, then extract contact information from matching websites.

Use with Claude AI (MCP)

This actor is available as a tool in Claude AI through the Model Context Protocol (MCP). Add it to Claude Desktop, Cursor, Windsurf, or any MCP-compatible client.

Setup for Claude Code

$claude mcp add --transport http apify "https://mcp.apify.com?tools=automation-lab/tech-stack-detector"

Setup for Claude Desktop, Cursor, or VS Code

Add this to your MCP config file:

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

Example prompts

  • "What technologies is apify.com built on — framework, CDN, and analytics?"
  • "Check the tech stacks of these 10 SaaS competitor sites and tell me which ones use React"
  • "Find all Shopify stores in this list of company websites"

Learn more in the Apify MCP documentation.

Legality

Yes. Tech Stack Detector only analyzes publicly visible information — HTTP response headers, meta tags, and JavaScript libraries that every browser already sees. No authentication is bypassed, no private data is accessed, and no terms of service are violated.

Technology detection is a standard practice in web development, cybersecurity, and competitive analysis. Tools like BuiltWith and Wappalyzer have operated in this space for over a decade.

Key points:

  • Only publicly accessible data is analyzed
  • No login credentials or private APIs are used
  • The tool behaves like a regular browser visit
  • Results contain technical metadata, not personal data

For more details, see the Apify guide on ethical web scraping.

Error diagnostics

When a run fails, sanitized diagnostic information (the error, a scrubbed copy of the input, and the actor, build and run IDs) is sent to our private GlitchTip error-tracking service so we can fix problems. Secret fields and URL query strings are removed first, and reports are retained for 30 days.

FAQ

How does it detect technologies? It analyzes HTML source code, inline scripts, meta tags, HTTP response headers (Server, X-Powered-By), and known file patterns. Each technology has specific signatures that the actor matches against.

Why is Google Analytics not reported when a site uses Google Tag Manager? Google Tag Manager is a container, and the shared Google tag (gtag.js) serves Google Ads as well as Google Analytics. Google Analytics is reported only when the HTML shows Analytics-specific evidence: a google-analytics.com reference or a GA measurement ID (G-… or UA-…) in the gtag.js loader or a gtag('config', …) call. A tag configured only with a Google Ads ID (AW-…) is reported as Google Ads. Analytics tags injected later by the GTM container are not visible to an HTTP-only check.

How does it find a company's email provider? It reads the domain's public DNS records: MX hosts name the mailbox provider (for example aspmx.l.google.com → Google Workspace, *.mail.protection.outlook.com → Microsoft 365). When a security gateway such as Mimecast or Proofpoint receives the mail first, the provider comes from the SPF record instead; if SPF names no mailbox host either, emailProvider is null and the gateway stays in technologies and mxHosts. emailProvider is null when the domain has no MX records or uses an unknown or self-hosted mail server; mxHosts still lists the raw hosts. Set checkDns to false to skip DNS.

Can it detect technologies loaded via JavaScript? It detects technologies referenced in inline scripts and script tags in the HTML source. Technologies loaded entirely via client-side dynamic imports after page load may not be detected, since the actor does not run a browser.

How accurate is the detection? Each detection includes a numeric confidence score from 0 to 1 and an evidence array. Unique HTTP headers and framework-specific HTML markers score higher than broad HTML references, so you can audit why every technology was reported.

How is this different from BuiltWith or Wappalyzer? Tech Stack Detector offers a lightweight, API-first alternative with pay-per-event pricing. You can integrate it directly into your workflows via the Apify API, schedule automated runs, and process results programmatically. There are no monthly subscriptions or per-seat fees.

How many websites can I analyze in one run? There is no hard limit. The actor processes URLs concurrently, so runs with hundreds or thousands of websites complete efficiently. Each successfully analyzed URL is billed separately: $0.0023 on the Free plan, down to $0.00056 on higher plans.

The actor detects no technologies for a website I know uses React/Next.js. Sites that server-render and strip framework-specific markers from the HTML may not be detectable via HTTP-only analysis. Technologies loaded entirely via client-side JavaScript after page load are harder to detect since this actor does not run a browser. Try checking the HTTP headers and source code manually.

A URL returns an error instead of results. Common causes include: the domain is unreachable, the server blocks non-browser requests (returns 403), or the URL redirects to a login page. Check the statusCode and finalUrl fields, then verify the URL is publicly accessible in a browser. Rows with an error are not charged.

  • HTTP Status Checker — Check HTTP status codes, response times, and redirect targets for any list of URLs
  • Website Health Report — Comprehensive website health and SEO audit with SSL, DNS, headers, and performance checks

Server API: detect one website's tech stack over HTTP

Tech Stack Detector is also a Server Actor. Besides normal runs, it answers short HTTP requests directly, without starting a run for each website. Copy the server URL from the Actor's Server tab (do not build it from the Actor name) and authenticate with your Apify token. Use normal Actor runs for many websites.

$curl -sS "$SERVER_URL/detect?url=apify.com" -H "Authorization: Bearer $APIFY_TOKEN"
Method and pathInputOutput and charge
GET /Noneready: true, the routes and limits; no fetching or charge
GET /detectQuery url: a domain such as apify.com or a full http(s):// URL; one website per request{ok,count,results} with one record, the same as a normal run's dataset item; one URL analyzed event for the analyzed website; no start fee

A website that answers with an HTTP error or blocks the request, and a website that cannot be reached, return an error and are free (a normal run saves such websites as uncharged rows with error). Each request has a 25-second deadline (the website fetch itself is limited to 15 seconds, up to 5 redirects) and a 128 KiB response cap, and one server works on at most eight requests at once. Nothing is cached. Errors use { "ok": false, "error": { "code": "...", "message": "...", "retryable": false } }: 400 INVALID_URL or INVALID_INPUT; 402 spending limit; 404 unknown route; 405 wrong method; 502 SITE_ERROR, SITE_UNREACHABLE or charging failure; 503 server busy or stopping; 504 TIMEOUT. Failed requests are free. Retry only when retryable is true. The Server tab shows the full OpenAPI description.