Website Tech Stack Detector

Detect common CMS, frameworks, analytics, ecommerce, CDN, payment, marketing, and support technologies across a list of public websites. Every site returns one flat record of 73 columns: a named column per technology category, the infrastructure and security headers the server sent, the page's title, description, generator and canonical URL, and the emails, phone numbers and social profiles published on the page. Set max_items before each run to keep output and cost predictable.

What data can I extract?

• Batch URL analysis with one flat 73-column record per site
• A filterable column per technology category: cms, ecommerce_platform, framework, javascript_libraries, ui_libraries, analytics, advertising, marketing, payments, cdn, hosting, server_tech, programming_language, security_tech, support_tech, privacy_tools, monitoring, search_tech, media_tech, forms_tech, caching_tech
• Full technology list, categories, count, and per-technology evidence (header or HTML)
• Infrastructure: server, x_powered_by, content_type, content_length_bytes, cache_control, cdn_cache_status, cookie_names, response_time_ms
• Security posture: security_headers, hsts
• Redirects and identity: final_url, domain, is_https, redirect_count, redirect_chain, HTTP status
• Page metadata: title, h1, meta_description, meta_keywords, meta_generator, meta_robots, language, canonical_url, favicon_url, og_site_name, og_image, schema_org_types, hreflang_count, script_count, third_party_script_hosts
• Contact and social: emails, phones, linkedin_url, twitter_url, facebook_url, instagram_url, youtube_url, github_url, tiktok_url, twitter_handle
• Optional crawl profile with include_details: robots_txt_found, sitemap_url, robots_disallow_count, contact_page_url
• Fast HTTP-only execution without a browser

Every result is written to the default dataset and can be downloaded as JSON, CSV, Excel, or XML.

All 73 columns

Identity — cookie_names, og_site_name, title

Status — cdn_cache_status, content_type, is_https, schema_org_types, status

Money — payments

Contact — canonical_url, contact_page_url, emails, facebook_url, favicon_url, final_url, github_url, instagram_url, linkedin_url, phones, sitemap_url, tiktok_url, twitter_url, url, youtube_url

Counts and measures — count, hreflang_count, redirect_count, robots_disallow_count, script_count

Other detail — advertising, analytics, cache_control, caching_tech, categories, cdn, cms, content_length_bytes, detail, domain, ecommerce_platform, error, forms_tech, framework, h1, hosting, hsts, javascript_libraries, language, last_modified, marketing, media_tech, meta_description, meta_generator, meta_keywords, meta_robots, monitoring, og_image, privacy_tools, programming_language, redirect_chain, response_time_ms, robots_txt_found, search_tech, security_headers, security_tech, server, server_tech, support_tech, technologies, third_party_script_hosts, twitter_handle, ui_libraries, x_powered_by

Input example

{
  "urls": [
    "stripe.com",
    "shopify.com"
  ],
  "max_items": 2,
  "include_details": true
}

The default input is deliberately bounded and produces a small, useful Store test. max_items is a hard output ceiling.

Output example

{
  "url": "https://stripe.com",
  "final_url": "https://stripe.com",
  "status": 200,
  "domain": "shopify.com",
  "is_https": true,
  "redirect_count": 1,
  "redirect_chain": "https://shopify.com -> https://www.shopify.com/",
  "response_time_ms": 146,
  "technologies": [
    "Fastly",
    "Next.js"
  ],
  "detail": [
    {
      "name": "Cloudflare",
      "category": "cdn",
      "evidence": "header"
    },
    {
      "name": "Shopify",
      "category": "ecommerce",
      "evidence": "html"
    },
    {
      "name": "Tailwind CSS",
      "category": "ui",
      "evidence": "html"
    }
  ],
  "count": 2,
  "categories": [
    "cdn",
    "framework"
  ],
  "cms": "WordPress",
  "ecommerce_platform": "Shopify",
  "framework": "Next.js",
  "javascript_libraries": "jQuery",
  "ui_libraries": "Google Fonts",
  "analytics": "Google Tag Manager",
  "advertising": "Facebook Pixel",
  "marketing": "HubSpot, Klaviyo",
  "payments": "PayPal",
  "cdn": "Cloudflare",
  "hosting": "Netlify",
  "server_tech": "Nginx",
  "programming_language": "PHP",
  "security_tech": "reCAPTCHA",
  "support_tech": "Zendesk",
  "privacy_tools": "OneTrust"
}

44 further columns are omitted here for length — the full list is above, and every column appears in the export whether or not the source populated it.

Common use cases

• B2B lead qualification and segmentation
• Competitive technology research
• Migration and integration prospecting
• Portfolio and vendor inventory

Use with AI agents and MCP

Apify's MCP server can discover and call this Actor from an AI workflow. Example intent:

Identify the public web technologies detected on stripe.com and shopify.com.

Use the JSON from Input example as the tool arguments. The strict input schema rejects unsupported parameters, and the documented dataset schema tells the agent how to interpret each returned field.

Pricing and cost control

Output is billed per result at $0.003 per result (about $3.00 per 1,000 results), plus a $0.0005 Actor-start charge billed once per gigabyte of memory at run start. Use max_items to cap both output volume and charges. The price shown on the Apify Store listing is authoritative.

max_items limits both output volume and result-based charges. Start with 10 records, inspect them, and then scale deliberately. include_details adds up to two extra requests per site, so leave it off on long lists and turn it on when you want the sitemap and contact-page columns.

Reliability

The Actor validates input, bounds pagination, retries transient upstream failures, writes structured records, and fails explicitly when the source cannot produce usable output. A production default-input canary is monitored by the fleet.

Limitations and responsible use

• Detection is evidence of presence, not proof of absence.
• The signature database covers common technologies, not every product.
• Only the requested page is fetched and JavaScript is not executed.
• Version numbers and technologies visible only after interaction may be missed.
• Emails come from mailto: links plus plain-text addresses on the site's own domain, so an address printed only as an image, or only on a third-party domain, is not returned.
• Contact details belong to their owners. Use them in line with applicable marketing and privacy law.

Use the data lawfully, respect source terms, and independently validate records before making consequential decisions.

FAQ

Does it need my own API key?

No, the default workflow does not require a customer-supplied API key.

Can I export the results?

Yes. Download the default dataset as JSON, CSV, Excel, or XML, or retrieve it through the Apify API.

How do I control cost?

Set max_items to the most records you want returned. Begin with the bounded default input.

Can an AI agent call it?

Yes. The Actor has strict input and semantic output schemas and can be called through Apify's MCP tooling.

What does include_details do?

It fetches /robots.txt and one contact or about page per site, which fills robots_txt_found, sitemap_url, robots_disallow_count and contact_page_url, and usually adds emails and phone numbers the homepage does not print. It costs up to two extra requests per site and is off by default.

What happens when a source field is missing?

The relevant field is returned as null or an empty normalized value rather than being merged into another field.