[{"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/8463/dns+mail+fetcher+api/14826/mx+check?domain=yahoo.com' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the DNS Mail Fetcher API simply include your bearer token in the Authorization header.
| 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.
(Save 2 months with annual billing 🎉)
Trusted by leading companies
The DNS Mail Fetcher 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.
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.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
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.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund