Domain & IP Lookup
MX records for any domain, resolved live by the free tool. The IP half of that name is a roadmap, and this page says so before you build on it.
Two halves of the name, one of them real.
A domain lookup asks whether a name can receive mail. An IP lookup would ask who is behind an address. They are different questions, and only the first one ships today.
Domain
Does this name accept mail at all? One DNS query answers it: the mail exchanges for the domain, and whether it has an address at all when it has no mail route.
- A live DNS query — nothing is sent to the domain.
- MX first, then A, then AAAA if it has to.
- Free and unauthenticated. No key, no credits.
IP address
An IP lookup is not what we sell yet.
When it ships it will answer a different question from a domain lookup: not “does this domain accept mail” but “who is behind this address”. Until then the domain lookup above is the honest answer.
Two flows, one of them shipped.
The first chart is the code that runs when you press Look up — every branch, so you can predict the response. The second is a proposal drawn in dashes.
DNS resolution, drawn
Normalization happens locally. Then one MX query decides whether the domain can receive mail — and when it cannot, the address records get their turn before the lookup fails.
scroll sideways — the fallback branch sits off the edge
Every branch above traces to the shipped resolver. The provider tag is matched by the same step; the free response returns the records and the two booleans.
IP lookup, sketched
The shape an IP lookup would have to take — parse, validate, resolve ownership — with no data source attached, because none is wired.
scroll sideways to see the whole sketch
proposed — not yet available. The stages are generic on purpose: there is no endpoint, no response shape and no verdict vocabulary for IP lookups in this codebase.
What the answer means, and what it does not.
Four fields come back, and each one stops somewhere. Hover a row to trace it to the response.
GET https://api.multivalidator.io/api/v1/tools/mx?domain=example.com
{"success": true,"data": {"domain": "example.com","mxRecords": ["mx1.example.com"],"hasMxRecord": true,"hasARecord": true}}
No API key. Anonymous traffic is rate limited, and a 429 carries an X-RateLimit-Reset header.
400 · INVALID_REQUEST — “A valid domain is required.”
Field map · hover to trace
- domainstring
tells you The value that was actually queried, after normalization — scheme, path, port and trailing dot removed, and the domain half kept when you paste an email address.
does not It is not proof the domain exists. Normalization is string work, and it happens before any query.
- mxRecordsstring[]
tells you The exchanges that accept mail for the domain, sorted by priority. An empty array is a real answer, not a failure.
does not It does not mean a mailbox exists, and it is not a delivery guarantee — a record can point at a host that refuses everyone.
- hasMxRecordboolean
tells you Whether the domain has mail routing at all — somewhere for mail to be accepted.
does not It says nothing about a specific address. This is the field people over-read.
- hasARecordboolean
tells you Whether the domain has an A record, or an AAAA record when A comes back empty — it is on the internet somewhere.
does not It is not a mail route. Plenty of domains are addressable and accept no mail.
One lookup, every reason.
The same four fields, as the checks they are — one click each to read what the answer was and where it stops. Nothing is collapsed behind a second page, and nothing is expanded into a wall of text.
illustrative response
mx1.example.com
The exchange that accepts mail for this domain, returned in priority order. Whether that server accepts a given address is a different question — and one MX records cannot answer.
- mail routing
- true
- address record
- true
Nothing here reads a mailbox, and nothing is sent to the domain. The lookup reports what the domain publishes; the checks beside it report where each answer stops.
Scheme, path, port and trailing dot are stripped before the query, and a pasted email address is reduced to its domain half. It is string work done ahead of the lookup, so it is not proof the domain exists.
response · domain: "example.com"
States shown for the response above. A domain with no MX records reads “none published”; a domain with no address record reads “not found”. Both are answers, not errors.
What is domain & IP lookup?
Domain and IP lookup is the process of retrieving technical information associated with a domain name or an IP address. A domain lookup reads the DNS records a domain publishes; an IP lookup starts from an address and returns information about the network it belongs to, where a data source makes it available.
MultiValidator provides the domain half today: one free, unauthenticated DNS query for a domain’s mail-routing records and whether it has an address record. The IP half is drawn, labelled and explained as a roadmap above — it has no endpoint behind it, so nothing on this page reads an address.
Run the domain half in the free MX lookup — no account, no credits.
How domain lookup works.
Four moves, in order. Every one of them is visible in the response — there is no hidden second lookup behind the answer.
Normalize the domain
The input is trimmed and rewritten: scheme, path, port and trailing dot removed, and a pasted address reduced to its domain. No network call has happened yet.
Query the mail records
One live MX query returns the exchanges that accept mail, sorted by priority. An empty answer is a result — the domain publishes no mail route.
Query address records
The lookup tries A, then AAAA when A comes back empty, and records whether the domain is addressable at all.
Return the answer as JSON
You get the exact domain that was queried, its MX records, and the two presence booleans — small enough to log, cache or diff between runs.
What a lookup can tell you.
The categories below are the supported ones, and the list is exactly as long as the response is. Anything not listed here — WHOIS ownership, NS, TXT or CNAME records, an address lookup — is not part of this lookup.
DNS records
Inspect the mail-routing records a domain publishes, in priority order.
Mail routing
See whether a domain publishes somewhere for mail to be accepted at all.
Address records
Check whether a domain has an address record — A, or AAAA when A is empty.
Structured response
Read the queried domain back, with the two presence booleans, as JSON any job can consume.
Where a lookup earns its keep.
The jobs the free query does — the same answer the API returns, so the tool and the integration never diverge.
Troubleshooting mail delivery
Find out whether a domain publishes mail routing before you blame the inbox, and see which hosts it points its mail at.
Pre-send list hygiene
Screen the domains on a list for a mail route before spending the first credit on the addresses inside them.
Developer workflows
Call the endpoint from onboarding flows, dashboards, uptime checks and data-enrichment jobs.
Infrastructure review
Compare a domain's mail hosts and address records against the setup you expected to see.
Technical support
Give support teams a structured, shareable view of a domain's mail and address configuration.
Looking for a different kind of answer? Email validation probes the mailbox itself, phone validation resolves numbers, the IIN/BIN checker reads card issuers, and the API documentation covers every endpoint.
Domain lookup API.
Integrate the domain lookup directly into your application. Send a domain and receive structured results you can use in dashboards, internal tools, automation, monitoring and data-enrichment workflows.
The endpoint is a plain GET — no key, no credits — and it returns the same answer the free tool shows. For the whole contract, including rate limits and error codes, read the API documentation.
$ curl "https://api.multivalidator.io/api/v1/tools/mx?domain=example.com"{ "success": true, "data": { "domain": "example.com", "mxRecords": ["mx1.example.com"], "hasMxRecord": true, "hasARecord": true }}
Known limits
A domain with MX records can still reject every mailbox on it.
Records change. What resolves now may not resolve in an hour — DNS is cached and TTL-bound.
Caching and propagation mean two resolvers can answer differently for a while. The record is the same; the caches are not.
A published record is not proof of ownership. This lookup does not query WHOIS, and no DNS record names the legal owner of a domain.
We read public DNS. Nothing is sent to the domain and no mailbox is probed.
The answer is only as good as the DNS data the resolver was given. There is no second source behind it.
The MX lookup is free and unauthenticated. Proving a specific mailbox is the one-credit SMTP probe inside email validation, and that is a different question from the one this page answers.
Domain lookup FAQ.
The questions this page actually answers — including the ones where the answer is no.
A domain lookup retrieves the technical information a domain publishes about itself. In MultiValidator's case that is the domain's mail-routing records and whether it has an address record at all.
Related free tools
Each tool checks one layer. To run the full pipeline — MX lookup, live SMTP probe and catch-all detection with a reason and a score — use the API.
Stop mailing ghosts.
Start with free credits. No card, no call, no “book a demo”.