# Company Enrichment - domain to company profile (`sbr35/company-enrichment`) Actor

Input: a domain such as stripe.com. Output: company name, description, domain age, registrar, DNS and email provider, technology stack, hiring platform and social handles. Use when you have a website and need to know what the company is and what it runs on.

- **URL**: https://apify.com/sbr35/company-enrichment.md
- **Developed by:** [Alexandre de La Fayette](https://apify.com/sbr35) (community)
- **Categories:** Business, Lead generation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 company profiles

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?

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

## Company Enrichment

Give it a domain. Get back a company profile assembled from public records.

No API keys, no logins, no personal data. Every field comes from somewhere anyone can look:
domain registration records, DNS, the company's own public homepage, and public certificate logs.

### What you get

One row per domain:

**Identity**

| Field | Description |
|---|---|
| `domain` | Normalised domain (protocol and `www.` stripped) |
| `companyName` | Company name from site metadata |
| `description` | Meta or OpenGraph description |
| `title` | Page title |
| `language` | Declared page language |

**Registration** — from RDAP, the public successor to WHOIS

| Field | Description |
|---|---|
| `registrar` | Who the domain is registered through |
| `registeredAt` / `expiresAt` | Registration dates |
| `domainAgeYears` | Age in years — a useful proxy for company maturity |
| `status` | Domain status codes |

**Infrastructure** — from DNS

| Field | Description |
|---|---|
| `mailProvider` | Google Workspace, Microsoft 365, Zoho, Proton, Mimecast, Fastmail, Amazon SES |
| `nameserverProvider` | Cloudflare, AWS Route 53, Azure, Google |
| `mx` / `ns` / `ipv4` | Raw records |
| `hasSPF` / `hasDMARC` | Email authentication posture |

**Technology and presence** — from the public homepage

| Field | Description |
|---|---|
| `technologies` | Detected stack: WordPress, Shopify, Next.js, HubSpot, Segment, Intercom, Stripe and more |
| `socials` | LinkedIn, X, GitHub, YouTube handles found on the page |
| `atsPlatform` / `atsSlug` | Which hiring system they use, and their slug |
| `careersLinkInHtml` / `pricingLinkInHtml` | Whether those links appear in the static HTML |

### Input

```json
{
  "domains": ["stripe.com", "notion.so", "figma.com"],
  "includeHomepage": true,
  "includeCertificates": false,
  "timeoutSeconds": 25
}
```

| Option | Default | What it does |
|---|---|---|
| `domains` | required | Domains to enrich. `https://` and `www.` are stripped for you |
| `includeHomepage` | `true` | Read the public homepage for metadata, tech and socials |
| `includeCertificates` | `false` | Look up subdomains in public certificate logs. Off by default because the crt.sh service is often slow |
| `timeoutSeconds` | 25 | Per-domain timeout |

### Who this is for

- **Sales teams** qualifying inbound domains before a rep spends time on them
- **Marketing** segmenting a list by technology stack or company maturity
- **Investors** doing quick diligence across many companies at once
- **Recruiters** — the `atsPlatform` field tells you exactly where a company posts its jobs
- **Security and IT** auditing email authentication (SPF/DMARC) across a portfolio

Pairs naturally with our **ATS Jobs Aggregator**: this tells you a company uses Greenhouse and
gives you their slug; that one pulls all their open roles.

### Where the data comes from

| Source | What it provides |
|---|---|
| RDAP | Registration, registrar, dates |
| DNS | MX, NS, A records, SPF, DMARC |
| Public homepage | Metadata, technology signals, social links |
| Certificate transparency logs | Subdomains (optional) |

The homepage fetch **honours robots.txt** — a site that disallows crawling is skipped, and the
row comes back with `robotsAllowed: false`.

### Honest limits

- **Technology detection reads static HTML only.** Sites that load everything client-side will
  show fewer signals. Detection matches asset URLs, not brand names, so a company merely
  *mentioning* Shopify is not reported as using it.
- **`careersLinkInHtml` is about the HTML, not reality.** Sites with client-rendered navigation
  will report `false` even when the page exists. The field name says so deliberately.
- `includeCertificates` adds roughly 8 seconds per domain and sometimes returns nothing when
  crt.sh is unavailable.
- No personal contact data is collected. This profiles companies, not people.

### Pricing

Pay per event. You are charged per domain successfully enriched.

### Changelog

**1.0** — First release. RDAP, DNS, homepage metadata, technology and ATS detection.

# Actor input Schema

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

Domains or company websites to enrich, e.g. stripe.com. http(s):// and www. are stripped automatically.

## `includeHomepage` (type: `boolean`):

Read the public homepage for title, description, social links and technology signals. Honours robots.txt.

## `timeoutSeconds` (type: `integer`):

How long to wait for each domain before giving up. Raise it for slow sites, lower it to fail fast on large lists.

## `includeCertificates` (type: `boolean`):

Query public certificate-transparency logs for subdomains. Off by default: the crt.sh service is frequently slow or unavailable and can add ~8s per domain.

## Actor input object example

```json
{
  "domains": [
    "stripe.com",
    "notion.so",
    "figma.com"
  ],
  "includeHomepage": true,
  "timeoutSeconds": 25,
  "includeCertificates": false
}
```

# Actor output Schema

## `companies` (type: `string`):

Registration, DNS, technology and presence data for each domain.

## `companiesCsv` (type: `string`):

The same profiles as a spreadsheet-ready CSV.

# 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",
        "notion.so",
        "figma.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("sbr35/company-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",
        "notion.so",
        "figma.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("sbr35/company-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",
    "notion.so",
    "figma.com"
  ]
}' |
apify call sbr35/company-enrichment --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,sbr35/company-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/zCijjCskW4OkBlh5X/builds/8cx7uWpKr0Sq9wLLc/openapi.json