Website Tech Stack Detector

Find out what any website is built with. Paste a list of domains and get, for each one, the detected CMS or site builder, ecommerce platform, JavaScript framework, web server, hosting and CDN, analytics and ad pixels, tag manager, live chat, payment provider, cookie-consent tool, A/B testing and fonts, with version numbers where the page exposes them and the evidence behind each detection. It also infers the domain's email provider (Google Workspace, Microsoft 365 and others) from MX records.

It is a plain HTTP fetch plus fingerprint matching, with no browser, so it is fast and cheap enough to run over long lead lists.

Find out what CMS a website uses

Enter one or more domains and read the technologyNames and categories fields. WordPress, Drupal, Joomla, Ghost, Webflow, Wix, Squarespace, Framer and Shopify-style platforms are matched from headers, cookies, script URLs, meta tags (such as generator) and page HTML. Each detection in technologies lists its category, a version when one is exposed, and the evidence sources (header:*, cookie, script, meta:*, html).

Bulk technology lookup for lead lists

Feed a column of domains from a CRM or spreadsheet and get one row per site. Filter the dataset afterwards, for example for rows whose technologyNames include a given ecommerce platform and a given email marketing or chat tool. Results export as JSON, CSV, Excel or via the API.

Use cases

• Lead qualification and segmentation: find sites on a specific platform, or still on an older stack, before you reach out.
• Competitor research: see which analytics, chat, payment and tag-manager tools a competitor loads.
• Agency prospecting: shortlist sites by CMS or by missing tools (for example no cookie-consent tool detected).
• Migration planning: inventory the platforms across a portfolio of domains.
• Security and tech audits: spot exposed server and poweredBy header values and framework versions.
• CRM enrichment: add technology and email-provider columns to existing records.

Input

Field	Type	Default	Notes
urls	array of strings	required	Domains or URLs. Bare domains get https:// added. Duplicates are removed.
detectEmailProvider	boolean	true	Look up MX records to identify the email provider.
maxConcurrency	integer	10	Sites analyzed in parallel, 1 to 25.

{
  "urls": ["shopify.com", "https://www.wordpress.org"],
  "detectEmailProvider": true,
  "maxConcurrency": 10
}

Output

One dataset row per site. Fields: input, url, finalUrl, statusCode, title, technologies, technologyNames, categories, server, poweredBy, mx, emailProvider and error. The values below are illustrative of the shape.

{
  "input": "example.com",
  "url": "https://example.com",
  "finalUrl": "https://www.example.com/",
  "statusCode": 200,
  "title": "Example Store",
  "technologies": [
    { "name": "Next.js", "category": "JS framework", "version": null, "evidence": ["html"] },
    { "name": "Google Tag Manager", "category": "Tag manager", "version": null, "evidence": ["script"] }
  ],
  "technologyNames": ["Next.js", "Google Tag Manager"],
  "categories": ["JS framework", "Tag manager"],
  "server": "nginx",
  "poweredBy": null,
  "mx": ["aspmx.l.google.com"],
  "emailProvider": "Google Workspace"
}

If a site cannot be fetched, the row contains input, url, an error (such as a network error code) and an empty technologies array. emailProvider is Other when MX records exist but match no known provider, and null when none are found.

Pricing

Pay per event: $0.002 per site analyzed ($2 per 1,000 sites), no subscription.

• 500 sites: $1.00
• 5,000 sites: $10.00
• 50,000 sites: $100.00

One charge is made per site analyzed successfully; rows that returned an error are free. Apify platform usage is billed by Apify per its plan. Set a maximum charge per run in the run options and the actor stops when it is reached.

How it works and limitations

• Only the URL you give is fetched (the homepage), one request per site, following redirects, with a 25-second timeout. The first 3 MB of HTML is examined.
• Detection uses 130+ hand-written fingerprints. Patterns are kept specific, so a miss is more likely than a false positive.
• Technologies injected only by client-side JavaScript after page load may be missed, since no browser runs.
• Inner pages are not crawled, so tools used only on checkout or blog pages will not appear.
• Sites that block automated requests may return an error or a challenge page instead of the real site.
• Email provider comes from MX records only and shows who receives mail, not who sends it.

Built and maintained with AI assistance. Missing a technology? Request it in the Issues tab.

FAQ

How do I find out what CMS a website is using? Run the actor with the domain and check technologyNames for a CMS or site builder such as WordPress, Drupal, Webflow or Wix, and technologies[].evidence to see why it matched.

Can I check thousands of websites at once? Yes. Pass them in urls and raise maxConcurrency up to 25. Cost is $0.002 per site.

How can I tell which email provider a domain uses? Leave detectEmailProvider on. The mx and emailProvider fields show the MX hosts and the provider inferred from them.

Why was a technology on a site not detected? It may be loaded only by client-side JavaScript, appear only on inner pages, or not have a fingerprint yet. Report it in the Issues tab.

Does it detect version numbers? Where the page exposes them (for example in a generator meta tag or a script URL), they appear in version; otherwise version is null.

Is this a Wappalyzer or BuiltWith replacement? It is an independent tool with its own, smaller fingerprint set focused on common technologies, priced per site with no subscription.

Related tools

Other actors by the same developer (same flat pay-per-result pricing, no subscription):

• Apple App Store Reviews Scraper (Multi-Country)
• Article Extractor – Clean Text & Markdown for LLM/RAG
• Company Jobs Scraper: Workday, Greenhouse, Lever, Ashby
• Bulk Domain Checker — WHOIS/RDAP, DNS, SPF/DMARC, SSL Expiry
• Bulk PageSpeed Insights & Core Web Vitals Checker
• PDF to Text Extractor (Bulk, with Metadata)
• Website SEO Audit Crawler
• Sitemap Extractor & Bulk URL Status Checker
• Website Screenshot – Bulk Full Page PNG, JPEG & PDF

Integrations

Run it from the Apify API, a schedule, or no-code tools: the Apify apps for Zapier, Make and n8n can start any public actor ("Run Actor") and read its dataset. AI agents can call it through the Apify MCP server.