# Website Technology Detector (`gifted_wagon/website-technology-detector`) Actor

Detect CMS, ecommerce, frameworks, analytics, CDNs, hosting, payments, and support tools with evidence, confidence, and safe URL validation.

- **URL**: https://apify.com/gifted\_wagon/website-technology-detector.md
- **Developed by:** [Michael Olmos](https://apify.com/gifted_wagon) (community)
- **Categories:** Developer tools, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.05 / 1,000 website analyzeds

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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Website Technology Detector

Detect observable website technologies from public HTML and response headers. Categories include CMS, ecommerce, web frameworks, analytics, tag managers, CDN, hosting, payments, support, monitoring, and web servers.

### Evidence, not black boxes

Every detection includes a category, confidence, and evidence source such as `html_signature` or a specific response header. Full response headers are excluded by default. Detection is best-effort: server-side or deliberately hidden technologies may not be observable.

The Actor blocks localhost, private IPs, private DNS answers, embedded credentials, and unsafe redirects. Provide `urls`, a deterministic `maxWebsites`, and timeout settings.

### Quick start

```json
{
  "urls": [
    "https://apify.com"
  ],
  "maxWebsites": 10,
  "timeoutSecs": 20,
  "includeHeaders": false
}
```

Run the public example first, then provide a bounded list of company websites. Keep `includeHeaders` off unless your downstream process truly needs the filtered header evidence.

### Output

Each website row contains canonical and final URLs, fetch status, title, detected technologies grouped by category, confidence, evidence, counts, and an explicit error when a public page cannot be analyzed. The run summary records successes, failures, detections, and budget status.

Useful workflows include sales qualification, market research, migration planning, integration compatibility checks, public technology inventories, and routing leads by CMS, ecommerce platform, analytics, or payments provider.

### API and automation

```bash
curl -X POST \
  "https://api.apify.com/v2/acts/gifted_wagon~website-technology-detector/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://apify.com"],"maxWebsites":1}'
```

In n8n or Make, map website URLs into bounded batches, filter detections by category and confidence, and retain evidence with every downstream record.

### Pricing

The primary `website-analyzed` event starts at **$0.0015 per successfully analyzed website**. Only successful rows are charged; failed websites and the `OUTPUT` summary are uncharged. A small Actor-start event covers startup.

### Responsible use

Use technology signals for lawful research, compatibility, sales qualification, and security inventory. Do not treat a detection as authorization to probe, exploit, or bypass a website.

### FAQ and limitations

- **Is detection guaranteed?** No. Server-side, proxied, removed, or deliberately hidden technologies may not be observable.
- **Does it scan for vulnerabilities?** No. It reads public HTML and response signals; it is not a penetration-testing tool.
- **Why include confidence and evidence?** They make every detection reviewable instead of presenting a black-box claim.
- **Can it access private networks?** No. Local and private destinations and unsafe redirects are blocked.

# Actor input Schema

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

Public HTTP(S) URLs. Private and local network targets are blocked.

## `maxWebsites` (type: `integer`):

Hard cap applied before fetching and charging.

## `timeoutSecs` (type: `integer`):

Maximum fetch time per website before an uncharged failure row is returned.

## `includeHeaders` (type: `boolean`):

Disabled by default to minimize unnecessary source metadata retention.

## Actor input object example

```json
{
  "urls": [
    "https://apify.com"
  ],
  "maxWebsites": 100,
  "timeoutSecs": 20,
  "includeHeaders": false
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

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

No description

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("gifted_wagon/website-technology-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("gifted_wagon/website-technology-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 '{}' |
apify call gifted_wagon/website-technology-detector --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,gifted_wagon/website-technology-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/hWOKBC8XXzf22AuVV/builds/tHJV7LY2RoeIURdZx/openapi.json