Tech Stack Detector - Wappalyzer & BuiltWith Alternative avatar

Tech Stack Detector - Wappalyzer & BuiltWith Alternative

Pricing

from $2.00 / 1,000 results

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

Tech Stack Detector - Wappalyzer & BuiltWith Alternative

Returns each website's email provider (Google Workspace, Microsoft 365, Zoho) and the SaaS tools connected to its domain, read from DNS MX, SPF and TXT records, plus its CMS, frameworks, analytics, payments and CDN. Bulk URL lists, plain HTTP, no browser, no API key. JSON, CSV or API.

Pricing

from $2.00 / 1,000 results

Rating

0.0

(0)

Developer

Ben

Ben

Maintained by Community

Actor stats

1

Bookmarked

118

Total users

14

Monthly active users

3 hours ago

Last modified

Share

🔎 Tech Stack and Email Provider Detector for Any Website

Find out which email provider a company uses (Google Workspace, Microsoft 365, Zoho) and which SaaS tools it has connected to its domain (Atlassian, DocuSign, OpenAI, Canva, Slack and more), read from the domain's DNS MX, SPF and TXT records. The same row also lists the site's CMS, frameworks, analytics, payment provider and CDN, found from the page's headers, HTML, scripts and cookies. A page alone never shows the email and SaaS layer, which is what sales teams use to qualify a lead.

Feed it a list of domains and get one structured record per site, for lead qualification, prospect research and competitor tracking. It is plain HTTP analysis without a headless browser, so long lists run fast, and every technology says which signal found it (detectedBy). Export to JSON/CSV/Excel, run on a schedule, call via API, or connect to Make, Zapier or n8n.

💵 Pricing

You pay per website row: $0.0025 on the Free plan, less on paid Apify plans, plus a start fee of $0.00005 per run. From November 12, 2026 a row costs $0.002875 on the Free plan, with the same plan discounts; the start fee stays. A site that cannot be reached costs nothing: it gets no dataset row and is listed with its error and error_type in the run's key-value store record FAILED_SITES.

🧩 What is the Website Tech Stack Detector?

It turns any list of website URLs into a structured technology report. For each site it fetches the page over HTTP, inspects the response headers, HTML, scripts, stylesheets and meta tags, and matches them against 100+ technology signatures across 15+ categories. You get a deduplicated list of detected technologies — each with a category and a confidence rating — so sales, marketing and research teams can profile prospects and competitors in bulk without manually viewing source on every page.

What data does it extract?

  • Email provider and senders from MX and SPF records (Google Workspace, Microsoft 365, Zoho, SendGrid, Mailgun, Amazon SES, HubSpot...) under the category Email
  • SaaS tools that verified the domain from TXT tokens (Atlassian, Stripe, Facebook, Apple, Slack, Zoom, OpenAI, Canva, DocuSign...) under the category SaaS verification
  • Detected technologies — name, category, confidence (high/medium) and detectedBy (header, cookie, html, script, meta or dns) for each
  • Technology count and a categories summary (techs grouped by category)
  • Server and X-Powered-By headers, plus the meta generator tag
  • Page title and meta description
  • SSL flag, HTTP status code and any redirect URL
  • Version numbers for common frameworks (WordPress, jQuery, Bootstrap, React, Vue, Angular) where exposed
  • Per-site timing (analysis_time_ms); sites that cannot be reached are free and left out of the results

Across CMS & site builders (WordPress, Shopify, Wix, Squarespace, Webflow, Drupal, Ghost, Contentful, Strapi), frontend frameworks (React, Next.js, Vue, Nuxt, Angular, Svelte, Gatsby, jQuery), CSS frameworks, web servers & backends (Nginx, Apache, PHP, Express, ASP.NET, Rails, Django, Laravel), CDN & hosting (Cloudflare, Vercel, Netlify, Heroku, AWS, GCP, Azure, Fastly), analytics (Google Analytics, GTM, Hotjar, Mixpanel, Segment, Amplitude, Plausible, Matomo), marketing & CRM (HubSpot, Mailchimp, Klaviyo, Salesforce, Marketo), customer support (Intercom, Zendesk, Drift, Crisp, Tawk.to), e-commerce (WooCommerce, Magento, BigCommerce, PrestaShop), payments (Stripe, PayPal, Braintree, Square), security (reCAPTCHA, hCaptcha, Turnstile) and fonts.

⬇️ Input

