Tech Stack Detector: $0.40 per 1,000 Websites avatar

Tech Stack Detector: $0.40 per 1,000 Websites

Pricing

from $0.40 / 1,000 websites

Go to Apify Store
Tech Stack Detector: $0.40 per 1,000 Websites

Tech Stack Detector: $0.40 per 1,000 Websites

Detect website technologies from public pages and DNS. Get evidence, confidence, visible versions, CMS, commerce, analytics, payment tools, hosting, email providers and social links. One row per domain; blocked and unreachable sites return free notes. $0.40 per 1,000 websites.

Pricing

from $0.40 / 1,000 websites

Rating

0.0

(0)

Developer

Zaiq

Zaiq

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Features

Limited permissions

Share

Website Technology Detector: CMS, Analytics & Tech Stack

Get a technology stack with evidence for each website. $0.0004 per website with detected technologies — $0.40 per 1,000, the same price on every Apify plan. Blocked, unreachable, parked and unrecognized websites return free notes. Apify adds a $0.00005 start charge per run.

Paste a domain into urls, for example {"urls":["example.com"]}. The first output column gives a one-line verdict. Expand the row to see technologies, categories, visible versions, confidence, the exact signal matched, and where that signal was found.

Check CMS and commerce platforms, JavaScript frameworks, analytics, advertising tags, payment tools, CDNs, visible hosting signals and email providers. The Actor reads public HTML, response headers, cookie names and DNS. It uses more than 6,000 static technology definitions; it does not execute JavaScript or claim to detect every installed tool.

What you get

FieldWhat it holds
verdict, statusA short result first, followed by an explicit status such as ok, partial, blocked or parked.
technologiesTechnology names and categories, visible version or null, confidence score, observed/inferred label, and up to three matched signals with source URLs.
Stack columnscms, ecommerce, frameworks, analytics, adsPixels, payments, cdn, hosting, dnsProvider, emailProvider and emailDelivery.
dnsPublic MX, SPF TXT, NS and CNAME observations with resolver and query status. Mailbox providers come from MX; sending services come from SPF.
socialLinksPublic profile links present on the pages read. Sharing buttons and login links are excluded.
pages, coverage, notesURLs actually read, HTTP status, route, truncation and gaps. A missing technology means it was not detected in this material.
resultId, checkedAtStable domain identity within the run and the time of inspection. Already-delivered rows are skipped on restart.
SUMMARYResults and failures, request counts, traffic, route escalations, timing and charged events.

What people use it for

  • Enrich a domain list: Add technology columns to public company websites for research and segmentation.
  • Plan integrations: Check public evidence of a CMS, commerce platform or payment tool before choosing an integration approach.
  • Track a migration: Schedule repeat runs and compare the resulting technology rows in your own workflow.
  • Review detection evidence: Inspect the actual header, asset path or DNS record behind a result instead of accepting an unexplained label.

How to use it

  1. Enter one or more public websites in Website URLs or domains. Leaving the field empty checks example.com.
  2. Keep one page per website for a quick lookup. Use up to three pages to read more of the same website.
  3. Set Maximum cost per run, then click Start. Open Website technologies for the overview or Evidence and coverage for detail.
  4. Export JSON for nested evidence, or CSV/Excel for the summary columns.

Input

FieldExampleNotes
urls["example.com"]Up to 10,000 domains or HTTP(S) URLs. Exact hostname duplicates and www aliases are combined; other subdomains can have different stacks.
maxPages1From 1 to 3 linked public pages per website. DNS and robots requests are separate.
includeDnstrueRead MX, SPF TXT, NS and CNAME records. Public DNS answers, including errors, are cached within the run.
respectRobotstrueFollow readable robots.txt rules, including on redirect destinations.
probePathsfalseOptionally read a manifest and an already-detected CMS public index. No forms or administrative pages are submitted.
allowProxyFallbacktrueOn Apify, try datacenter and fresh residential routes after a refused or empty response. The price stays the same. Residential recovery reads a small initial fragment and can miss later signals.
concurrency6Maximum of 1–8 websites at once. The active limit drops as large DNS caches grow. Requests within a website are sequential.
siteTimeoutSeconds45From 10 to 120 seconds per website. Partial evidence is returned when the allowance is used.

Output

Each result is one row in the run's dataset (download it as JSON, CSV, Excel, XML or HTML, or read it through the API). An example row (values shortened):

{
"verdict": "3 technologies detected",
"domain": "example.com",
"status": "ok",
"technologyCount": 3,
"technologies": [
{
"name": "CDN provider",
"category": "CDN",
"categories": [
"CDN"
],
"version": null,
"confidence": 100,
"detection": "observed",
"evidence": [
{
"type": "headers",
"key": "server",
"match": "cdn-provider",
"sourceUrl": "https://example.com/",
"ruleSource": "community"
}
]
},
{
"name": "DNS provider",
"category": "DNS",
"categories": [
"DNS"
],
"version": null,
"confidence": 100,
"detection": "observed",
"evidence": [
{
"type": "dns",
"key": "NS",
"match": ".ns.provider.example",
"sourceUrl": "dns:example.com",
"ruleSource": "community"
}
]
},
{
"name": "HTTP/3",
"category": "Miscellaneous",
"categories": [
"Miscellaneous"
],
"version": null,
"confidence": 100,
"detection": "observed",
"evidence": [
{
"type": "headers",
"key": "alt-svc",
"match": "h3",
"sourceUrl": "https://example.com/",
"ruleSource": "community"
}
]
}
],
"coverage": {
"pagesRequested": 1,
"pagesScanned": 1,
"htmlTruncated": false,
"javascriptExecuted": false,
"externalScriptsDownloaded": false,
"dnsRequested": true,
"dnsComplete": true,
"staticOnly": true,
"absenceMeans": "Not detected in the public material fetched; not proof of absence."
}
}

