Check a domain's email DNS (MX, SPF, DKIM, DMARC)
curl --request GET \
--url https://my.server.express/api/v1/public/email-dnsconst options = {method: 'GET'};
fetch('https://my.server.express/api/v1/public/email-dns', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://my.server.express/api/v1/public/email-dns"
response = requests.get(url)
print(response.text){
"success": true,
"data": {
"domain": "<string>",
"mx": [
{
"priority": 123,
"host": "<string>"
}
],
"spf": "<string>",
"dmarc": "<string>",
"dkim": [
{
"selector": "<string>",
"found": true
}
],
"findings": [
{
"level": "error",
"text": "<string>"
}
]
}
}{
"success": false,
"error": "<string>"
}{
"success": false,
"error": "<string>"
}{
"success": false,
"error": "<string>"
}Public Tools
Check a domain's email DNS (MX, SPF, DKIM, DMARC)
One DNS-only report on whether a domain is set up to send mail convincingly, with plain-English findings worst first. DKIM is probed on a fixed list of common selectors (default, google, selector1, selector2, k1, mail, s1, dkim), since DKIM has no way to list them. Nothing connects to a mail server. Limited to 20 requests per minute per IP.
GET
/
v1
/
public
/
email-dns
Check a domain's email DNS (MX, SPF, DKIM, DMARC)
curl --request GET \
--url https://my.server.express/api/v1/public/email-dnsconst options = {method: 'GET'};
fetch('https://my.server.express/api/v1/public/email-dns', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://my.server.express/api/v1/public/email-dns"
response = requests.get(url)
print(response.text){
"success": true,
"data": {
"domain": "<string>",
"mx": [
{
"priority": 123,
"host": "<string>"
}
],
"spf": "<string>",
"dmarc": "<string>",
"dkim": [
{
"selector": "<string>",
"found": true
}
],
"findings": [
{
"level": "error",
"text": "<string>"
}
]
}
}{
"success": false,
"error": "<string>"
}{
"success": false,
"error": "<string>"
}{
"success": false,
"error": "<string>"
}