WHOIS Company Intelligence API

What this Actor does

For each domain you provide, this Actor combines public domain registration data (WHOIS via the public RDAP protocol) with the company's own public website business metadata into one clean, enriched record.

It looks up registrar, registration/update/expiry dates, nameservers, registrant organization and country, and domain status from RDAP. When website enrichment is enabled, it also reads the company's public homepage for its title, description, Organization name, and public social profile links. Each domain produces exactly one dataset row, with source attribution, a confidence score, and a list of missing fields.

Why this Actor is useful

Sales, marketing, and research teams use domain-to-company enrichment to qualify leads, dedupe accounts, detect newly registered competitors, and append firmographic context to spreadsheets and CRMs. This Actor turns a list of domains into an API-ready dataset without manual lookups.

Who this is for

• B2B sales and lead-generation teams
• Growth and demand-generation marketers
• Sales and revenue operations
• Data enrichment and list-building teams
• Competitive intelligence analysts
• Anti-fraud and due-diligence researchers

Common use cases

• Enrich a list of domains with registrar and registration data
• Append company name, description, and social links to leads
• Detect newly registered or recently updated domains
• Build account-level firmographic datasets for outreach
• Add domain-age and registrant signals to lead scoring

How it works

• WHOIS / registration data comes from the public RDAP service at https://rdap.org/domain/{domain} (the modern, structured successor to WHOIS).
• Company business metadata comes only from the company's own public homepage (HTML <title>, meta description, schema.org Organization JSON-LD, and public social profile links).
• Each request uses a timeout, and a failure in one domain or one source never stops the whole run.

Input

• domains: List of domains to enrich. Accepts bare hostnames or full URLs (protocol and path are stripped automatically). Required.
• enrichFromWebsite: When true (default), also fetch the public homepage and read its public business metadata.
• maxItems: Maximum number of dataset rows to save.
• maxConcurrency: How many domains to process at once. The default is intentionally conservative.
• requestTimeoutSecs: Maximum time to spend on a single RDAP or website request.
• proxyConfiguration: Optional Apify proxy configuration where permitted by your compliance process.

Output

• domain: The normalized domain that was looked up.
• registrar: Registrar name from RDAP.
• createdDate: Domain registration date from RDAP.
• updatedDate: Last-changed date from RDAP.
• expiryDate: Expiration date from RDAP.
• nameservers: Nameserver hostnames from RDAP.
• registrantOrganization: Registrant organization from RDAP (often redacted by privacy services).
• registrantCountry: Registrant country from RDAP when published.
• domainStatus: EPP/RDAP status codes for the domain.
• companyName: Organization name from the homepage's structured data when enrichment is enabled.
• companyDescription: Public meta description from the homepage.
• websiteTitle: The homepage <title>.
• socialProfiles: Public social profile links found on the homepage.
• sourceUrl: The homepage URL used for enrichment.
• detectedAt: Timestamp when this Actor produced the row.
• dataSources: Which sources succeeded, e.g. ["rdap","website"].
• confidenceScore: Heuristic confidence based on how many sources succeeded and how complete the key fields are.
• missingFields: Which of the key fields (registrar, createdDate, companyName) were not available.

Sample input

{
  "domains": [
    "apify.com"
  ],
  "enrichFromWebsite": true,
  "maxItems": 50,
  "maxConcurrency": 3,
  "requestTimeoutSecs": 30
}

Sample output

{
  "domain": "apify.com",
  "registrar": "Gandi SAS",
  "createdDate": "2015-12-21T13:21:34Z",
  "updatedDate": "2024-11-19T09:14:02Z",
  "expiryDate": "2025-12-21T13:21:34Z",
  "nameservers": [
    "albert.ns.cloudflare.com",
    "lola.ns.cloudflare.com"
  ],
  "registrantOrganization": "Apify Technologies s.r.o.",
  "registrantCountry": "CZ",
  "domainStatus": [
    "client transfer prohibited"
  ],
  "companyName": "Apify",
  "companyDescription": "Apify is the platform where developers build, deploy, and publish web scraping and automation tools.",
  "websiteTitle": "Apify: Full-stack web scraping and data extraction platform",
  "socialProfiles": [
    "https://twitter.com/apify",
    "https://www.linkedin.com/company/apifytech",
    "https://github.com/apify"
  ],
  "sourceUrl": "https://apify.com",
  "detectedAt": "2026-06-27T00:00:00.000Z",
  "dataSources": [
    "rdap",
    "website"
  ],
  "confidenceScore": 1,
  "missingFields": []
}

How to use

Run this Actor on Apify with a list of domains, export the dataset as JSON, CSV, or Excel, or pull it through the Apify API. Connect the output to Google Sheets, Make, Zapier, a webhook, or your CRM. For recurring enrichment, save the input as an Apify task and schedule runs.

Pricing

This Actor is designed for a pay-per-event model at $0.003 per lookup (one event per domain enriched). You pay only for the domains you process.

Best practices

• Provide clean domains; full URLs are accepted and normalized automatically.
• Keep maxConcurrency low to be gentle on RDAP and origin servers.
• Treat redacted registrant fields as expected, not as errors.
• Use missingFields and confidenceScore to filter records in downstream workflows.

Compliance and responsible use

