Domain Lookup API - DNS, MX, SPF, Tech & Contact Emails avatar

Domain Lookup API - DNS, MX, SPF, Tech & Contact Emails

Pricing

from $2.55 / 1,000 domain analyzeds

Go to Apify Store
Domain Lookup API - DNS, MX, SPF, Tech & Contact Emails

Domain Lookup API - DNS, MX, SPF, Tech & Contact Emails

Domain lookup in one call: DNS A/AAAA, MX mail servers, NS, SPF/TXT, homepage title and tech hints, social profiles and public contact emails for any domain. Use it for lead enrichment, KYB checks and email deliverability. Keyless, bulk.

Pricing

from $2.55 / 1,000 domain analyzeds

Rating

0.0

(0)

Developer

Centor Prat

Centor Prat

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

πŸ”Ž Domain Lookup API: DNS, MX, SPF, Tech & Contact Emails

One call, DNS + the live homepage, one record. Give a domain (or many) and get a single structured intel record β€” resolved IPs, mail (MX) & name servers, SPF, homepage title/description/ tech, social profile links, and public contact emails β€” instead of juggling DNS tools and a crawler.

Headless Β· keyless (no API keys) Β· structured JSON out Β· built for AI agents.

⚑ Why it's different

Other actors give you raw DNS or raw page scrapes. This one fuses them into one agent-ready record and judges it: does it resolve, does it run mail, does it expose contacts? Ask once.

πŸ“‹ What you get (per domain)

FieldMeaning
resolves, dns.a, dns.aaaaDoes it resolve + its IPv4/IPv6
dns.mx, hasMailServerMail servers + a flag
dns.ns, dns.spf, dns.txtName servers, SPF record, TXT records
homepage.title, .metaDescription, .canonical, .generatorLive homepage metadata + tech hint
techHintsDetected stack hints (e.g. generator)
socialLinkedIn / Twitter(X) / Facebook / Instagram / YouTube / GitHub / TikTok links
emailsPublic contact emails found on the homepage
robotsTxt, sitemapsrobots.txt presence + any declared sitemaps
hasContactsTrue if emails or social links were found

πŸ“₯ Input

FieldTypeMeaning
domainstringA single domain, e.g. apify.com (scheme/path stripped)
domainsarrayMany domains: ["apify.com","stripe.com"] (billed per domain)
includeEmailsbooleanExtract public contact emails (default true; off to skip personal data)
webhookUrlstringPOST the records here (Zapier/Make/n8n/custom)

Example input

{ "domains": ["apify.com", "stripe.com"] }

πŸ“€ Output (one row per domain)

{
"domain": "apify.com", "resolves": true, "hasMailServer": true,
"dns": { "a": ["99.84.9.10"], "mx": ["0 apify-com.mail.protection.outlook.com."],
"ns": ["ns-1928.awsdns-49.co.uk."], "spf": "v=spf1 include:... -all", "txt": ["..."] },
"homepage": { "finalUrl": "https://apify.com/", "statusCode": 200,
"title": "Apify: Marketplace of ready-to-run tools for AI",
"metaDescription": "...", "generator": null },
"techHints": [], "social": [{"platform":"github","url":"https://github.com/apify"}],
"emails": ["support@apify.com"], "robotsTxt": true, "sitemaps": ["https://apify.com/sitemap.xml"],
"hasContacts": true, "sources": ["dns.google (DNS-over-HTTPS)", "apify.com (homepage)"],
"capturedAt": "2026-..."
}

πŸ’° Pricing (pay-per-event menu)

  • domain-analyzed β€” base, charged per domain.
  • contacts-found β€” premium, charged only when a domain yields emails/social (the high-value outcome).

πŸ’‘ Use cases

  • Lead enrichment: turn a list of domains into contacts + socials + tech in one call.
  • Due diligence / KYB: does it resolve, run mail (MX/SPF), what's the stack, who to contact.
  • Agent tools: give an outreach/research agent one call instead of DNS + crawl + parse glue.
  • Deliverability checks: MX + SPF presence at a glance across many domains.

πŸ€– For AI agents (MCP)

Keyless, one call β†’ a fused, structured record. Every input is described in the schema for programmatic/MCP use. Example MCP server config:

{
"mcpServers": {
"domain-intel": {
"url": "https://mcp.apify.com/?tools=actors,docs,centorprat/domain-lookup-dns-mx-email"
}
}
}

Claude Code: claude mcp add --transport http apify "https://mcp.apify.com/?tools=actors,docs,centorprat/domain-lookup-dns-mx-email" --header "Authorization: Bearer <YOUR_APIFY_TOKEN>"

No extra setup: this Actor is callable from Claude, Cursor, ChatGPT or any MCP client through the Apify MCP server, and agents can find it on their own with the server's search-actors tool.

πŸš€ Ready-made tasks (one click)

Pre-configured runs for the most common jobs. Open one, change the input, run:

❓ FAQ

  • Do I need an API key? No β€” DNS-over-HTTPS and the homepage fetch are keyless.
  • How many domains per run? As many as you pass; billed per domain (plus the premium event when contacts are found).
  • Where do emails/social come from? Only the domain's own public homepage HTML β€” no login, no third-party data.
  • Why didn't it find social/emails for site X? Many sites load them via JavaScript or keep them off the homepage; this reads the homepage HTML only.
  • Does it follow redirects? Yes (https first, then http), and reports the final URL + status.
  • Is the data stored? No β€” fetched, composed, returned.
  • Commercial use? The DNS and your-target homepage are public; see the note below on personal data.

⚠️ Personal data

emails may be personal data. Use it lawfully (e.g. legitimate B2B outreach, due diligence) and in line with GDPR/CAN-SPAM and the target site's terms. This actor only reads a domain's own public homepage; it stores nothing.

πŸ“œ Data & attribution

DNS via Google Public DNS-over-HTTPS; homepage data from the target domain's own site. Public data, composed and returned; nothing stored.

Part of one suite of keyless, agent-ready composers by the same developer: