Tech Stack Detector

Find out which technologies a website runs on — CMS, e-commerce platform, analytics and ad tags, JavaScript frameworks, CDN, hosting, email provider and 7,000+ others — for a whole list of websites at once. Versions are reported where the site exposes them.

It loads each homepage once over plain HTTP (no browser), so it is fast and cheap. You pay only for websites that were actually analysed.

What you get for each website

Field	Example	Meaning
technologyNames	Shopify, Cloudflare, Google Tag Manager	All detected technologies in one line (with version if known)
technologies	[{"name":"WordPress","version":"6.8","confidence":100,"categories":["CMS","Blogs"],"website":"https://wordpress.org"}]	Full detail per technology
byCategory	{"CMS":["WordPress"],"Analytics":["Google Analytics"]}	Technologies grouped by category — easy to filter
technologyCount	18	Number of technologies found
finalUrl, statusCode	https://www.example.com/, 200	Where the URL ended up after redirects
error	HTTP 403 (blocked ...)	Set when the site could not be analysed

Use cases

• Lead generation: find all Shopify, WooCommerce or Magento stores in a list, or every company that uses HubSpot or Salesforce.
• Sales intelligence: know a prospect's CMS, analytics and marketing stack before the first call.
• Market research: measure how common a framework or tool is across a set of competitors.
• Agencies: audit client and prospect sites in bulk.
• AI agents: works as a tool through the Apify MCP server — give it URLs, get structured JSON back.

Input

{
  "urls": ["wordpress.org", "https://www.allbirds.com", "zalando.de"],
  "checkDns": true
}

Domains without https:// are accepted. With checkDns on, public DNS records (MX, TXT, NS, SOA) are also read, which finds email, DNS hosting and services verified on the domain (for example Microsoft 365 or Atlassian Cloud).

Pricing

Pay per event: $8 per 1,000 analysed websites. There is no extra charge per run.

You are not charged when a website does not exist, cannot be reached, blocks automated requests (HTTP 403 and similar), shows a bot-protection page ("Just a moment...", captcha) instead of the site, or disallows bots in robots.txt. Such items are still returned, with the reason in error.

How it works, and its limits

Detection uses the open-source webappanalyzer fingerprints (GPL-3.0): patterns in the HTML, script URLs, inline scripts, meta tags, HTTP headers, cookies, page elements and DNS records.

Please know what it can and cannot see before you buy:

• Only the homepage (or the URL you give) is loaded, without running JavaScript. Tools that only appear after JavaScript runs in a real browser can be missed. Patterns that need a browser (JavaScript variables, XHR calls, stylesheets) are not used.
• Some sites block automated requests (often big platforms behind bot protection). We respect that and do not try to get around it; these sites are free and marked in error.
• robots.txt is respected. If a site disallows the page for all bots, it is skipped.
• DNS-based results show services that are connected to the domain (for example a domain verification record), which usually but not always means the company uses them.
• Fingerprints are community-maintained; a rare technology can be missed or misidentified. Report it in Issues and it will be checked.

Open source

This Actor's source code is public and licensed under GPL-3.0, like the fingerprint data it uses.

Support

Open an issue on the Actor's Issues tab. Issues are answered within 24 hours.