Whether a lead's mail runs on Google Workspace, Microsoft 365 or sits behind a Proofpoint gateway changes a lot: how your messages get filtered, which deliverability advice applies, and — if you sell anything that touches email — whether they are a prospect at all. That answer has always been public, in the domain's DNS. It just wasn't in your list.

DNS Query is a new list enrichment that puts it there. Pick a record type and a field, and it writes the answer onto every lead:

  • MX — the mail servers, plus a plain provider name in a second field: Google Workspace, Microsoft 365, Proofpoint, Mimecast, Zoho Mail and around forty others. A provider we don't recognise is stored as its server domain, so you can still filter and group by it.
  • TXT — SPF records, DMARC policy (query _dmarc), or the verification tokens companies leave behind when they sign up for software. A "record exists" check for atlassian-domain-verification tells you who uses Atlassian.
  • NS — who hosts their DNS: Cloudflare, Route 53, GoDaddy.
  • A, AAAA, CNAME, SOA, CAA, SRV — for anything else you want to know.

Results can be stored as the full list, the first value, a count, or a simple true/false. For an email address the lookup uses the exact domain after the @, since that is where mail is actually routed; without one, it falls back to the lead's company domain.

It costs nothing — no connects, just DNS. Leads at the same company share one lookup. Need several records? Add the enrichment more than once.

It sits with the other enrichments on any list, and is on the API as an automation with enrichment_type: "dns_query".