The DNS MX Records Extractor API is designed to quickly and reliably obtain Mail Exchange (MX) records associated with any domain. When a query is made, the API returns an ordered list of the email servers configured for that domain, including both the server name and its corresponding priority. These records are essential for determining which servers should receive emails addressed to that domain, making this API indispensable for developers, system administrators, and services that need to validate or audit email configurations.
The API is perfect for integration into monitoring dashboards, DNS diagnostic tools, domain validators, corporate email onboarding solutions, and other platforms where ensuring proper email delivery is required. Furthermore, as it is a RESTful API that responds in structured JSON format, it can be easily integrated into any web or mobile application.
To use this endpoint, you must specify a domain in the parameter.
MX Check - Endpoint Features
| Object | Description |
|---|---|
domain |
[Required] Indicates a domain |
[{"priority": 1, "value": "mta5.am0.yahoodns.net."}, {"priority": 1, "value": "mta6.am0.yahoodns.net."}, {"priority": 1, "value": "mta7.am0.yahoodns.net."}]
curl --location --request GET 'https://zylalabs.com/api/8461/dns+mx+records+extractor+api/14828/mx+check?domain=yahoo.com' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The MX Check endpoint returns an ordered list of Mail Exchange (MX) records for a specified domain. This includes the mail server names and their corresponding priorities, which indicate the order in which mail servers should be contacted for email delivery.
The key fields in the response data include "server" (the mail server's hostname) and "priority" (an integer indicating the server's priority for email delivery). These fields help determine the correct routing of emails for the domain.
The response data is structured in JSON format, typically containing an array of objects. Each object represents an MX record with fields for "server" and "priority," allowing for easy parsing and integration into applications.
The MX Check endpoint provides information about the mail servers associated with a domain, including their names and priorities. This data is crucial for verifying email configurations and ensuring proper email delivery.
Users can customize their data requests by specifying the domain they wish to check in the endpoint parameter. This allows for targeted queries to retrieve MX records for specific domains of interest.
Typical use cases for the MX Check data include validating email configurations, integrating into monitoring dashboards, auditing DNS settings, and assisting in corporate email onboarding processes to ensure reliable email delivery.
Data accuracy is maintained through regular updates and checks against authoritative DNS servers. This ensures that the MX records returned reflect the most current configurations for the specified domains.
If the MX Check endpoint returns partial or empty results, it may indicate that no MX records are configured for the domain or that the domain does not exist. Users should verify the domain's validity and check DNS settings for potential issues.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Service Level:
100%
Response Time:
806ms
Service Level:
100%
Response Time:
1,939ms
Service Level:
100%
Response Time:
1,267ms
Service Level:
100%
Response Time:
1,959ms
Service Level:
100%
Response Time:
825ms
Service Level:
100%
Response Time:
765ms
Service Level:
100%
Response Time:
278ms
Service Level:
100%
Response Time:
341ms
Service Level:
100%
Response Time:
100ms
Service Level:
100%
Response Time:
782ms
Service Level:
100%
Response Time:
140ms
Service Level:
100%
Response Time:
2,410ms
Service Level:
100%
Response Time:
2,120ms
Service Level:
100%
Response Time:
56ms
Service Level:
100%
Response Time:
85ms
Service Level:
100%
Response Time:
66ms
Service Level:
100%
Response Time:
58ms
Service Level:
100%
Response Time:
8,111ms
Service Level:
100%
Response Time:
238ms
Service Level:
100%
Response Time:
1,000ms