Skip to main content

Email Authentication Posture API

developer
GET/v1/domain/email-auth

Summarizes published SPF, DMARC, common DKIM selectors, MTA-STS, TLS-RPT and BIMI records in a DNS-derived score and grade. This REST endpoint checks record presence and selected policy values; it does not test inbox placement or validate a signed message.

What It Does

Queries TXT records and probes five DKIM selectors: google, selector1, selector2, s1 and default. Returns each component, a 0–100 posture score, grade and recommendations. MTA-STS, TLS-RPT and BIMI checks here only observe TXT record presence; use their dedicated endpoints for deeper validation. An absent result can reflect DNS lookup failure, and an undiscovered DKIM selector does not prove that mail is unsigned.

Why It's Useful

Collect a compact authentication baseline before investigating individual email policies or reviewing a domain with its mail administrator.

Use Cases

Email Administrator

Email Authentication Baseline

Collect published authentication settings before a sender-policy review.

Identify which individual checks need further investigation.

Parameters

NameLocationTypeRequiredDescription
domainquerystringRequiredDomain whose published email authentication records should be checked.Example: example.com

Response Fields

Result fields below are inside the JSON data object. Any row named meta describes the sibling response metadata object. See response and error handling for status codes and error responses. Optional observations may be absent or null; inspect warnings and partial-failure fields before treating a missing result as a negative finding.

FieldTypeDescription
domainstringNormalized queried domain.
scorenumber0–100 heuristic: SPF up to 25, DMARC 35, discovered DKIM 20, MTA-STS 10, TLS-RPT 5, BIMI 5.
gradestringA+ (95+), A (85+), B (70+), C (50+), D (30+), otherwise F.
spfobjectpresent, qualifier (+all, ~all, -all or none), and observed record.
dmarcobjectpresent, policy, pct and observed record.
dkimobjectpresent and selectors_found from the five probed selectors.
mta_stsobjectpresent: whether an MTA-STS TXT record was discovered.
tls_rptobjectpresent: whether a TLS-RPT TXT record was discovered.
bimiobjectpresent: whether a default-selector BIMI TXT record was discovered.
recommendationsstring[]Suggested next steps based on the observations.

Code Examples

Replace YOUR_API_KEY with your API key. This endpoint requires the developer plan or higher; see plans and usage limits.

cURL
curl --request GET 'https://api.edgedns.dev/v1/domain/email-auth?domain=example.com' \
  --header "Authorization: Bearer YOUR_API_KEY"
JavaScript
const response = await fetch(
  "https://api.edgedns.dev/v1/domain/email-auth?domain=example.com",
  {
    "method": "GET",
    "headers": {
      "Authorization": "Bearer YOUR_API_KEY"
    }
  }
);

if (!response.ok) {
  throw new Error(`EdgeDNS returned HTTP ${response.status}`);
}
const data = await response.json();
console.log(data);
Python
import requests

response = requests.request(
    'GET',
    "https://api.edgedns.dev/v1/domain/email-auth?domain=example.com",
    headers={'Authorization': 'Bearer YOUR_API_KEY'},
    timeout=60,
)
response.raise_for_status()
data = response.json()
print(data)

Read the full Email Authentication Posture guide

Learn the concepts, choose a practical workflow, and interpret the observations from Email Authentication Posture before acting on them. Use the documented REST request for this operation.

Read the guide →

    Related Endpoints

    External References

    Learn more about the standards and protocols behind this endpoint.

    Email Authentication Posture API Reference | EdgeDNS