# Domain Enrichment — Industry, Tech Stack & Contacts ($10/1k) (`leadharbor/domain-enrichment`) Actor

Give it domains. Each comes back with the site's title and description, an industry, the tech stack, emails, phones and social links read from the public homepage. $10 per 1,000.

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

## Pricing

from $10.00 / 1,000 domain enricheds

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

## Domain Enrichment

Give it domains. For each one it reads the **public homepage** (and one contact page, if the homepage links to `/contact` or `/contact-us`) and returns the site's **title and description**, its **tech stack**, **emails**, **phone numbers**, **social links** and an **industry**.

It makes plain HTTP requests. No browser, no proxy, no login.

**Not live on Apify yet; planned price: $10 per 1,000 enriched domains ($0.010 each) plus $0.00005 per run start (not set anywhere live, as of 13 Oct 2026).** Domains that cannot be fetched are returned with an error and are **not charged**.

### Who it is for

- Sales and marketing teams who have a list of company domains and need a first layer of context (what the site says, what it runs on, where to reach it).
- AI agents and automations that need structured facts about a domain through one API call.
- Anyone sorting a domain list by platform, for example "which of these run on Shopify".

### What you get

| Field | What it is |
|---|---|
| `input` | The text you gave. |
| `domain` | The host that was fetched (lowercase, no `www.`). `null` if the input could not be read. |
| `finalUrl` | The homepage URL after redirects. |
| `httpStatus` | HTTP status of the homepage. |
| `title` | The page's `<title>`, as written by the site. `null` if absent. |
| `metaDescription` | The site's own `<meta name="description">`, or its `og:description` if there is no plain description. `null` if neither exists. Never written by AI. |
| `industry` | One industry from a fixed list of 26 (see below), picked by Jev from the title and description. `null` if Jev is unavailable or not confident enough. |
| `industryConfidence` | Jev's confidence (0.6 to 1) for the pick. `null` when `industry` is `null`. |
| `techStack` | Names detected by our own rules on response headers and homepage HTML (see below). |
| `emails` | Up to 5 addresses from `mailto:` links and visible text on the homepage and the contact page. Addresses on the site's own domain come first. Duplicates removed. |
| `phones` | Up to 3 numbers from `tel:` links only. Numbers written as plain text are not read. |
| `contactPageUrl` | The `/contact` or `/contact-us` page linked from the homepage. `null` if there is no such link. |
| `socials` | `linkedin`, `twitter`, `facebook`, `instagram`, `youtube`: the first profile link found for each, or `null`. |
| `enrichedAt` | ISO timestamp. |
| `error` | `null` on success, otherwise the reason (see Errors). |

#### Industry list

Software & SaaS, E-commerce & Retail, Marketing & Advertising Agency, Financial Services & Fintech, Healthcare & Medical, Education & E-learning, Real Estate & Property, Travel, Hospitality & Restaurants, Manufacturing & Industrial, Construction & Engineering, Legal & Professional Services, Consulting & Business Services, Media, News & Publishing, Entertainment & Gaming, Telecommunications & Internet Infrastructure, Transportation & Logistics, Energy & Utilities, Non-profit & Community, Government & Public Sector, Automotive, Food & Beverage Production, Beauty, Fashion & Lifestyle, Sports, Fitness & Wellness, Agriculture, Personal Blog or Portfolio, Other.

#### Tech stack names

Shopify, WordPress, WooCommerce, Wix, Squarespace, Webflow, HubSpot, Google Analytics, Google Tag Manager, Stripe, Cloudflare, Next.js, React, Intercom, Mailchimp, Vercel, Netlify. These come from rules we wrote ourselves (a script URL, a header, a page marker). A tool that is loaded only after the page runs JavaScript is not seen, and a tool not on this list is not reported.

### Input

| Field | What it does |
|---|---|
| `domains` | Domains or URLs, one per line. Only the domain part is used. Duplicates are removed. Required. |
| `maxItems` | Process only the first N unique inputs. Default 100, maximum 2,000. |

Example input:

```json
{ "domains": ["stripe.com", "shopify.com", "notion.so"] }
```