This shortened example comes from a real direct-connection run on 25 October 2026. Names and vendor identifiers have been replaced with neutral labels, and source addresses use example domains; the counts, confidence scores, status and coverage are retained. No example company copy is included. The run’s key-value store contains a SUMMARY record with traffic, coverage, failures and charges.

Pricing

  • $0.0004 per website with detected technologies, including a useful result with partial coverage. Direct and recovered results have the same price on every Apify plan.
  • Blocked, unreachable, parked, invalid and no-technology results are free. Retries, additional pages within the selected limit, DNS lookups and failure notes have no separate event charge.
  • Apify’s $0.00005 start charge counts towards the buyer’s Maximum cost per run.
  • No AI step or separate model charge.
  • Launch price. It may rise later; Apify emails every user 14 days before any price increase takes effect, and a rise can happen at most once a month.

What typical jobs cost at the list price:

JobCost
1 successful website$0.00045 including the start charge
100 successful websites$0.04005 including the start charge
1,000 successful websites$0.40 including the start charge
100 inputs, 80 successful and 20 free notes$0.03205 including the start charge

Set Maximum cost per run to at least $0.00045 for one successful website, including the start charge. The Actor checks the remaining allowance before starting work and returns free notes for inputs it cannot inspect within that limit.

Tips

  • Use one page first; add pages when you need evidence beyond the landing page.
  • Filter on observed technologies when you need direct evidence. Inferred dependencies are labelled separately.
  • Treat a DNS provider as a DNS provider: nameservers alone do not establish where a website is hosted.
  • Check partial-coverage notes before comparing two runs. Consent prompts, region, hidden scripts and site changes can affect results.

Use it through the API

Python

from apify_client import ApifyClient
client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("zaiq/tech-stack-detector").call(run_input={"urls": ["example.com"], "maxPages": 1})
for row in client.dataset(run.default_dataset_id).iterate_items():
print(row)

JavaScript

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('zaiq/tech-stack-detector').call({"urls": ["example.com"], "maxPages": 1});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

HTTP (one call, results back)

curl -X POST 'https://api.apify.com/v2/acts/zaiq~tech-stack-detector/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>' \
-H 'Content-Type: application/json' \
-d '{"urls": ["example.com"], "maxPages": 1}'

Integrations and schedules

  • Schedules: run it every hour, day or week from the Apify Console (Schedules) and keep a history of results.
  • Make, Zapier, n8n, Google Sheets, Slack, Airtable: connect it through Apify's integrations, or send each finished run to a webhook.
  • Datasets: results stay in the run's dataset; export them or read them by API whenever you need them.

Use it with AI agents (MCP)

Add Apify's MCP server with this Actor already pinned (https://mcp.apify.com?tools=zaiq/tech-stack-detector) to Claude, ChatGPT, Cursor, VS Code or any MCP client. The agent can find this Actor and run it for you: ask it for "check the technology stack for these public website domains and show the evidence". AI agents can also pay for runs directly through Apify's agentic payments.

Limits

  • Static public signals only. No browser rendering, logged-in data, private APIs, CAPTCHA solving or hidden server inventory.
  • An observed asset or tag establishes a public signal, not an active subscription or proof that a service processes transactions. Confidence is a fingerprint score, not a calibrated probability.
  • Only versions present in matched public signals are returned. Unknown versions are null. Dependency inferences are explicitly marked.
  • Direct pages have a 12 MB decoded-body limit and a 16 MB site allowance. Residential recovery has a much smaller traffic allowance and returns partial coverage when it can provide evidence.
  • Robots restrictions and rate limits can end an inspection. The Actor stops requesting a website after a 429 response and does not rotate around it.
  • At most 150 HTTP requests reach one website across a run, including shared redirects. Inputs converging on the same website can therefore receive a budget note.
  • No automatic comparison or historical database is included. Schedule runs and compare their saved rows in your own system.
  • Fingerprint data includes the GPL-3.0 community definitions from enthec/webappanalyzer. Source attribution and the retained license are included with the Actor.

FAQ

What is charged?

One event for each website with detected technologies. A partial result with evidence is charged. A blocked page, parked domain, unreachable address or page with no supported detections is a free note.

Is this a website security scanner?

No. It reads public technology signals and does not test vulnerabilities, submit forms or probe administrative pages.

Why can a technology be missing?

Some services appear only after JavaScript executes, after consent, on a different page or to a different visitor. An empty category is not proof of absence.

Does an email provider mean a contact address was found?

No. MX records identify mail routing providers; SPF identifies sending services. This Actor does not extract personal email addresses.

Does a restart charge the same website twice?

Already-delivered domain keys are read from the dataset and skipped on restart. A new, separate run performs a new lookup.

Can the output be used without AI?

Yes. Detection is deterministic fingerprint matching with evidence and requires no AI key.

What happens to malformed inputs?

They produce free notes. One malformed input or inaccessible website does not stop the rest of the list.

Support

Questions, a site that changed, or a field you need? Open an issue on this Actor's Issues tab: we answer there, usually within a day.


Also found as: website technology detector, tech stack detector, website technology lookup, CMS detector, bulk domain enrichment, website technology API.