Domain WHOIS Lookup (RDAP) + DNS, MX, SPF and DMARC avatar

Domain WHOIS Lookup (RDAP) + DNS, MX, SPF and DMARC

Pricing

from $2.00 / 1,000 domain lookups

Go to Apify Store
Domain WHOIS Lookup (RDAP) + DNS, MX, SPF and DMARC

Domain WHOIS Lookup (RDAP) + DNS, MX, SPF and DMARC

Bulk domain lookup from official sources. For each domain: registrar, created, updated and expiry dates, domain age, status, nameservers and DNSSEC from the registry's RDAP server, plus DNS records, the email provider behind the MX, and SPF and DMARC policy. No registrant personal data.

Pricing

from $2.00 / 1,000 domain lookups

Rating

0.0

(0)

Developer

Ground Truth

Ground Truth

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Give it a list of domains. For each one you get who the registrar is, when it was registered and when it expires, whether it is registered at all, its nameservers and DNS records, which email provider handles its mail, and whether it publishes SPF and DMARC. Data comes from the registries' own RDAP servers and public DNS resolvers. Every record links to the source it came from.

When to use it

  • Check a list of domains from a CRM, a lead list or a CSV: which are still registered, which expire soon, how old each is.
  • Find which companies run Google Workspace, Microsoft 365, Zoho, Proofpoint or Mimecast, from their MX records.
  • Audit email authentication across a portfolio: who has SPF, who has DMARC, and whether DMARC is none, quarantine or reject.
  • Screen domains before you buy, rank or block them: registration age, registrar, status codes such as client hold.
  • Spot names that are free to register: registered: false when the registry itself answers "not found".

For an AI agent: call it when you need hard, checkable facts about a domain (is it registered, how old, who hosts its mail, does it have DMARC) instead of guessing from a web page.

What it does not do

  • It returns no registrant data: no owner name, email, phone or address, even when a registry sends them. Only the registrar, a company, is kept.
  • It does not use WHOIS port 43 and does not scrape any site. For a TLD with no RDAP server (many country codes, for example .ru, .cn, .jp, .ch) it returns DNS data only and sets rdap_available to false.
  • A few registries publish limited RDAP data. .de returns status and nameservers but no registrar or dates, and the record says so in notes.
  • DNS answers reflect the public resolvers at the time of the run. It does not read DKIM keys or website content.
  • email_provider is judged from MX hostnames. An unrecognised MX is Other (not a recognised provider), never a guess.

Sample output

Input:

{ "domains": ["google.com", "this-domain-does-not-exist-q8z1x.com"] }

Output for the first domain (trimmed to the main fields, run on 2026-10-18):

{
"domain": "google.com",
"lookup_status": "ok",
"registered": true,
"registered_basis": "rdap",
"registrar": "MarkMonitor Inc.",
"registrar_iana_id": 292,
"created_date": "1997-09-15",
"updated_date": "2019-09-09",
"expiry_date": "2028-09-14",
"domain_age_days": 10625,
"days_until_expiry": 697,
"status_codes": ["client delete prohibited", "client transfer prohibited", "client update prohibited",
"server delete prohibited", "server transfer prohibited", "server update prohibited"],
"nameservers": ["ns1.google.com", "ns2.google.com", "ns3.google.com", "ns4.google.com"],
"dnssec_signed": false,
"dns_mx": [{ "priority": 10, "host": "smtp.google.com" }],
"email_provider": "Google Workspace",
"email_provider_category": "mailbox",
"has_spf": true,
"spf_record": "v=spf1 include:_spf.google.com ~all",
"spf_policy": "softfail",
"has_dmarc": true,
"dmarc_record": "v=DMARC1; p=reject; rua=mailto:***@google.com",
"dmarc_policy": "reject",
"verify_url": "https://rdap.verisign.com/com/v1/domain/google.com"
}

The second domain comes back as registered: false, rdap_status: "not_found", dns_status: "nxdomain".

