Docs/Sources/MX Lookup

MX Lookup

Get MX records for a domain

OperationalCredits 10 per callp50 233msDomain Data

Overview

Pass any domain name to run a live DNS lookup for its mail configuration. The response returns the queried domain and an array of MX entries, showing each mail exchange server hostname paired with its priority routing integer.

Live Test MX Lookup Source →

Formula

One function covers the whole catalog: the first argument names the source, the rest are its inputs, and the "field" pair says which single value lands in the cell. Formulas covers the grammar that applies to all of them.

=VERVE("mxlookup", A2, "field", "mx.0.priority")

A2 holds the domain you are looking up. Drag the formula down and each row resolves on its own.

With literal values

Nothing has to come from a cell — typed values work the same way.

=VERVE("mxlookup", "yahoo.com", "field", "mx.0.priority")

Inputs

Required inputs are positional, in the order below. Everything else is passed as a "name", value pair after them — the same shape as SUMIFS. Premium inputs are accepted on every plan but only take effect on plans that include them.

InputTypeWhere it goesDescription
domainRequiredstringargument 2 (A2)The domain you want to get the MX records for (e.g. yahoo.com)
domain

What lands in your sheet

The "field" pair is what makes the formula resolve to one cell. Its value is a dot-path from the table below, so swapping it is how you pull a different value — one formula per column.

Seeing everything at once

Drop the "field" pair and the formula returns the whole response instead: two columns, field name on the left and value on the right, spilling from the cell you typed in.

=VERVE("mxlookup", A2)
Good for exploring, not for filling down

The second row's table would land on top of the first's, and every cell after the first reads #REF! (#SPILL! in Excel). Keep one per sheet, or name a field, and leave the cells below and to the right empty.

Response fields

Paths are relative to data. Each one is exactly what the "field" pair accepts, so swapping it is how you pull a different value into a cell. On a plan without a Premium field the cell reads #PREMIUM(field) rather than a value, so a locked field never looks like a real answer.

Use as "field"TypeExample cell valueDescription
domainstringyahoo.comThe domain name that was queried for MX records
mxarray[3]Array of MX records for the domain
mx.0.prioritynumber1Priority value of the MX record for routing
mx.0.exchangestringmta7.am0.yahoodns.netMail exchange server hostname for receiving emails

Filling a whole column

Both platforms make one batched call for a column rather than one request per cell, and both cost the same — 10 credits per row looked up. How you write it differs, because the two runtimes batch at different points.

Rows 2–100 in one call
=VERVE("mxlookup", A2:A100, "field", "mx.0.priority")

In Google Sheets, give the arguments ranges and the answers spill down from the cell you typed in. Custom functions there run synchronously and in isolation, so dragged cells cannot be coalesced — the range form is how a column becomes one call. The "field" pair is required here: a per-row two-column table has nowhere to spill. Use a full column per input (A2:A100, not A2) — a single-cell reference is read as row 1 only and the rest of the column comes back blank.

In Excel, type the formula once and fill down — no range form and none needed, because its runtime is asynchronous and the add-in coalesces the calls a fill produces into a single batched request. Do not hand VERVE.CALL a range: Excel flattens it into positional arguments, so A2:A100 arrives as a hundred separate arguments and the cell reads #ERR rather than filling.

Either way, column A holds your domain values and the answers land beside them, one row each, blank rows skipped.

When a cell doesn't fill

A failed lookup returns readable text starting with #ERR rather than a spreadsheet error, because Excel cannot show a custom message on a real error — you would get a bare #VALUE! with no reason. The trade-off is that IFERROR() will not catch it; test with LEFT(cell, 4) = "#ERR" instead. Error handling covers the rest.

Cell readsWhat happened
#ERR Not connectedNo API key saved. Open the side panel and connect your account.
#ERR Replace <name> with a cell or valueA preview formula was copied as-is. Swap the placeholder for a cell reference.
#ERR No "x" in mxlookupAn option name this source does not take. The message lists the ones it does.
#ERR No data point "…"The "field" path is not in the response. Check it against the table above.
#PREMIUM(field)The field exists but your plan does not include it.
#ERR Out of creditsThe cycle's credits are spent. Usage resets on your billing date.

Before the formula works

The add-in reads the API key you saved once in the side panel — the key never goes in the formula, so a shared sheet does not leak it and a collaborator without access simply sees the last calculated values.

  1. Install the add-in for Google Sheets or Excel.
  2. Open the side panel and sign in, or paste a key from your dashboard.
  3. Type the formula above into any cell.

Use cases

Signup Email Validation
To stop fake signups, authentication workflows check MX records to confirm the registrant's email domain can actually accept incoming messages.
Domain Migration Auditing
DevOps engineers track exchange hostnames and priority numbers before and after DNS changes to verify mail traffic directs to new servers.
Cold Outreach Deliverability
Sales outreach software verifies that recipient domains have active mail servers before scheduling outbound campaign sequences to protect sender reputation.
Mail Provider Detection
Identify whether a prospect uses Google Workspace, Microsoft 365, or self-hosted infrastructure by parsing the returned exchange server hostnames.

Other ways to use MX Lookup

Set up MX Lookup on VerveSheets, or reach the same source a different way. Your VerveSheets account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →
Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →
Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →

More in Domain Data:

Was this page helpful?