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.