{
"count": 1,
"items": [
{
"input": "google.com",
"domain": "google.com",
"status": "ok",
"checkedAt": "2026-11-19T03:23:07Z",
"mx": {
"found": true,
"nullMx": false,
"records": [
{
"host": "smtp.google.com",
"priority": 10,
"resolves": true,
"isCname": false
}
]
},
"spf": {
"found": true,
"record": "v=spf1 include:_spf.google.com ~all",
"qualifierAll": "softfail",
"mechanisms": [
{
"qualifier": "pass",
"mechanism": "include",
"value": "_spf.google.com"
},
{
"qualifier": "softfail",
"mechanism": "all",
"value": null
}
],
"dnsLookups": 1,
"lookupLimit": 10,
"lookupLimitExceeded": false,
"includes": [
"_spf.google.com"
],
"errors": []
},
"dmarc": {
"found": true,
"record": "v=DMARC1; p=reject; rua=mailto:[email protected]",
"policy": "reject",
"subdomainPolicy": null,
"pct": 100,
"rua": [
"mailto:[email protected]"
],
"ruf": [],
"adkim": "r",
"aspf": "r",
"source": "_dmarc.google.com",
"inheritedFrom": null
},
"dkim": {
"found": false,
"selectorsChecked": [
"google",
"selector1",
"selector2",
"default",
"k1",
"s1",
"mail"
],
"keys": []
},
"mtaSts": {
"txtFound": true,
"id": "20210803T010101",
"policyFetched": true,
"mode": "enforce",
"maxAge": 86400,
"mx": [
"smtp.google.com",
"aspmx.l.google.com",
"*.aspmx.l.google.com"
],
"error": null
},
"tlsRpt": {
"found": true,
"record": "v=TLSRPTv1;rua=mailto:[email protected]",
"rua": [
"mailto:[email protected]"
]
},
"bimi": {
"found": true,
"record": "v=BIMI1; l=; a=; lps=googlewallet-noreply-bimi",
"logoUrl": null,
"vmcUrl": null
},
"score": 100,
"grade": "A",
"issues": [
{
"severity": "info",
"area": "mx",
"issue": "Only one MX record, so there is no backup mail server.",
"fix": "Add a second MX with a higher priority number if your provider offers one."
},
{
"severity": "info",
"area": "spf",
"issue": "SPF ends with '~all' (softfail). This is common and acceptable when DMARC is enforced.",
"fix": "Use '-all' once you are sure every sender is listed."
},
{
"severity": "info",
"area": "dkim",
"issue": "No DKIM key found for the common selectors (google, selector1, selector2, default, k1, s1, mail). A domain can use any selector name, so this does not prove DKIM is missing.",
"fix": "Pass your selector in dkimSelectors to check it."
}
],
"issueCount": 0,
"normalized": false
}
]
}
curl --location --request GET 'https://zylalabs.com/api/15068/dmarc+spf+mx+lookup+api/39889/dmarc+spf+mx+lookup+api?domains=google.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 DMARC SPF MX Lookup 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.
One call per domain list returns MX, SPF, parsed, DNS lookups against the limit of 10, includes resolved, DMARC policy and reports, DKIM keys, MTA-STS, TLS-RPT, BIMI, a score and a plain fix list.
One call per domain list returns MX, SPF (parsed, DNS lookups against the limit of 10, includes resolved), DMARC policy and reports, DKIM keys, MTA-STS, TLS-RPT, BIMI, a score and a plain fix list.
Up to 100 results per request, depending on the endpoint.
Every request collects live data from the public source. Identical requests may be served from a cache for up to 6 hours.
List parameters accept several values separated by commas, for example: london,paris.
The endpoint accepts these query parameters, all optional: domains, domain, dkimSelectors. Domains: Domains to check, up to 50 per call, bare names (no https, no mailbox). The API answers 400 above 50 (the API checks the first 50). Each row shows your input and the checked (lowercased) domain; duplicates are checked once and listed in duplicateInputs. Several values: comma separated. Domain: Optional: exactly one domain. It is never split: a value with spaces, commas, semicolons or new lines returns one invalid_format row. Use domains for a list. DkimSelectors: Optional.
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