### Example output

Real output from running this Actor locally on the three prefilled domains on 5 Oct 2026 (no Jev key was set locally, so `industry` is `null` here). Input `shopify.com`:

```json
{
  "input": "shopify.com",
  "domain": "shopify.com",
  "finalUrl": "https://www.shopify.com/",
  "httpStatus": 200,
  "title": "Shopify: The All-in-One Commerce Platform for Businesses - Shopify",
  "metaDescription": "Try Shopify free. Build or grow your business fast with AI. Get more than ecommerce software with tools to manage every part of your business.",
  "industry": null,
  "industryConfidence": null,
  "techStack": [
    "Shopify",
    "Cloudflare"
  ],
  "emails": [],
  "phones": [],
  "contactPageUrl": null,
  "socials": {
    "linkedin": "https://www.linkedin.com/company/shopify",
    "twitter": "https://twitter.com/shopify",
    "facebook": "https://www.facebook.com/shopify",
    "instagram": "https://www.instagram.com/shopify",
    "youtube": "https://www.youtube.com/user/shopify"
  },
  "enrichedAt": "2026-10-05T19:18:33.763Z",
  "error": null
}
```

The other two prefilled domains in the same run:

| Domain | finalUrl | Title | techStack | emails / phones / socials |
|---|---|---|---|---|
| stripe.com | `https://stripe.com/` | Stripe | Financial Infrastructure to Grow Your Revenue | Next.js, React | none found in the page HTML |
| notion.so | `https://www.notion.com/` | The AI workspace that works for you. | Notion | Cloudflare, Next.js, React | none found in the page HTML |

Empty contact fields are normal for big sites: their homepages often load links with JavaScript, which this Actor does not run. For comparison, a separate local run on `gnu.org` returned `contactPageUrl: "https://www.gnu.org/contact/"` and these emails: `gnu@gnu.org`, `webmasters@gnu.org`, `web-translators@gnu.org`, `maintainers@gnu.org`, `sysadmin@gnu.org`.

### Pricing

- **$0.010 per enriched domain.** Charged only when the homepage answers HTTP 200-399 and is read as HTML.
- **$0.00005 per run start.**
- Failed fetches, pages blocked by robots.txt and unreadable inputs are returned with an `error` and are **free**.

### Errors

A failed row has `error` set and every data field empty. These are the exact messages:

| `error` | Meaning |
|---|---|
| `Invalid domain: could not read a valid host from this input.` | The text is not a domain or URL. |
| `Blocked: private, loopback or local address.` | `localhost`, a private or local IP, or a name that resolves to one. These are never fetched. |
| `IP addresses are not supported; give a domain name.` | A public IP address was given instead of a domain. |
| `blocked by robots.txt` | The site's robots.txt disallows the homepage for this crawler. |
| `Domain does not resolve.` | DNS has no address for the domain. |
| `Could not connect (CODE).` | The connection or TLS handshake failed, for example `ECONNREFUSED` or `ETIMEDOUT`. |
| `Request timed out after 10s.` | No complete answer within 10 seconds. |
| `Too many redirects (more than 5).` | The redirect chain was longer than 5. |
| `Redirected to a non-standard port.` / `Redirected to an unsupported protocol.` / `Redirect to an invalid URL.` | A redirect pointed somewhere this Actor does not follow. |
| `Site returned HTTP 404.` | The homepage answered with an error status (the real status code is in the message and in `httpStatus`). |
| `Page is not HTML (content-type: ...).` | The homepage is not an HTML document. |
| `Enrichment failed: ...` | An unexpected error for this domain. The run continues with the others. |

### How it fetches

- Tries `https://domain/`, then `http://domain/`, then `https://www.domain/`.
- Honest user agent: `leadharbor-domain-enrichment/1.0 (+https://apify.com/leadharbor)`.
- 10 second limit per page, at most 5 redirects, at most 1.5 MB read per page. 10 domains at a time.
- Checks `robots.txt` before fetching the homepage and the contact page. If robots.txt cannot be read (missing or an error), the fetch goes ahead.
- Every address a name resolves to is checked before connecting, and every redirect is re-checked, so private and local addresses are never reached.
- Public, logged-out pages only. No cookies, no accounts.

