Bulk DNS Records Lookup - A, MX, TXT, SPF & DMARC

Resolve the DNS records for a whole list of domains in one run. For each domain you get its A / AAAA addresses, MX mail servers, TXT records, NS name servers, CNAME, SOA and CAA - plus the SPF and DMARC records pulled out for you and the mail provider inferred from the MX host (Google Workspace, Microsoft 365, Zoho, Proton, and more).

Runs on Node's native DNS resolver - no browser, no anti-bot target, no proxy needed - so it is fast and costs a fraction of a cent per domain. Ideal for email-deliverability audits, domain due diligence, security/attack-surface checks and enriching a lead list with the domain's mail stack.

What you get per domain

Field	Meaning
a / aaaa	IPv4 and IPv6 addresses
mx	Mail servers, sorted by priority (exchange + priority)
txt	All TXT records (as strings)
ns	Authoritative name servers
cname / soa / caa	Canonical name, start-of-authority, and certificate-authority records
spf	The v=spf1... record, lifted out of TXT
dmarc	The v=DMARC1... record from _dmarc.<domain>
mailProvider	Email host inferred from the MX record (e.g. Google Workspace, Microsoft 365)
resolved	true if the domain resolves to anything (A/AAAA/MX/NS/CNAME)

A missing record is a null field, not an error - a domain that does not exist comes back with resolved: false and a short error, and is still one row so your list stays aligned.

Input

{
  "domains": ["google.com", "apify.com", "github.com"],
  "recordTypes": ["A", "MX", "TXT", "DMARC"]
}

• Domains - one per line. A full URL or an email address is fine too; only the host is used (https://www.example.com/path and joe@example.com both become example.com).
• Import from a file - paste a whole list, or link a public .txt/.csv, a Google Sheet/Drive link, or an Apify key-value-store record.
• Record types - leave empty for all, or pick just the ones you need (SPF comes with TXT).
• Output fields - tick only the columns you want for a lean export.

Leave the domain list empty and the run returns a small free sample so you can see the shape first.

Use with AI assistants (MCP)

Available through the Apify MCP server - an agent can resolve the mail stack for a batch of domains before deciding where to route a message or whether a domain is set up for email at all.

Agent-ready: autonomous payments (x402 & Skyfire)

This actor is agent-ready - AI agents can discover it, run it, and pay for it autonomously, with no Apify account and no human in the loop. It uses pay-per-event pricing and limited permissions, so it qualifies for Apify's agentic-payment standards:

• x402 - an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the Apify MCP server - no account, no API key.
• Skyfire - agent-to-service payments for fully autonomous AI-agent workflows.

Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.