Registrant Lookup and Reverse WHOIS — What Is (and Isn't) Possible

Two hard facts govern every “who owns this domain?” / “what domains does this person own?” question:

1. RDAP/WHOIS no longer contains registrant contact data. Since GDPR took effect (May 2018), registries and registrars redact the registrant’s name, organization, email, and phone from public registration data. DataPulse RDAP tools return registrar-level data only — there are no registrant fields in the responses.
2. DataPulse has no reverse-WHOIS capability. No DataPulse tool can search registration records by registrant email, name, or organization — the data is not in the records to begin with, and the search tools match domain-name labels, not WHOIS/RDAP record contents.

Registrar vs Registrant

These are routinely confused. They are different parties:

abuse_email / abuse_phone are the registrar’s abuse desk — a contact for reporting abuse of any domain that registrar sponsors. They are NOT the domain owner’s contact details. Never present them as the registrant.

Queries This Server Cannot Answer

• “Any domain with WHOIS details containing <email>” — reverse WHOIS by registrant email. Not possible.
• “All domains registered by <person/organization>” — reverse WHOIS by registrant name/org. Not possible.
• “Who owns <domain>?” — the registrant’s identity is redacted; only the sponsoring registrar, dates, status, and nameservers are available.

Do not reach for the search tools as a workaround:

• datapulse_dns_searchlabels / datapulse_dns_dpsearch match domain-name labels only — passing an email address just fuzzy-matches the string against domain names and returns meaningless results.
• datapulse_dns_registrar searches registrar company names (GoDaddy, Tucows, …), not domain owners.

None of them search registration-record contents.

How to Answer Such a Query

Tell the user, honestly:

1. Registrant contact data has been redacted from public WHOIS/RDAP since GDPR (2018), and DataPulse does not offer reverse-WHOIS.
2. Commercial reverse-WHOIS providers exist outside DataPulse (built on pre-2018 archives and private data-sharing agreements), but coverage of post-2018 registrations is inherently poor for the same reason.
3. Offer the alternative pivots below.

Do NOT run the email through a label search — it will not match anything meaningful and gives the user false confidence that a search was performed.

What You CAN Do Instead

• Have a specific candidate domain? datapulse_live_rdap(query=...) — registrar, registration/expiration dates, status, nameservers.
• Have a brand or name string? datapulse_dns_searchlabels on the label (e.g. neurogum), never the email address — then investigate the hits individually.
• Want an ownership signal for a domain? datapulse_domain_overview — its entity_name/entity_type/country come from LLM extraction of the site’s web content (not RDAP). Treat it as a claim made by the website, not a registration record.
• Attribution via infrastructure: datapulse_dns_dptechsim (similar DNS fingerprints), datapulse_dns_neighborhood (cluster membership), datapulse_dns_regclusters (same registrar + date cohorts), and datapulse_dns_rdap_history (registrar/nameserver timelines) can link domains to a common operator without registrant data.

Related Topics

• datapulse_help(topic="rdap") — RDAP lookups, response format, GDPR impact
• datapulse_help(topic="searchlabels") — what label search actually matches
• datapulse_help(topic="typo_squatting") — inferring relationships from infrastructure