# Website Tech Stack Detector (`cyber1nj3ct0r/tech-stack-detector`) Actor

Find out what any website is built with: CMS, shop system, analytics, tag managers, JavaScript frameworks, web server, CDN, hosting, payment and marketing tools, with versions. Over 7,000 technologies. Paste a list of sites; get one row per site.

- **URL**: https://apify.com/cyber1nj3ct0r/tech-stack-detector.md
- **Developed by:** [Sanira Botheju](https://apify.com/cyber1nj3ct0r) (community)
- **Categories:** Developer tools, Lead generation, SEO tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.25 / 1,000 websites

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### What does Website Tech Stack Detector do?

It tells you what websites are built with. Paste a list of websites and get, for each one, the technologies it uses, recognised from more than 7,000 fingerprints:

- **CMS and shop systems**: WordPress, Shopify, Wix, Squarespace, Webflow, Ghost, WooCommerce, Magento and many more, with the version when the site shows it.
- **Analytics and marketing**: Google Analytics, Google Tag Manager, Hotjar, Mixpanel, HubSpot, Mailchimp, Meta and LinkedIn pixels.
- **Frameworks and languages**: React, Next.js, Vue.js, Angular, jQuery, Laravel, PHP, Node.js.
- **Servers, CDN and hosting**: Nginx, Apache, Cloudflare, Fastly, Amazon CloudFront, Vercel, AWS, GitHub Pages.
- **E-mail and DNS**: Google Workspace, Microsoft 365 and DNS hosts, read from the domain's DNS records.

Each website gives one row, with ready-made columns for the main categories, so a list of thousands of sites turns into a spreadsheet you can sort and filter.

### What data do you get?

| Field | What it holds |
|---|---|
| `technologyNames`, `technologyCount` | Every technology found, the most important categories first |
| `technologies` | Each technology with its `version`, `confidence` (0 to 100), `categories` and `website` |
| `cms`, `ecommerce`, `analytics`, `tagManagers` | Comma-separated names per category, empty when none was found |
| `javascriptFrameworks`, `webFrameworks`, `programmingLanguages` | The same for code |
| `webServers`, `cdn`, `hosting` | The same for servers and infrastructure |
| `paymentProcessors`, `marketingAutomation`, `advertising` | The same for business tools |
| `byCategory` | All technologies grouped by category name |
| `url`, `finalUrl`, `httpStatus`, `title` | The address, where it redirected, its status and the page title |

The run summary lists the technologies found on the most websites, handy for market research.

### How to find out what a website is built with

1. Paste the websites under **Websites**, one per line, or link a text file or a Google Sheet that lists them. `example.com` is enough.
2. Press **Start**.
3. Open the **Technologies** tab, or download the results as CSV, Excel or JSON.

### How much does it cost?

| Plan | Price |
|---|---|
| Free and Starter | $0.30 per 1,000 websites ($0.0003 each) |
| Scale | $0.27 per 1,000 websites |
| Business | $0.25 per 1,000 websites |

Checking 10,000 websites costs $3. An address that cannot be read counts as one website too. Apify's free plan gives $5 of credit each month, enough for about 16,000 websites. Set a maximum cost for the run, and the tool stops before it would go over it.

### Input

```json
{
    "urls": [
        { "url": "https://apify.com" },
        { "url": "crawlee.dev" }
    ],
    "checkDns": true,
    "includeDescriptions": false
}
```

### Output example

```json
{
    "url": "https://blog.apify.com",
    "httpStatus": 200,
    "title": "Apify Blog",
    "technologyCount": 21,
    "technologyNames": ["Ghost", "Zapier", "Node.js", "Varnish", "Bootstrap", "Nginx", "Google Workspace", "Google Tag Manager", "..."],
    "technologies": [
        { "name": "Ghost", "version": "6.71", "confidence": 100, "categories": ["CMS", "Blogs"], "website": "https://ghost.org" }
    ],
    "cms": "Ghost",
    "analytics": "Mixpanel",
    "tagManagers": "Google Tag Manager",
    "webServers": "Varnish, Nginx, OpenResty",
    "cdn": "jsDelivr",
    "marketingAutomation": "Mailgun, HubSpot, Google Workspace, Amazon SES",
    "checkedAt": "2026-10-18T01:12:40.000Z",
    "error": null
}
```

### What can you use it for?

- **Lead lists**: find shops on Shopify or WooCommerce, or sites without analytics, before you contact them.
- **Market research**: count which CMS, analytics or payment tools a list of companies uses.
- **Competitor research**: see what tools the leaders in your market run.
- **Agencies and freelancers**: check a prospect's site before a call, in bulk.
- **Security and IT**: find old versions of WordPress, jQuery or server software across many sites.

### Use it from the API

```bash
curl -X POST "https://api.apify.com/v2/acts/cyber1nj3ct0r~tech-stack-detector/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"urls": [{"url": "https://apify.com"}]}'
```

The same works from Python, JavaScript, Make, Zapier and n8n through Apify's integrations.

### FAQ

#### How does it recognise technologies?

It reads each website's page once, like a visitor's first request, and looks at the HTML, the addresses of its scripts, its inline scripts, meta tags, response headers and cookies, plus the domain's DNS records (MX, TXT, NS, SOA, CNAME). These are matched against the open-source fingerprints of the webappanalyzer project, which continues the open rules of Wappalyzer (GNU GPL v3.0). Versions come from the same places, for example a `generator` tag or a script's file name.

#### Why is a technology I know about missing?

The tool does not run the page's JavaScript (no browser, which keeps it fast and cheap), so the few technologies that can only be seen from inside a running page are missed, and so are tools that a page loads only after a click or consent. It looks at the address you give, usually the home page; a shop's checkout or a blog's article pages may show more. Confidence below 100 means the fingerprint is a hint rather than proof.

#### A site answers with HTTP 403 and shows only Cloudflare. Why?

Some sites put a firewall in front of every visitor they do not know. The tool says who it is in its User-Agent and does not get round such blocks; it then reports the technologies of the answer it got (often only the firewall) and the HTTP status.

#### Does it follow links or crawl a site?

No. One request per address, plus a few DNS lookups for its domain. Add the pages you want checked to the list.

#### Something does not work

Open an issue on the tool's **Issues** tab with the run's link. Issues are answered.

# Actor input Schema

## `urls` (type: `array`):

Home pages or any other pages, for example <code>https://www.example.com</code> or just <code>example.com</code>. Add them one by one, paste many at once with <b>Bulk edit</b>, or link a text file (or a Google Sheet published as CSV) that lists them. Each address is looked up once.

## `checkDns` (type: `boolean`):

Also read the domain's MX, TXT, NS, SOA and CNAME records, which show the e-mail provider, DNS host and verified services (for example Google Workspace, Microsoft 365, Cloudflare DNS).

## `includeDescriptions` (type: `boolean`):

Add a one-line description to each technology found. Off by default to keep the results short.

## `requestTimeoutSecs` (type: `integer`):

How long to wait for a website to answer.

## `userAgent` (type: `string`):

The name the tool sends with each request. Leave empty to use the tool's own name, which tells site owners what is visiting. Set your own only for sites you run or have permission to use.

## Actor input object example

```json
{
  "urls": [
    {
      "url": "https://apify.com"
    },
    {
      "url": "https://crawlee.dev"
    },
    {
      "url": "https://blog.apify.com"
    }
  ],
  "checkDns": true,
  "includeDescriptions": false,
  "requestTimeoutSecs": 30
}
```

# Actor output Schema

## `technologies` (type: `string`):

One record per website with every technology found, grouped by category.

## `summary` (type: `string`):

Counts for the run and the technologies found on the most websites.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urls": [
        {
            "url": "https://apify.com"
        },
        {
            "url": "https://crawlee.dev"
        },
        {
            "url": "https://blog.apify.com"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("cyber1nj3ct0r/tech-stack-detector").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "urls": [
        { "url": "https://apify.com" },
        { "url": "https://crawlee.dev" },
        { "url": "https://blog.apify.com" },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("cyber1nj3ct0r/tech-stack-detector").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urls": [
    {
      "url": "https://apify.com"
    },
    {
      "url": "https://crawlee.dev"
    },
    {
      "url": "https://blog.apify.com"
    }
  ]
}' |
apify call cyber1nj3ct0r/tech-stack-detector --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,cyber1nj3ct0r/tech-stack-detector"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Kc7rfMPD2TK13GCze/builds/4oM3HW6ce3hDkRdeJ/openapi.json