### Use it from code

```bash
curl -X POST "https://api.apify.com/v2/acts/leadharbor~domain-enrichment/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"domains":["stripe.com","shopify.com"]}'
```

Python, with the [apify-client](https://pypi.org/project/apify-client/) package:

```python
from apify_client import ApifyClient

client = ApifyClient("YOUR_TOKEN")
run = client.actor("leadharbor/domain-enrichment").call(
    run_input={"domains": ["stripe.com", "shopify.com"]}
)
for row in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(row["domain"], row["industry"], row["techStack"], row["emails"], row["error"])
```

### FAQ

**Does it return employee count or revenue?**
No. Neither can be read from a website over HTTP, so there is no such field.

**Does it run JavaScript or use a browser?**
No. It reads the HTML the server sends. Content added later by JavaScript (many modern homepages build their menus and footers that way) is not seen, so `emails`, `phones` and `socials` can be empty and a tool loaded by script may be missing from `techStack`.

**Who writes `metaDescription`?**
The site does. It is copied from the page, and is `null` if the page has none. Nothing is generated.

**How is `industry` decided?**
By Jev, a classification API, which picks one option from the fixed list above using only the page title and description. It is `null` when there is no title or description, when the answer is not confident enough (below 0.6), or when the service does not answer. A `null` industry does not stop the run and does not change the price.

**Are phone numbers read from the page text?**
No. Only `tel:` links, so a number is returned only when the site marks it up as a phone link.

**Does it check that an email works?**
No. The emails are addresses found on the page. They are not checked for mailbox validity. To screen them, use the Bulk Email Verifier below.

**Why was my domain blocked by robots.txt?**
The site's robots.txt disallows the homepage for this crawler. The Actor respects it and does not fetch the page. You are not charged.

**Am I charged for failures?**
No. Only domains that answered HTTP 200-399 and were read as HTML are charged.

**How many domains per run?**
Up to 2,000 (`maxItems`). Split larger lists into several runs.

### Limits

- Homepage plus at most one contact page per domain.
- At most 5 emails, 3 phones and 5 social links per domain.
- Pages are read up to 1.5 MB.
- HTML only, as served. No JavaScript rendering.
- Only the first 2,000 unique inputs of a run are processed.

### Related actors

- [Domain Trust Check](https://apify.com/leadharbor/domain-trust-check): trust score, domain age, SSL and email DNS for each domain.
- [Website Contact Extractor](https://apify.com/leadharbor/website-contact-extractor): find emails and phones across business websites.
- [Google Maps Scraper, MX-Checked Business Email Leads](https://apify.com/leadharbor/google-maps-verified-email-scraper): business leads with emails from Google Maps.
- [Disposable Email & Domain Checker](https://apify.com/leadharbor/disposable-email-checker): list-only throwaway check.
- [Bulk Email Verifier](https://apify.com/leadharbor/bulk-email-verifier): MX, SPF, DMARC and a score for each email address.

# Actor input Schema

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

One domain per line, e.g. stripe.com. A full URL also works; only the domain part is used. Duplicates are removed.

## `maxItems` (type: `integer`):

Only the first N unique domains are processed (1-2,000).

## Actor input object example

```json
{
  "domains": [
    "stripe.com",
    "shopify.com",
    "notion.so"
  ],
  "maxItems": 100
}
```

# Actor output Schema

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

One row per domain: title, description, industry, tech stack, emails, phones and social links.

## `resultsUi` (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 = {
    "domains": [
        "stripe.com",
        "shopify.com",
        "notion.so"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leadharbor/domain-enrichment").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": [
        "stripe.com",
        "shopify.com",
        "notion.so",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("leadharbor/domain-enrichment").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": [
    "stripe.com",
    "shopify.com",
    "notion.so"
  ]
}' |
apify call leadharbor/domain-enrichment --silent --output-dataset

```

## MCP server setup

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

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/P1kc0FNCdA0ZNoZLm/builds/feI2OKf9VwpplxFjk/openapi.json