# Domain Intel: tech stack, CMS, contacts, socials & sitemap (`alexisv/domain-intel`) Actor

Dado un dominio devuelve CMS, tecnologías, redes sociales, datos de contacto públicos y un mapa del sitio. Pensado para agentes de IA.

- **URL**: https://apify.com/alexisv/domain-intel.md
- **Developed by:** [Alexis Toledo Ruiz](https://apify.com/alexisv) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 domain diggers

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## Website Tech Stack & CMS Detector: contacts, socials and sitemap

Give it a list of domains and get one structured profile per website. No proxies to set up, no browser to maintain, JSON out.

### What you get for each domain

- **What the site is**: type (online store, blog or content site, SaaS, local business...), description, main menu sections and topics.
- **CMS and technologies**: WordPress, Shopify, Wix, Webflow, Next.js, React, Nginx, Cloudflare and about 100 more, each with a confidence level and the evidence found.
- **WordPress details**: active theme and visible plugins, with versions when the site exposes them.
- **Third-party services**: analytics, advertising pixels, tag managers, chat, payments, CDNs and consent tools.
- **Privacy signals**: whether a cookie banner or consent tool is detected, and links to privacy, cookies, terms and legal pages.
- **Public contact data**: emails, phone numbers, organization data (JSON-LD) and social profiles.
- **Site map**: pages found through robots.txt, sitemaps and internal links, grouped by section.

### Use cases

- **Lead generation and prospecting**: analyze a list of sites and filter by platform or tools (for example Shopify stores using Klaviyo), with a public contact when available.
- **Agencies and freelancers**: audit a prospect's stack before the first call.
- **Competitive research**: see which tools and platforms competitors use.
- **AI agents**: call it from an agent through the Apify MCP server to enrich a domain with structured data.

### Input

| Field | Description |
|---|---|
| `domains` | Domains or URLs to analyze, for example `example.com`. |
| `includeSitemap` | Discover pages via robots.txt, sitemaps and internal links. Default `true`. |
| `maxSitemapUrls` | Maximum URLs collected per domain. Default `500`. |
| `contactPages` | Extra contact, legal or about pages to visit. Default `2`. |

### Example output

```json
{
  "input": "example.com",
  "url": "https://example.com/",
  "summary": { "type": "Online store", "about": "...", "sections": ["..."], "topics": ["..."] },
  "cms": ["Shopify"],
  "technologies": [{ "name": "Shopify", "category": "E-commerce", "confidence": "high", "evidence": ["..."] }],
  "wordpress": null,
  "thirdParties": { "trackers": 3, "byCategory": { "Analytics": ["Google Analytics"] } },
  "privacy": { "cookieBanner": true, "consentTool": "OneTrust", "legalPages": { "privacy": "..." } },
  "contacts": { "emails": ["..."], "phones": ["..."] },
  "socials": { "instagram": ["..."] },
  "sitemap": { "totalUrls": 250, "tree": {} }
}
```

### Pricing

Pay per event: one `domain-analyzed` event per domain analyzed successfully. Domains that fail are not charged.

### Limitations

- Only **publicly available** information is collected. Pages with no public link or sitemap entry cannot be discovered.
- Detection reads the HTML served without running JavaScript. Services loaded later (for example after accepting cookies) may not appear, and single-page apps may show fewer technologies than a browser would.
- The site summary is heuristic (metadata, headings and menu). It does not use AI and is approximate.
- The privacy section is a shallow automatic check, not legal advice.
- Sites behind strict bot protection may return partial data.

### Responsible use

Respect each site's terms of use and applicable data protection law (such as GDPR) when using contact data.

# Actor input Schema

## `domains` (type: `array`):

Lista de dominios a analizar (ej. example.com).

## `includeSitemap` (type: `boolean`):

Descubre páginas vía robots.txt, sitemaps y enlaces internos.

## `maxSitemapUrls` (type: `integer`):

Límite de URLs recogidas por dominio.

## `contactPages` (type: `integer`):

Cuántas páginas de contacto/legal/nosotros visitar además de la home.

## Actor input object example

```json
{
  "domains": [
    "example.com"
  ],
  "includeSitemap": true,
  "maxSitemapUrls": 500,
  "contactPages": 2
}
```

# Actor output Schema

## `results` (type: `string`):

Tabla resumen con un resultado por dominio analizado.

# 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 = {
    "domains": [
        "example.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("alexisv/domain-intel").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 = { "domains": ["example.com"] }

# Run the Actor and wait for it to finish
run = client.actor("alexisv/domain-intel").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 '{
  "domains": [
    "example.com"
  ]
}' |
apify call alexisv/domain-intel --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,alexisv/domain-intel"
        }
    }
}
```

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/EsUHIQbFBj7XtTyHt/builds/CafxUz82fO6ocuUBN/openapi.json