Bulk Domain RDAP & DNS Lookup – Registrar, Expiry, Age, MX/SPF/DMARC

Paste in a list of domains (or full website addresses) and get one clean row per domain with its registration details, DNS records and basic email-security checks.

The tool asks the official domain registries directly using RDAP, the modern, structured replacement for WHOIS. The right registry server for each domain ending (.com, .org, .uk and so on) is picked from the official IANA directory. DNS records come from a public DNS-over-HTTPS resolver.

Registrant names, addresses, phone numbers and email addresses are never collected.

What you get for each domain

• Whether the domain is registered (or likely available)
• Registrar name and registrar IANA ID
• Creation, last-updated and expiry dates
• Domain age in days and days left until expiry, already calculated for you
• Registry status codes, such as "client transfer prohibited"
• Nameservers and whether DNSSEC is enabled
• DNS records of the types you choose: A, AAAA, MX, NS, TXT, CNAME, SOA, CAA
• Whether the domain has an SPF record and a DMARC record
• The registry server that answered, and an error note if something went wrong

Typical uses

• Track when your own domains, or your clients' domains, are due to expire
• Check how old a domain is when assessing leads, vendors or suspicious websites
• Audit email security (MX, SPF, DMARC) across many domains at once
• Find out which registrar and DNS provider a list of companies uses
• Check whether names on a shortlist are still unregistered

Price

$0.002 per domain looked up. For example, 1,000 domains cost $2.00. You pay only for the rows you receive, and the run never returns more rows than your Max results setting.

Input

Field	What it does
Domains (required)	A list of domains or URLs, for example example.com or https://www.example.org/page. Each URL is reduced to its registrable domain, so www.bbc.co.uk/news becomes bbc.co.uk. Duplicates are removed.
Include DNS records	Turn DNS record lookups on or off. Default: on.
DNS record types	The record types to fetch: A, AAAA, MX, NS, TXT, CNAME, SOA, CAA. Default: A, AAAA, MX, NS, TXT.
Check SPF / DMARC	Checks for an SPF record and looks up the _dmarc record. Default: on.
Max results	The maximum number of domains to process. The input form pre-fills 1,000. If the field is left out entirely, the limit is 50.

Example input

{
  "domains": ["google.com", "example.org", "https://www.bbc.co.uk/news"],
  "includeDns": true,
  "recordTypes": ["A", "MX", "NS", "TXT"],
  "includeEmailSecurity": true,
  "maxItems": 100
}

Output

Field	Meaning
domain	Normalised domain name
registered	true if the registry has a record. false if it was not found, which usually means the domain is available.
registrar	Sponsoring registrar name
registrarIanaId	Registrar IANA ID, if provided
createdDate	Registration date (ISO 8601, UTC)
updatedDate	Date the registry record last changed
expiresDate	Expiry date
domainAgeDays	Days since registration
daysUntilExpiry	Days until expiry
statuses	Registry status codes
nameservers	Nameservers listed at the registry
dnssec	true if the domain's delegation is DNSSEC-signed
dnsRecords	Record type mapped to a list of values
hasSpf	true if a TXT record starts with v=spf1
hasDmarc	true if a _dmarc record starting with v=DMARC1 exists
rdapServer	The registry RDAP address that answered
error	Empty if all went well, otherwise a short explanation
checkedAt	Time of the lookup (ISO 8601, UTC)

How some values are formatted (please read)

• IPv4 addresses use underscores instead of dots. For example, 93.184.215.14 appears as 93_184_215_14. This applies to A records and to IP addresses inside TXT records such as SPF. Without it, automated personal-data filters can mistake an IP address for a phone number. To get the usual form, replace each _ with a dot.
• In TXT and CAA records, email addresses are replaced with [email redacted], and any run of 7 or more digits is replaced with [masked]. The hasSpf and hasDmarc checks use the original, unmasked records, so they are not affected.
• For SOA, only the primary nameserver is returned.

Example output row

{
  "domain": "example.org",
  "registered": true,
  "registrar": "ICANN",
  "registrarIanaId": "376",
  "createdDate": "1995-08-31T04:00:00Z",
  "updatedDate": "2026-08-30T04:00:10Z",
  "expiresDate": "2027-08-30T04:00:00Z",
  "domainAgeDays": 11355,
  "daysUntilExpiry": 331,
  "statuses": ["server delete prohibited", "server transfer prohibited", "server update prohibited", "auto renew period"],
  "nameservers": ["katelyn.ns.cloudflare.com", "mitch.ns.cloudflare.com"],
  "dnssec": true,
  "dnsRecords": {
    "A": ["104_20_26_136", "172_66_157_237"],
    "MX": ["0 ."],
    "NS": ["katelyn.ns.cloudflare.com", "mitch.ns.cloudflare.com"],
    "TXT": ["v=spf1 -all"]
  },
  "hasSpf": true,
  "hasDmarc": true,
  "rdapServer": "https://rdap.publicinterestregistry.org/rdap/",
  "error": "",
  "checkedAt": "2026-10-02T07:20:44Z"
}

Limits and good to know

• Some domain endings have no RDAP service. A few country-code endings do not publish one. For these domains, the row says so in the error field, and registration status is inferred from DNS where possible.
• Registries limit request rates. The tool sends one request at a time to each registry, with a short pause between requests, and retries temporary errors with increasing waits. If a registry or the DNS resolver refuses access outright (for example HTTP 403 or 429 after retries), the run stops and logs the reason clearly. Results collected up to that point are kept.
• "Not registered" is not a guarantee. A false value in registered means the registry had no record at the moment of the lookup. It does not guarantee that you can buy the domain, because names can be reserved or premium.
• Results are a snapshot. Dates, records and statuses can change after the lookup.
• One bad domain never ends the run. Problems are noted in that row's error field and the run continues.

Terms and privacy

This tool uses public, documented protocols: RDAP from the official domain registries and DNS-over-HTTPS. Contact details of registrants, administrators and abuse desks are deliberately ignored and never stored. Registries publish their own terms of use, which generally allow lookups for lawful purposes and prohibit using the data for spam or unsolicited marketing. You are responsible for using the results in line with those terms and with applicable law.