Pass a list of URLs (with or without https://), an optional cap and the DNS switch:

FieldDescription
urlsList of website URLs to analyze — https:// is optional (e.g. airbnb.com)
maxUrlsMaximum number of URLs to process (0 = unlimited)
includeDnsAlso read each domain's MX and TXT records to find the email provider, email senders and SaaS tools (default true; adds one DNS lookup per site, run in parallel with the page fetch)

Example input

{
"urls": [
"https://stripe.com",
"https://vercel.com",
"shopify.com",
"notion.so"
],
"maxUrls": 0,
"includeDns": true
}

⬆️ Output

Each analyzed site is one clean record (view as a table, or export JSON / CSV / Excel). The sample is a real stripe.com row, shortened to five of its 16 technologies:

{
"url": "https://stripe.com",
"domain": "stripe.com",
"success": true,
"technologies": [
{ "name": "Next.js", "category": "Frontend Framework", "confidence": "high", "version": null, "detectedBy": "html" },
{ "name": "Nginx", "category": "Web Server", "confidence": "high", "version": null, "detectedBy": "header" },
{ "name": "Intercom", "category": "Customer Support", "confidence": "high", "version": null, "detectedBy": "script" },
{ "name": "Google Workspace", "category": "Email", "confidence": "high", "version": null, "detectedBy": "dns" },
{ "name": "Atlassian", "category": "SaaS verification", "confidence": "high", "version": null, "detectedBy": "dns" }
],
"technology_count": 16,
"categories": {
"Frontend Framework": ["React", "Next.js"],
"Web Server": ["Nginx"],
"Customer Support": ["Intercom"],
"Payment": ["Stripe", "PayPal"],
"Email": ["Google Workspace"],
"SaaS verification": ["Google Search Console", "Microsoft 365", "Atlassian", "Facebook", "Apple", "DocuSign", "OpenAI", "Canva"]
},
"server": "nginx",
"powered_by": null,
"meta_generator": null,
"title": "Stripe | Financial Infrastructure to Grow Your Revenue",
"description": "Stripe is a financial services platform that helps all types of businesses accept payments...",
"status_code": 200,
"redirect_url": "https://stripe.com/en-de",
"ssl": true,
"error": null,
"error_type": null,
"analyzed_at": "2026-10-25T11:51:50.325363",
"analysis_time_ms": 494
}

💡 Use cases

  • 🎯 Sales intelligence — technographic targeting: find companies running Shopify, HubSpot, Salesforce or any specific tool and tailor your outreach.
  • 🥊 Competitive analysis: see exactly which CMS, frameworks, analytics and payment stack your competitors run.
  • 📊 Market research: measure technology adoption across hundreds or thousands of domains to spot trends.
  • 🛡️ Security & audit: flag outdated frameworks, exposed server headers and missing protections across your own properties.

❓ FAQ

How do I detect what technology a website uses? Paste one or more URLs into urls and run. For each site you get a categorized list of detected technologies (CMS, frameworks, analytics, payments and more), each with a confidence rating.

Which technologies can it detect? 100+ across 15+ categories — CMS and site builders, frontend and backend frameworks, CSS frameworks, web servers, CDN and hosting, analytics, marketing and CRM, customer support chat, e-commerce, payment processors, security and fonts, plus email providers, email senders and SaaS tools found in DNS.

How does DNS detection work? With includeDns on (the default) it reads the domain's MX records (who hosts the mailboxes), its SPF record (which services may send email for the domain) and its TXT verification tokens (which SaaS tools the company proved it owns the domain to). These finds carry detectedBy: "dns" and the categories Email or SaaS verification. They show tools a page never loads, such as Google Workspace, Microsoft 365, Atlassian or Slack. Set includeDns to false for page detection only.

Does it use a real browser? No. It uses fast HTTP analysis of headers, HTML, scripts, stylesheets and meta tags — so it's quick, cheap to run at scale and avoids the blocking issues headless browsers hit.

Can it find websites using a specific tool (e.g. Shopify or HubSpot)? Yes — run your list of domains, then filter the output by technology name or category to keep only the sites using the tool you care about.

How accurate is the detection? Each technology carries a confidence of high or medium based on how it was matched. Strong signatures (unique scripts, headers, CDN hosts) score high.

Do I need an API key or login? No. It reads publicly accessible pages — just supply the URLs.

Can it detect version numbers? For common frameworks (WordPress, jQuery, Bootstrap, React, Vue, Angular) it extracts a version when the page exposes one; otherwise version is null.

Why didn't it detect a technology I know is there? Some tools load only after JavaScript executes, or are proxied behind a CDN, so they leave no HTTP-level signature. Single-page apps may also hide indicators behind client-side rendering.

How many URLs can I analyze at once? As many as you like — set maxUrls to cap a run, or leave it at 0 for unlimited batch processing.

Can I run it on a schedule or via API? Yes — schedule recurring runs in Apify, call it via the API/SDK, or connect it to Make, Zapier or n8n.

Is using this legal? It only reads publicly available page data. Use it responsibly for research, sales and audits, and follow applicable laws and each site's terms.

🔗 You might also like


Keywords: tech stack detector, email provider lookup, website technology checker, technographics, detect CMS, find Shopify stores, sales intelligence, competitor tech stack, framework detection, website analyzer, lead generation, technology lookup, what tech does a website use, web technology scraper, DNS TXT record lookup, SPF record checker, SaaS tools detection.