• WHOIS data is sourced only from the public RDAP protocol (rdap.org), which exposes registration data that registries and registrars publish for public access. Many registrants are redacted for privacy (for example under GDPR); this Actor reports those fields as missing rather than inferring them.
• Company metadata is read only from the company's own public homepage — the public HTML title, meta description, schema.org Organization data, and public social profile links. No login, paywall, CAPTCHA, or access-control bypass is performed.
• Crunchbase, LinkedIn, and similar proprietary databases are NOT scraped. Those platforms require their own licensed APIs and have their own terms. This Actor does not access, scrape, or resell their data. Any "company intelligence" here is derived solely from public RDAP records and the company's own public website.
• This Actor is for public data only. It must not be used to gather sensitive personal data, support spam or abuse, or violate applicable laws or source terms. You are responsible for your use of the output.

Limitations

• Registrant organization and country are frequently redacted by privacy/proxy services and will appear as missing.
• RDAP coverage and field availability vary by TLD and registry; some TLDs expose less data than others.
• Website metadata quality depends entirely on what the company publishes on its public homepage. Sites without structured data or meta tags will have fewer enriched fields.
• This Actor reads only the homepage, not deep crawls of a site.
• It does not provide funding, headcount, revenue, or other proprietary firmographics that require licensed third-party databases (such as Crunchbase or LinkedIn).
• Markup, RDAP availability, and access policies can change over time.

Troubleshooting

• Empty registrar/dates usually mean the RDAP service had no record or the TLD exposes limited data.
• Empty company fields usually mean the homepage has no structured data or meta description, or enrichment was disabled.
• Slow runs can usually be improved by lowering maxConcurrency or requestTimeoutSecs.
• Missing fields reflect source-data limitations, not invented values.

Changelog

• v0.1.0: Initial release combining public RDAP registration data with public website business metadata.

Use WHOIS Company Intelligence API with AI agents (MCP)

Give Claude, ChatGPT, Cursor, VS Code or any MCP client this Actor as a tool through the hosted Apify MCP server. The agent sees the input fields with descriptions and example values, runs the Actor, and reads the results.

MCP server URL (this Actor only):

https://mcp.apify.com/?tools=technicaldost/whois-company-intelligence-api

Claude Code:

$claude mcp add --transport http apify "https://mcp.apify.com/?tools=technicaldost/whois-company-intelligence-api" --header "Authorization: Bearer YOUR_APIFY_TOKEN"

Cursor, VS Code, Claude Desktop and other clients (mcp.json or the client's MCP settings):

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com/?tools=technicaldost/whois-company-intelligence-api",
      "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }
    }
  }
}

Clients that support sign-in (such as Claude.ai connectors) can use the URL without a token and log in to Apify instead. Get your token in Apify Console → Settings → API & Integrations, or generate a ready config for your client at mcp.apify.com. In the agent the tool is named technicaldost--whois-company-intelligence-api; ask it, for example, to "run WHOIS Company Intelligence API with {"domains": ["apify.com"]}".

AI agents without an Apify account can also run and pay for this Actor per request with x402 agentic payments.

Run WHOIS Company Intelligence API via API

Run the Actor and get its results in one call (replace YOUR_APIFY_TOKEN):

curl -X POST "https://api.apify.com/v2/acts/technicaldost~whois-company-intelligence-api/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"domains": ["apify.com"]}'

Python (pip install apify-client):

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("technicaldost/whois-company-intelligence-api").call(run_input={"domains": ["apify.com"]})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript / TypeScript (npm install apify-client):

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });
const run = await client.actor('technicaldost/whois-company-intelligence-api').call({"domains": ["apify.com"]});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Long runs: start them with POST /v2/acts/technicaldost~whois-company-intelligence-api/runs and fetch the dataset when the run finishes, or receive a webhook.

Related Actors

• Company Tech-Stack & Domain Intelligence API — Domain to company tech stack, founded year, headcount, industry, funding, socials & logo. Open-data company en
• Healthcare Intelligence Scraper — Extract healthcare provider data from NPI registry, Healthgrades, Zocdoc directories
• Brazil CNPJ Company Lookup - Receita Federal — Look up Brazilian companies you already have a CNPJ for. Public RFB company record: legal name, CNAE, status
• Career Page Job Scraper & Change Monitor — Scrape public career pages and ATS job boards, filter structured roles, and detect new or removed openings acr

FAQ

Can I use WHOIS Company Intelligence API with AI agents like Claude or ChatGPT?

Yes. Connect the Apify MCP server with ?tools=technicaldost/whois-company-intelligence-api (see above) and the agent can run the Actor and read its results on its own.

Can I call WHOIS Company Intelligence API from my own code?

Yes. Use the REST API, or the official Python and JavaScript clients shown above. Results are available as JSON, CSV, Excel, XML or HTML.

How do I run it on a schedule?

Save your input as a task in Apify Console and add a schedule (for example, daily). Use webhooks or integrations to send each run's results onward.

Is it legal to use this Actor?

It works with publicly available data. Make sure your use complies with the source website's terms and with data protection laws such as GDPR, especially for personal data.

Something doesn't work or I need a feature. What should I do?

Open an issue in the Issues tab on this Actor's page with an example input, and we'll look into it.