# Domain WHOIS Lookup — RDAP, Expiry, DNS, MX & SSL in Bulk (`jeffev/domain-whois-lookup`) Actor Bulk domain lookup: registrar, creation and expiry dates, days to expiry, domain age, status, nameservers and registrant (when public; .br includes the CNPJ/CPF), via RDAP, the official WHOIS successor. Plus DNS (A, MX, NS, SPF, DMARC, email provider) and SSL certificate issuer and expiry. - **URL**: https://apify.com/jeffev/domain-whois-lookup.md - **Developed by:** [Jefferson Valandro](https://apify.com/jeffev) (community) - **Categories:** Developer tools, SEO tools, Lead generation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $1.40 / 1,000 domain lookups This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. 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 WHOIS Lookup — RDAP, Expiry, DNS, MX & SSL in Bulk Look up **thousands of domains at once** and get the **registrar, creation date, expiry date and days to expiry, domain age, status, nameservers and DNSSEC**, plus the **registrant** when it is public (for **.br domains, the owner's name and CNPJ/CPF**). Uses **RDAP**, the official successor of WHOIS, with a classic WHOIS fallback for registries that don't offer RDAP. Optionally adds **DNS** (A, AAAA, MX, NS, SPF, DMARC and the detected **email provider**: Google Workspace, Microsoft 365, Zoho...) and the **SSL certificate** (issuer, validity, days to expiry, names covered). Built for **domain portfolio and expiry monitoring, lead enrichment** (which companies use Google Workspace or Microsoft 365), **security and IT audits, and SEO research**. ### Why this one - **Domains, URLs or emails** as input: the domain is extracted automatically, subdomains are reduced to the registered domain. - **Registrar lookup for .com/.net**: the central registry only knows the registrar, so the actor also asks the registrar for the registrant organization and country. - **Days to expiry** for both the domain and the SSL certificate, ready for alerts. - **Email provider detection** from MX records, plus SPF and DMARC. - **.br registrant with CNPJ**, straight from registro.br. ### Input ```json { "domains": ["github.com", "https://www.magazineluiza.com.br/", "contact@shopify.com", "bbc.co.uk"], "includeDns": true, "includeSsl": true } ``` ### Output | Field | Description | |---|---| | `domain`, `host`, `registered`, `source` | domain, original host, whether it is registered, RDAP or WHOIS | | `registrar`, `registrarIanaId`, `createdAt`, `updatedAt`, `expiresAt`, `daysToExpiry`, `domainAgeYears` | registration | | `status`, `nameservers`, `dnssec` | registry status | | `registrantName`, `registrantCountry`, `registrantEmail`, `registrantDocument`, `privacyProtected`, `abuseEmail` | registrant (when public) | | `a`, `aaaa`, `mx`, `ns`, `spf`, `dmarc`, `emailProvider` | DNS | | `sslValid`, `sslIssuer`, `sslValidFrom`, `sslValidTo`, `sslDaysToExpiry`, `sslNames` | SSL certificate | ### Example output One real item from a test run (long texts and lists shortened): ```json { "type": "domain", "input": "expired.badssl.com", "domain": "badssl.com", "registered": true, "source": "rdap", "registrar": "MarkMonitor Inc.", "registrarIanaId": "292", "createdAt": "2015-04-07T22:09:30Z", "updatedAt": "2026-03-06T10:32:49Z", "expiresAt": "2027-04-07T22:09:30Z", "daysToExpiry": 163, "domainAgeYears": 11.6, "status": [ "client delete prohibited", "client transfer prohibited", "client update prohibited" ], "nameservers": [ "ns-cloud-c1.googledomains.com", "ns-cloud-c2.googledomains.com", "ns-cloud-c3.googledomains.com" ], "dnssec": false, "registrantName": "DNStination Inc.", "registrantCountry": "US", "registrantEmail": "admin@dnstinations.com", "registrantDocument": null, "privacyProtected": false, "abuseEmail": "abusecomplaints@markmonitor.com", "rdapServer": "https://rdap.verisign.com/com/v1", "a": [ "104.154.89.105" ], "aaaa": [], "mx": [ "gmr-smtp-in.l.google.com", "alt1.gmr-smtp-in.l.google.com", "alt2.gmr-smtp-in.l.google.com" ] } ``` ### Notes - Most registrars hide personal registrant data (GDPR); companies often keep their organization name public. - Some country registries (e.g. .de) publish only whether a domain is registered. ### Feedback Found a problem or need a field? Open an issue in the **Issues** tab: every issue is read and answered. If the actor helped you, a review on the Store helps a lot. ### How much does it cost? You pay only for results delivered, at a fixed price per item. **Apify platform usage is included** in that price, so there are no compute costs on top. Errors and items that couldn't be found are free. | What you get | Price | Example | |---|---|---| | Domain lookup | $0.002 each | 1,000 domain lookups = $2.00 | The Apify **Free plan includes $5 of monthly credit**, enough for about **2,500 domain lookups** per month at no cost. You can also set a maximum spend per run. On paid Apify plans it gets cheaper automatically: **10% off on Starter, 20% on Scale and 30% on Business**. # Actor input Schema ## `domains` (type: `array`): Domains, website URLs or email addresses, one per line (the domain is extracted automatically). ## `includeDns` (type: `boolean`): A, AAAA, MX, NS, SPF and DMARC records, plus the detected email provider (Google Workspace, Microsoft 365...). ## `includeSsl` (type: `boolean`): Certificate issuer, validity dates, days to expiry and names covered. ## `followRegistrar` (type: `boolean`): For .com/.net and similar, the central registry only knows the registrar; this also queries the registrar's RDAP for registrant organization and country (often privacy-protected). ## Actor input object example ```json { "domains": [ "github.com", "magazineluiza.com.br", "bbc.co.uk" ], "includeDns": true, "includeSsl": true, "followRegistrar": true } ``` # Actor output Schema ## `results` (type: `string`): Registration, DNS and SSL data per domain. # 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "domains": [ "github.com", "magazineluiza.com.br", "bbc.co.uk" ] }; // Run the Actor and wait for it to finish const run = await client.actor("jeffev/domain-whois-lookup").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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "domains": [ "github.com", "magazineluiza.com.br", "bbc.co.uk", ] } # Run the Actor and wait for it to finish run = client.actor("jeffev/domain-whois-lookup").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": [ "github.com", "magazineluiza.com.br", "bbc.co.uk" ] }' | apify call jeffev/domain-whois-lookup --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,jeffev/domain-whois-lookup" } } } ``` 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 ` 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/XBz3h0VC1dPybaYPo/builds/nqlnT9aLJO8Uxqk5N/openapi.json