NexGenData Tech Stack Detector icon

NexGenData Tech Stack Detector

Detect web technologies (CMS, analytics, frameworks, CDN, etc.) on any URL — Wappalyzer-style

Detect

AI-generated

Summary

Detects web technologies (CMS, analytics, frameworks, CDN, payment processors, etc.) on one or more website URLs by running the NexGenData Tech Stack Detector actor on Apify synchronously and returning its dataset items.

Inputs

  • URLs (required) — List of website URLs to analyze. Bare hostnames like stripe.com are accepted (scheme is auto-added by the actor). Blank entries are trimmed and dropped.
  • Category Filter — Optional list of categories (e.g. CMS, Analytics, CDN, Ecommerce, JavaScript Frameworks, Payment Processors) to restrict detection. Empty means all categories; only sent when at least one is given.
  • Include Confidence Scores — Adds a 0–100 confidence score per detected technology (header match 100, script-src 90, HTML body 85, implied-only 60). Default true.
  • Extract Version Numbers — Attempts to parse versions from headers, script URLs, and HTML. Default true.
  • Additional Fields — Collection with HTTP Timeout per URL (3–60s, default 15, sent to the actor), Actor Memory in MB (default 1024), and Run Timeout in seconds (default 240; Apify caps sync runs at 300). Requires an Apify token in the NexGenData API credential.

Output shape

One output item per record returned by the actor's dataset, with the actor's result placed in json. Each item is paired to the input item that triggered it. Results are typically per-URL tech detections, but the exact fields come from the actor.

Runs once per input item. The call is synchronous, so it blocks until the actor finishes or times out. If Continue On Fail is enabled, a failed item yields {error: message} instead of throwing. Requires the nexGenDataApi credential with an Apify token.

Examples

Example 1: Enrich a list of lead company domains with their tech stack for sales qualification.

URLs set to an expression for the domain field (or several fixed domains), defaults for confidence and versions, no category filter.

Example 2: Find which sites use a particular ecommerce or payment platform.

URLs: shopexample.com; Category Filter: Ecommerce, Payment Processors; Include Confidence Scores on.

Example 3: Scan slow-loading sites without hitting run limits.

Additional Fields: HTTP Timeout 45, Run Timeout 290, Actor Memory 2048.

Links

Discussion