{
"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'
注册后,每个开发者都会被分配一个个人 API 访问密钥,这是一个唯一的字母和数字组合,用于访问我们的 API 端点。要使用 DMARC SPF MX 查询 API 进行身份验证,只需在 Authorization 标头中包含您的 bearer token。
| 标头 | 描述 |
|---|---|
授权
|
必需
应为 Bearer access_key. 订阅后,请查看上方的"您的 API 访问密钥"。
|
每个域名列表的一个调用返回 MX SPF(解析的 DNS 查询,限制为 10 包括解析结果) DMARC 策略和报告 DKIM 密钥 MTA-STS TLS-RPT BIMI 评分和一个简单的修复列表
每个请求最多可返回100个结果,具体取决于端点
每个请求从公共源收集实时数据 相同的请求可以从缓存中服务长达6小时
参数列表接受由逗号分隔的多个值,例如:伦敦,巴黎
该端点接受这些查询参数,均为可选:domains、domain、dkimSelectors。Domains:要检查的域名,每次调用最多 50 个,裸名称(不带 https,不带邮箱)。如果超过 50 个,API 将返回 400(API 仅检查前 50 个)。每行显示您的输入和检查的(小写)域名;重复项只检查一次,并列在 duplicateInputs 中。多个值:以逗号分隔。Domain:可选:恰好一个域名。它不会被拆分:带有空格、逗号、分号或换行符的值返回一个 invalid_format 行。使用 domains 表示一个列表。DkimSelectors:可选。