Domain & DNS Lookup API — records, whois & IP (no key) avatar

Domain & DNS Lookup API — records, whois & IP (no key)

Pricing

from $2.00 / 1,000 lookups

Go to Apify Store
Domain & DNS Lookup API — records, whois & IP (no key)

Domain & DNS Lookup API — records, whois & IP (no key)

Resolve DNS records (A/AAAA/MX/TXT/NS/CNAME/SOA/CAA), look up domain whois via RDAP (registrar, dates, status, nameservers, DNSSEC), and IP-network ownership (owner, country, CIDR). Clean HTTP API + MCP, no key. Pay per query.

Pricing

from $2.00 / 1,000 lookups

Rating

0.0

(0)

Developer

Synthetic

Synthetic

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

2 days ago

Last modified

Categories

Share

Everything you need to inspect a domain or an IP, behind a clean HTTP API (and MCP tool): resolve DNS records (A, AAAA, MX, TXT, NS, CNAME, SOA, CAA, SRV, PTR), pull domain whois via RDAP (registrar, creation/expiry dates, status, nameservers, DNSSEC), and look up IP-network ownership (org, country, CIDR range, abuse contact). Perfect for monitoring, security, sales intelligence, deliverability and agents. No API key. Pay per query.

  • 🌐 DNS records — resolve any record type over DNS-over-HTTPS (fast, portable, no local resolver needed).
  • 📇 Whois (RDAP) — registrar, registration/expiry/updated dates, EPP status codes, nameservers, DNSSEC — structured, not raw text.
  • 🖧 IP network — who owns an IP: network name, country, CIDR range, parent allocation and abuse contact.
  • 🔒 Modern & keyless — RDAP (the successor to legacy whois) + DoH; clean JSON, no key.
  • 💵 Pay per query.

The use case it was built for

Check a domain's MX and SPF before sending mail, watch an expiry date, confirm DNSSEC, or find out which network an IP belongs to for abuse triage — all in one call, as structured JSON your app or agent can act on.

Sample output (whois, domain "github.com")

{
"ok": true, "domain": "github.com", "registrar": "MarkMonitor Inc.",
"status": ["client delete prohibited", "client transfer prohibited"],
"created": "2007-10-09T18:20:50Z", "expires": "2028-10-09T18:20:50Z",
"nameservers": ["dns1.p08.nsone.net", "dns2.p08.nsone.net"], "dnssec": false
}

How to use

  • HTTP API (Standby): POST or GET /dns, /whois, /ip. GET / returns help. Example: GET /dns?domain=example.com&types=MX,TXT.
  • Normal run: pass { operation, domain | ip, types? }; results land in the dataset + key-value store.
  • MCP tool: expose it to your agent via Apify's MCP server.

Input

  • operationdns · whois · ip.
  • domain — for dns / whois (a full URL is accepted; the host is used).
  • types — (dns) record types, e.g. ["A","MX","TXT"]. Default: A, AAAA, MX, TXT, NS.
  • ip — for ip (IPv4 or IPv6).

Pricing

Per query from $0.005 (down to $0.0015 on higher tiers). One call = one lookup (the dns op can return many record types at once).

FAQ

Do I need a key? No. DNS uses DNS-over-HTTPS (Google, with a Cloudflare fallback); whois/IP use RDAP via rdap.org.

Why RDAP instead of whois? RDAP is the IETF standard replacing legacy port-43 whois — it returns structured JSON with consistent fields. Some TLDs (e.g. a few ccTLDs) don't publish RDAP yet; those return a clear "no RDAP" message.

Can it check SPF/DKIM/DMARC? Yes — request the TXT record type (SPF/DMARC live in TXT; DKIM under its selector subdomain).

Notes & limits

DNS answers reflect the resolver's view and TTLs. RDAP fields vary slightly by registry. IP lookups return network-level ownership (not street-level geolocation).