Mail servers · Priority · Null MX
MX API
Where does this
domain receive mail?
Build a mail-routing check into your app. Send a domain and get its published mail servers in priority order, with an explicit record when the domain accepts no mail.
Complete mail-routing results on every plan.
Look up a domain's mail servers
Try it
One domain. Its published route.
Mail servers.
Ready for your app.
Read the complete request and JSON together. These recorded examples show a list of servers, a single server and a domain that explicitly declines mail. Records can change.
Read the preferred server and its backups.
Lower priority numbers are preferred. This complete Gmail response lists all five published mail servers.
Request
curl "https://api.parseapi.com/mx/gmail.com" \
-H "X-API-Key: YOUR_API_KEY" \
-H "X-API-Version: 2.2.0"Example response
Read the answer
The route.
And what it means.
Use the server list to inspect a domain's mail setup or diagnose a routing problem. Keep the published route separate from whether a specific inbox exists.
Check an email address- Lower numbers are preferred
- A server with priority 5 is preferred over one with priority 10. Equal priorities have equal preference; alphabetical order in the response is for consistent output.
- A dot explicitly declines mail
- A single
{ "priority": 0, "host": "." }is a null MX record. The domain publishes that it accepts no mail. - An empty array means no MX records
- Mail can still fall back to the domain's A or AAAA address. An empty
mx: []is a different answer from an explicit refusal.
Coverage & freshness
Mail routes change.
Your check follows.
Look up public domain names, including exact subdomains and international names. Each answer reflects the published DNS records available to the lookup.
- Bounded by DNS lifetime
- Recent answers can be reused for up to one hour. Shorter DNS lifetimes expire sooner, and an expired answer requires a fresh check.
- An unavailable check stays an error
- Temporary DNS failures return HTTP 503. Follow Retry-After before retrying; keep the failure separate from an empty result.
From lookup to your app
One key.
Your way to build.
Copy the HTTP request, use an SDK in your language, or ask an agent through MCP. Read the domain, then iterate through the mx array.
HTTP, SDKs and MCP
The reference covers inputs, authentication, complete responses and errors. Mail-server records and priorities come back in the ordinary lookup; no extra detail request is needed.
Before you build.
What does an MX lookup return?
The exact domain checked and its published mail servers. Each entry has a host and a numeric priority. Lower numbers are preferred; equal-priority hosts are listed alphabetically. The complete result is included on every plan. Deep adds no further mail-routing detail.
What is a null MX?
A single record with priority 0 and host "." means the domain explicitly accepts no mail. That record stays in the mx array so your app can recognize the published refusal.
Does an empty mx array mean mail cannot be delivered?
An empty array means no MX records were found. Mail can still use the domain's A or AAAA address as a fallback. Keep an empty array separate from an explicit null MX. Neither a server list nor an empty array proves that a particular inbox exists.
How fresh are the answers?
Answers are reused within their DNS lifetime, capped at one hour. Shorter lifetimes expire sooner. An expired answer needs a new lookup; a failed refresh returns an error instead of an old server list.
What happens if DNS is unavailable?
A temporary DNS failure returns HTTP 503 with code dns_resolution_failed. Honor Retry-After, allow at most two retries with jitter, and set a total deadline. Treat the failure as an unavailable check rather than an empty mail-server list.
Can I check a subdomain or an international domain?
Yes. Send the exact hostname, without a URL or email address. Subdomains are checked as supplied. International names can use Unicode or ASCII IDNA form; the response domain is lowercased and IDNA-encoded.
How is MX priced?
Each lookup uses one request from your shared ParseAPI allowance. All mail-server records and priorities are included on every plan. Email mailbox verification is a separate operation with its own allowance.
MX API pricing
Build mail routing in.
One lookup uses one API request from your shared ParseAPI allowance. Every plan includes the complete mail-server list and priorities.
Free
Create your API key
Complete MX lookups
Room to grow
See plans
Complete MX lookups