QName AI WHOIS & RDAP

WHOIS domain lookup powered by QName AI

QName AI WHOIS & RDAP Domain Intelligence turns a domain list into structured, source-aware registration evidence. Add one domain or up to 1,000 domains, run the Actor, and receive one dataset row per domain. The WHOIS domain lookup is designed for domain research, portfolio checks, brand protection, SEO research, security triage, and AI Agent workflows that need predictable JSON instead of unstructured terminal output.

This Actor uses the managed QName AI API pool, so you do not need to expose a QName API key. Each WHOIS domain lookup can use RDAP, registrar WHOIS, or DNS evidence. The source distinguishes a complete WHOIS record from a DNS-only observation.

Key capabilities:

• Run a single or bulk WHOIS domain lookup with up to 1,000 unique domains.
• Receive normalized registrar, creation, update, expiry, nameserver, DNSSEC, status, error-code, and source fields.
• Preserve nested QName AI data for workflows that need more than the table view.
• Export WHOIS and RDAP results through Apify as JSON, JSONL, CSV, Excel, XML, or RSS.
• Schedule a recurring bulk WHOIS check or connect the dataset to other Apify integrations.
• Call the Actor from Apify API clients, CLI tools, or AI Agents through the Apify MCP server.

How to run a bulk WHOIS lookup

Open the Input tab and enter domains as a list. Bare domains and full URLs are accepted. The Actor extracts the hostname, converts it to lowercase, removes a trailing dot, and deduplicates the list before sending one bulk request to QName AI. Invalid or empty entries do not become WHOIS requests.

Example input:

{
  "domains": [
    "qname.ai",
    "example.com",
    "https://www.cloudflare.com/products/registrar/"
  ],
  "includeRaw": false
}

The maximum input is 1,000 domains per run. For recurring monitoring, save the configuration as an Apify task and attach a schedule. For a one-time WHOIS domain lookup, run the Actor and open the default dataset.

The optional includeRaw setting adds upstream WHOIS or RDAP evidence. Leave it disabled for compact datasets; enable it for parsing audits or later review.

WHOIS and RDAP output

Every requested domain produces an independent dataset row. A typical structured WHOIS result looks like this:

{
  "domain": "qname.ai",
  "registrationStatus": "registered",
  "code": "SUCCESS",
  "source": "rdap",
  "registrar": "Example Registrar",
  "createdDate": "2024-01-01T00:00:00Z",
  "expirationDate": "2027-01-01T00:00:00Z",
  "updatedDate": "2026-01-01T00:00:00Z",
  "nameServers": ["ns1.example.com", "ns2.example.com"],
  "statuses": ["clientTransferProhibited"],
  "dnssec": "signedDelegation",
  "error": null,
  "checkedAt": "2026-09-13T00:00:00.000Z"
}

The code and registrationStatus fields are intentionally separate. Common codes include SUCCESS, DOMAIN_NOT_REGISTERED, DOMAIN_RESERVED, DOMAIN_DROPZONE, DOMAIN_REGISTRY_RESTRICTED, and QUERY_FAILED. A failed WHOIS domain lookup is kept in the dataset instead of silently disappearing, which makes batch completeness easy to audit.

The source field can be rdap, whois, registrar, or dns. QName AI does not treat DNS-only evidence as a complete WHOIS record. When only DNS evidence is available, registrationStatus is dns_observed; the Actor does not invent registration dates, registrar details, or availability conclusions.

Why source-aware domain intelligence matters

WHOIS data is not uniform. Registries may provide structured RDAP, text WHOIS, redacted records, or restricted responses. A domain can resolve in DNS while a registration service is unavailable. Treating these signals as equivalent can create false availability alerts or incorrect domain-age calculations.

QName AI keeps structured evidence and exposes the source used for each result. An AI Agent can attribute registrar and expiry data to RDAP while flagging a DNS-only result for follow-up instead of presenting a guess as verified WHOIS.

Use cases

Domain portfolio monitoring

Schedule a bulk WHOIS domain lookup to track expiry dates, nameserver changes, transfer locks, and registrar changes. Treat each run as a timestamped observation rather than a permanent fact.

Domain acquisition research

Check candidates before deeper trademark or pricing research. DOMAIN_NOT_REGISTERED does not guarantee a normal-price purchase. Premium, reserved, restricted, and dropzone domains need a registrar check.

SEO and competitive research

Add creation dates, registrars, nameservers, and status codes to research data. WHOIS and RDAP evidence does not prove company age, traffic, or commercial success.

AI Agent and automation workflows

Use the Apify API or MCP server as a bounded WHOIS lookup tool. Stable output fields are easier for Agents to validate than free-form WHOIS text.

API and integrations

Run the Actor from Apify Console, API clients, CLI, schedules, or integrations. The API tab provides generated examples. Results use the default dataset, so Apify exports work without a separate QName credential.

The managed QName API key is an Actor secret environment variable. It is not included in inputs, datasets, logs, source files, or sample requests.

Limits and responsible use

• Maximum input: 1,000 unique domains per Actor run.
• Large WHOIS datasets can take longer because registries impose different latency and rate limits.
• Contact fields may be redacted or absent due to registry policy and privacy rules.
• WHOIS, RDAP, DNS, and registrar responses are observations, not legal advice or a guaranteed purchase decision.
• Do not use the Actor to collect or misuse personal data. Follow applicable law, registry terms, and Apify platform rules.

Frequently asked questions

Does the Actor require my QName API key?

No. The Store version uses a managed API pool configured by QName AI. A private QName key is never requested in the Actor input.

Can I check 1,000 domains in one run?

Yes. The input schema accepts up to 1,000 unique entries. The Actor normalizes URLs to hostnames and removes duplicates before the bulk WHOIS request.

Does DOMAIN_NOT_REGISTERED guarantee availability?

No. Confirm purchase availability and final price with a registrar. Reserved, premium, restricted, and dropzone names can behave differently from an ordinary unregistered domain.

Why is a result marked dns_observed?

It means QName AI found DNS evidence but did not receive complete structured WHOIS or RDAP evidence. The conservative label prevents DNS reachability from being presented as a verified registration record.

Where can I learn more about QName AI?

Visit QName AI, explore the WHOIS domain lookup, or review the qname-cli guide for terminal and Agent-native access.