Website Tech Stack Detector - CMS, Frameworks, Analytics

Find out what websites are built with, in bulk: CMS, e-commerce platform, analytics and tag managers, JavaScript frameworks, CDN, hosting, web server, mail provider and SaaS tools, with versions when the site shows them. Over 7,000 technologies are recognized, using the open-source fingerprints of the Wappalyzer community.

• More than the HTML. Headers, cookies, script URLs, meta tags and DNS records are checked. MX, TXT and NS records reveal the mail provider (Google Workspace, Microsoft 365), the DNS host and the SaaS tools whose ownership was verified (HubSpot, Atlassian, Stripe, DocuSign...).
• Fast and cheap. One HTTP request per site, no browser: about 0.3 s per site and $1 per 1,000 sites.
• Ready to filter. technologyNames for a quick look, byCategory (CMS, Ecommerce, Analytics, CDN...) to filter in a spreadsheet, and technologies with version, confidence and categories.
• No result, no charge. Invalid inputs, unreachable sites and internal addresses are returned for transparency but not billed.

What can I use it for?

• Lead generation: find the Shopify stores, WordPress sites or HubSpot users in a list of domains, and qualify them before outreach.
• Competitive and market research: which analytics, CDN or e-commerce platforms an industry uses.
• Agencies and freelancers: audit a client's stack and versions before a quote or a migration.
• Security and IT inventory: list the web servers, frameworks and versions exposed by your own sites.
• AI agents: let an agent identify a site's stack through the Apify MCP server (see below).

Input

{ "urls": ["apify.com", "https://www.example.com/shop", "allbirds.com"] }

Output

One row per website. Example from a real run (technologies shortened):

{
    "url": "https://allbirds.com/",
    "finalUrl": "https://www.allbirds.com/",
    "status": 200,
    "technologyCount": 10,
    "technologyNames": ["Shopify", "Apple iCloud Mail", "Microsoft 365", "HSTS", "Google Tag Manager", "Cursor", "Cloudflare", "Miro", "HTTP/3", "DocuSign"],
    "byCategory": {
        "Ecommerce": ["Shopify"],
        "Webmail": ["Apple iCloud Mail", "Microsoft 365"],
        "Tag managers": ["Google Tag Manager"],
        "CDN": ["Cloudflare"],
        "Miscellaneous": ["Miro", "HTTP/3", "DocuSign"]
    },
    "technologies": [
        { "name": "Shopify", "version": null, "confidence": 100, "categories": ["Ecommerce"], "website": "https://shopify.com" }
    ],
    "error": null,
    "checkedAt": "2026-10-12T12:42:44.733Z"
}

Field	Meaning
finalUrl / status	Page reached after redirects, and its HTTP status
technologyNames	Every technology detected
byCategory	The same technologies grouped by category
technologies	Details: version (when visible), confidence (0-100), categories, website
error	Why a site could not be analyzed (not billed)

Pricing

$0.001 per website analyzed ($1 per 1,000 sites) plus Apify's small run-start fee. No subscription. Invalid inputs, unreachable sites and internal addresses are free.

How it works, and its limits

The home page (or the URL you give) is fetched once, like a search engine bot would, and its DNS records are read. Each site gets at most 4 requests per second.

JavaScript is not executed. Technologies that only appear after the page runs its scripts (some chat widgets, A/B testing tools) can be missed, and sites behind a bot challenge may show only their CDN. In return, the Actor is fast and cheap enough to scan large lists.

No personal data is collected: the output only names technologies.

Use it from AI agents (MCP)

Add website-tech-detector to the Apify MCP server in your MCP client (Claude, Cursor, VS Code...).

Integrations

Apify API, schedules, webhooks, Make, Zapier, n8n. Export as JSON, CSV, Excel or HTML.

FAQ

Where do the fingerprints come from? From webappanalyzer, the community-maintained continuation of the open-source Wappalyzer rules (GPL-3.0). They are refreshed at each build.

Need the SSL certificate, DNS and registrar too? Use WHOIS & DNS Domain Lookup or SSL Certificate Checker.

Something wrong or missing? Open an issue on the Issues tab.