# Website Tech Fingerprint (`ib4ngz/website-tech-fingerprint`) Actor

Detect technologies across multiple websites with confidence scores, versions, and evidence.

- **URL**: https://apify.com/ib4ngz/website-tech-fingerprint.md
- **Developed by:** [Iqbal R](https://apify.com/ib4ngz) (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 $3.50 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
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

### What does Website Tech Fingerprint do?

**Website Tech Fingerprint identifies the technologies used by multiple websites in one run.** For every submitted URL, it returns detected platforms, frameworks, analytics tools, hosting providers, web servers, and other technologies with confidence scores, available version information, and supporting evidence.

Use it from Apify Console without writing code, or connect it to your workflow through the Apify API, schedules, webhooks, and integrations. You can try it with any public website, such as [apify.com](https://apify.com).

### Why use Website Tech Fingerprint?

Website technology data can support:

- Lead enrichment and sales qualification
- Competitor and market research
- Website migration planning
- Portfolio and vendor audits
- Agency prospecting
- Technology adoption analysis
- Automated Website Intelligence workflows

Batch input lets you analyze multiple domains in one run. Each website receives its own result, so a failed or unreachable URL does not prevent results for other websites.

### How to use Website Tech Fingerprint

1. Open the Actor and go to the **Input** tab.
2. Add one or more website URLs.
3. Choose whether to detect versions and include evidence.
4. Adjust the timeout or concurrency only when needed.
5. Click **Start**.
6. Open the **Output** tab to review or download the results.

The Actor produces one dataset item per unique URL.

### Input

Example input for multiple websites:

```json
{
    "startUrls": [{ "url": "https://apify.com" }, { "url": "https://wordpress.org" }, { "url": "https://shopify.com" }],
    "detectVersions": true,
    "includeEvidence": true,
    "timeoutMs": 30000,
    "maxConcurrency": 3,
    "maxRequestRetries": 2,
    "proxyConfiguration": {
        "useApifyProxy": false
    }
}
```

| Field                | Description                                             | Default             |
| -------------------- | ------------------------------------------------------- | ------------------- |
| `startUrls`          | One or more website URLs                                | `https://apify.com` |
| `detectVersions`     | Return versions when they are explicitly available      | `true`              |
| `includeEvidence`    | Include the reason each technology was identified       | `true`              |
| `timeoutMs`          | Maximum loading time per website                        | `30000`             |
| `maxConcurrency`     | Websites analyzed at the same time, from 1 to 20        | `3`                 |
| `maxRequestRetries`  | Additional attempts after a failed request, from 0 to 5 | `2`                 |
| `proxyConfiguration` | Optional Apify Proxy or custom proxy configuration      | Disabled            |

### Output

Each requested website creates a separate dataset item:

```json
{
    "success": true,
    "url": "https://apify.com/",
    "finalUrl": "https://apify.com/",
    "statusCode": 200,
    "scanMode": "browser",
    "technologies": [
        {
            "name": "Next.js",
            "slug": "next-js",
            "category": "frontend-framework",
            "version": null,
            "confidence": 99,
            "evidence": [
                {
                    "type": "html",
                    "value": "/_next/static/"
                }
            ]
        }
    ],
    "summary": {
        "technologyCount": 1,
        "categories": ["frontend-framework"]
    },
    "timing": {
        "durationMs": 1234
    }
}
```

Failed websites return `success: false` with a clear error code and safe message. Results can be downloaded in JSON, CSV, Excel, XML, HTML, and other formats supported by Apify.

### Data table

| Field          | Description                                                               |
| -------------- | ------------------------------------------------------------------------- |
| `success`      | Whether the website was analyzed successfully                             |
| `url`          | Normalized requested URL                                                  |
| `finalUrl`     | Destination after redirects                                               |
| `statusCode`   | Main page HTTP status                                                     |
| `technologies` | Technology names, categories, versions, confidence, and optional evidence |
| `summary`      | Number of technologies and detected categories                            |
| `timing`       | Processing time for the website                                           |
| `error`        | Error details for unsuccessful websites                                   |

### Supported website technologies

Current coverage includes WordPress, WooCommerce, Shopify, React, Next.js, Vue.js, Nuxt, jQuery, Bootstrap, Tailwind CSS, Google Analytics, Google Tag Manager, Meta Pixel, Cloudflare, Vercel, Netlify, nginx, Apache, and PHP.

Supported categories include CMS, ecommerce, frontend frameworks, JavaScript libraries, CSS frameworks, analytics, tag managers, CDN, hosting, web servers, and runtimes.

### Confidence scores and evidence

Only detections with confidence of at least 50 are returned. Higher scores indicate stronger or multiple supporting indicators:

- **90–100:** confirmed or very strong detection
- **75–89:** high confidence
- **50–74:** probable

Versions are returned only when the website exposes a recognizable version. The Actor does not guess missing versions. Set `includeEvidence` to `false` when you need smaller result files.

### How much does it cost to analyze website technologies?

Cost depends mainly on the number of URLs, website loading time, and page complexity. Start with a small batch to estimate usage for your target websites. Lower concurrency can reduce peak memory usage, while a shorter timeout can prevent slow websites from consuming unnecessary resources.

You can use any platform credits included with your Apify plan. See the run detail page for exact compute usage.

### Tips for reliable results

- Submit the homepage or the most representative page of each website.
- Use complete HTTPS URLs when possible.
- Keep evidence enabled when reviewing detection quality.
- Increase the timeout for slow or heavily protected websites.
- Enable proxy rotation when websites restrict requests from shared data-center IPs.
- Reduce concurrency when analyzing resource-intensive websites.
- Run scheduled scans to monitor technology changes over time.

### FAQ, disclaimers, and support

#### Why was a technology not detected?

Some websites hide version information, load tools only after consent, restrict automated access, or expose different content by region. A missing detection does not prove that a technology is absent.

#### Is website technology detection always exact?

No. Results are evidence-based estimates and should be reviewed before making critical business or security decisions.

#### Is it legal to analyze websites?

Technology fingerprinting is commonly used for research and operational purposes, but you are responsible for complying with applicable laws, website terms, and access restrictions.

For bug reports, missing technologies, or feature requests, use the Actor's **Issues** tab. Custom coverage and Website Intelligence solutions are also available for specialized projects.

# Actor input Schema

## `startUrls` (type: `array`):

Add one or more website URLs to analyze. Each URL produces one dataset item.

## `detectVersions` (type: `boolean`):

Extract explicitly exposed technology versions when possible.

## `includeEvidence` (type: `boolean`):

Include the matched headers, assets, markup, globals, and requests in results.

## `timeoutMs` (type: `integer`):

Maximum loading time for each website, in milliseconds.

## `maxConcurrency` (type: `integer`):

Number of websites analyzed at the same time. Lower this if target sites are resource-intensive.

## `maxRequestRetries` (type: `integer`):

Number of additional attempts when a website request fails.

## `proxyConfiguration` (type: `object`):

Optional proxy settings for improved access and IP rotation. Apify Proxy usage may require a paid plan.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://apify.com"
    }
  ],
  "detectVersions": true,
  "includeEvidence": true,
  "timeoutMs": 30000,
  "maxConcurrency": 3,
  "maxRequestRetries": 2,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `results` (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 = {
    "startUrls": [
        {
            "url": "https://apify.com"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ib4ngz/website-tech-fingerprint").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 = { "startUrls": [{ "url": "https://apify.com" }] }

# Run the Actor and wait for it to finish
run = client.actor("ib4ngz/website-tech-fingerprint").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 '{
  "startUrls": [
    {
      "url": "https://apify.com"
    }
  ]
}' |
apify call ib4ngz/website-tech-fingerprint --silent --output-dataset

```

## MCP server setup

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

```

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/8gWLzh4J4lgL2oRLg/builds/yZOC2nzDHageJ0NFN/openapi.json