Enter a domain, URL, IP, email, or record and get a focused result without setup.
MX Record Lookup
Enter a domain to find its published mail exchangers, preference values, and expected delivery order.
GET /v1/dns?domain=example.com&type=MX
Run the check, then ship the workflow
Use the browser tool for a fast answer, then move the same logic into scripts, monitoring, or product flows when it becomes repeatable.
Outputs highlight statuses, risks, records, and next actions instead of raw provider noise.
Use the request and response examples to turn a one-off check into an API call or recipe.
Used by people at these companies
What this tool helps you decide
Each page is shaped around a practical operational question, not just a raw lookup.
See the current DNS, registration, security, pricing, or reputation evidence.
Compare the result with related checks so the next move is easier to trust.
Copy examples, open linked tools, or move into API documentation when you need scale.
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
Check live service health and documented failure responses before you integrate.
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
Authenticated endpoints use API keys with clear credit costs before you call them.
Start with 1,000 free credits every month. Need more? Pick a monthly plan or buy a one-time pack.
Key Features
Retrieve the MX records currently published for the domain.
See each preference value and which mail exchangers should be tried first.
Identify missing records, duplicate priorities, and lookup errors quickly.
Example request
GET /v1/dns?domain=example.com&type=MX
Example response
{
"domain": "example.com",
"record_type": "MX",
"records": [
{ "data": "mail.example.com", "priority": 10, "ttl": 3600 }
],
"status": "success"
}
Built on the same API
The browser experience previews DomScan's structured endpoints, so teams can validate a use case before writing code.
Frequently asked questions
A lower preference value has higher priority. Sending mail servers normally try the lowest-value available exchanger first.
Yes. Mail servers may choose between exchangers with equal preference, which can distribute delivery across multiple hosts.
No. MX records show where mail should be delivered. They do not confirm that the server accepts mail, that a mailbox exists, or that delivery will succeed.