Check it yourself. Open the verify_url: it is the exact registry RDAP record the answer was read from. For DNS, open dns_verify_url, or run nslookup -type=MX google.com. To compare with classic WHOIS, query the registry at whois.verisign-grs.com: the creation date, expiry date and registrar IANA id will match. Registrar numbers can be checked in the IANA Registrar IDs registry (292 is MarkMonitor Inc.).

A handled error. Input such as "exa mple..com", "192.168.0.1" or 12345 is skipped with a plain reason in the run log and in the SKIPPED_INPUTS record, and is not charged. If every entry is unusable the run stops with a message that says so.

Input

FieldTypeRequiredDefaultMeaning
domainslist of textyesexample.com, iana.org, wikipedia.orgUp to 5,000 per run. Names, URLs, www. hosts and email addresses are reduced to the registered domain (https://www.bbc.co.uk/news becomes bbc.co.uk). Unicode names are converted to punycode. Duplicates are looked up once.
lookup_rdaptrue or falsenotrueRegistry data: registrar, dates, status, nameservers, DNSSEC, registered or not.
lookup_dnstrue or falsenotrueA, AAAA, MX, NS, TXT, email provider, SPF, DMARC.

Output fields

FieldMeaning
input, domain, domain_unicode, tldWhat you gave, the registered domain looked up, its unicode form if different, and its TLD
lookup_statusok, partial (one source did not answer) or error (none did, not charged)
checked_dateThe UTC date of the lookup
registered, registered_basistrue or false with rdap, or true with dns for TLDs without RDAP (a delegation exists). null when it cannot be told
rdap_available, rdap_status, rdap_serverWhether the TLD has an RDAP server; ok, not_found, no_rdap_for_tld, rate_limited, error or skipped; the server used
registrar, registrar_iana_idThe registrar company and its IANA id
created_date, updated_date, expiry_dateUTC dates from the registry
domain_age_days, days_until_expiryCounted from the registry dates to the check date. Negative days to expiry means the domain is past its expiry date
status_codes, nameservers, dnssec_signedEPP status codes, registry nameservers, whether the delegation is DNSSEC signed
dns_statusok, partial, nxdomain (name does not exist), servfail, error or skipped
dns_a, dns_aaaa, dns_mx, dns_ns, dns_txtResolved records. MX is a list of priority and host. TXT is capped at 100 records, and email addresses inside them are masked as ***@domain
email_provider, email_provider_categoryFrom the best-priority MX hosts. Category is mailbox, gateway (a filter such as Proofpoint or Mimecast in front of a mailbox system), forwarding, other or none (a null MX, RFC 7505)
has_spf, spf_record, spf_policySPF presence, the record, and its closing all: fail, softfail, neutral or pass
has_dmarc, dmarc_record, dmarc_policy, dmarc_subdomain_policy, dmarc_pctDMARC presence and the policy tags. Report mailbox names are masked
notesAnything worth knowing: a URL reduced to its domain, a registry with limited data, two SPF records
verify_url, dns_verify_urlThe RDAP record the data came from (or a public DNS lookup where the TLD has no RDAP), and a public DNS lookup of the MX records

Errors and what to do

What you seeMeaningWhat to do
lookup_status: "partial" or "error"A registry or resolver did not answerRe-run those domains. It does not mean the domain is unregistered
rdap_status: "rate_limited"The registry asked us to slow down and we stopped asking after two backoffsRe-run later, or in smaller batches
rdap_status: "no_rdap_for_tld"The TLD has no RDAP serverUse the DNS fields. registered is true only if nameservers exist
registered: falseThe registry itself answered "not found"The name is not registered (or has been released)
Entry skipped in the logNot a usable domainFix the entry; skipped entries are not charged

Pricing

Pay per event: $0.002 per domain looked up (about $2 per 1,000), plus Apify's small start event. You are not charged for invalid entries, duplicates, or a domain where every source failed.

Sources and licensing

Registry RDAP servers (served under their own terms), the IANA RDAP bootstrap file, Cloudflare and Google public DNS over HTTPS, and the Public Suffix List (Mozilla Public License 2.0). Details and the full testing record are in SOURCES.md.