Email Authentication Posture: Understand and Use the Results
DNS-derived email authentication posture in one call
Email authentication posture: what published records can tell you
Email authentication posture is a review of the policies and signing keys a domain publishes for mail receivers. It helps an administrator spot missing configuration and decide which individual checks need attention. It does not establish whether a particular message was authenticated or delivered to an inbox.
The distinction matters because publishing a policy and correctly using it are separate tasks. A domain can publish a valid signing key while an application sends unsigned messages. A strict policy can also disrupt legitimate senders whose authenticated domains do not align with the address recipients see.
Useful evidence includes:
Sender Policy Framework (SPF): the published policy for authorized sending infrastructure.
DomainKeys Identified Mail (DKIM): discoverable public keys used to verify message signatures.
Domain-based Message Authentication, Reporting, and Conformance (DMARC): alignment rules, policy preferences, and reporting destinations.
Transport and reporting records: signals such as mail transport policy and transport-security reporting.
A publication review answers questions such as which policies are present and where deeper validation is needed. It cannot discover every custom DKIM selector or prove that all outbound systems use the intended configuration. Unknown or missing results require investigation rather than an automatic conclusion that no authentication exists.
Use the findings alongside real message headers, sender inventories, and reports from the mail platform. Review changes with the people responsible for sending mail before increasing enforcement. The DMARC specification explains how policy publication relates to authentication and alignment.
The Email Authentication Posture endpoint, in plain language
DNS-derived email authentication posture in one call
Collect a compact authentication baseline before investigating individual email policies or reviewing a domain with its mail administrator.
What is actually happening when you call it
Queries TXT records and probes five DKIM (DomainKeys Identified Mail) selectors: google, selector1, selector2, s1 and default. Returns each component, a 0–100 posture score, grade and recommendations. MTA-STS (Mail Transfer Agent Strict Transport Security), TLS-RPT (TLS (Transport Layer Security) Reporting) and BIMI (Brand Indicators for Message Identification) checks here only observe TXT record (text record) presence; use their dedicated endpoints for deeper validation. An absent result can reflect DNS (Domain Name System) lookup failure, and an undiscovered DKIM selector does not prove that mail is unsigned.
Why this specific tool matters
Choose a task: Email Authentication Baseline. Collect published authentication settings before a sender-policy review.
Run the Email Authentication Posture request below and retain the input and observed result. Before changing configuration, compare the relevant fields with the value or policy you expected. Use the Email Authentication Posture reference to check the field definitions and supported options.
Available on the developer plan. The technical details: `GET /v1/domain/email-auth`.
When would I actually use this?
Email Authentication Baseline
Collect published authentication settings before a sender-policy review.
Use the finding: Identify which individual checks need further investigation.
Call this endpoint through REST
This is a REST-only GET endpoint and is not registered as a tool on the dedicated MCP server. Use its documented query parameters and the request example below. See the authentication guide for API-key setup.
The dedicated MCP server is available on every plan. Individual tool access and request limits depend on your plan. Management categories and endpoints disabled for the tool catalog are not exposed through MCP.
The technical way: call it from code
This Email Authentication Posture request uses the example inputs from its API contract. Replace YOUR_API_KEY with a key on the developer plan or higher; adapt the target to your task.
curl --request GET 'https://api.edgedns.dev/v1/domain/email-auth?domain=example.com' \
--header "Authorization: Bearer YOUR_API_KEY"Prepare inputs for Email Authentication Posture
Start with the inputs below. Keep the same hostname, path, and options when comparing Email Authentication Posture observations. The API reference contains the complete parameter contract, optional settings, and access requirements.
| Field | Type | Required? | What it means | Example |
|---|---|---|---|---|
domain | string | Yes | Domain whose published email authentication records should be checked. | example.com |
Interpret Email Authentication Posture findings
Read these fields alongside the full response from your Email Authentication Posture check. A missing value or failed lookup is different from a passing result. Keep returned errors and confidence or cache metadata when available; do not replace missing evidence with a successful default. See the complete response reference for additional fields.
| Field | Type | What you'll see in it |
|---|---|---|
domain | string | Normalized queried domain. |
score | number | 0–100 pattern-matching rules: SPF (Sender Policy Framework) up to 25, DMARC (Domain-based Message Authentication, Reporting and Conformance) 35, discovered DKIM (DomainKeys Identified Mail) 20, MTA-STS (Mail Transfer Agent Strict Transport Security) 10, TLS-RPT (TLS (Transport Layer Security) Reporting) 5, BIMI (Brand Indicators for Message Identification) 5. |
grade | string | A+ (95+), A (85+), B (70+), C (50+), D (30+), otherwise F. |
Words you might be wondering about
DNS (Domain Name System) — The internet's address book. When you type a website name, DNS turns it into the actual numeric address computers use to find each other.
TXT record (text record) — A DNS entry that holds plain text. Used for things like proving you own a domain or listing who can send email as you.
SPF (Sender Policy Framework) — A list, published in your DNS, of which servers are allowed to send email pretending to be you. Helps stop spammers from forging your address.
DKIM (DomainKeys Identified Mail) — A digital signature added to every email you send. The receiving mail server checks the signature to make sure the message really came from you and was not changed in transit.
DMARC (Domain-based Message Authentication, Reporting and Conformance) — An email rulebook you publish in your DNS. It tells receiving servers what to do with email that fails SPF or DKIM checks — ignore it, send it to spam, or block it entirely.
BIMI (Brand Indicators for Message Identification) — A standard that lets your company logo appear next to your emails in supported inboxes — but only after you've already set up DMARC properly.
MTA-STS (Mail Transfer Agent Strict Transport Security) — A way to tell other mail servers "always use encryption when sending email to me, and refuse to fall back to unencrypted delivery."
TLS-RPT (TLS Reporting) — A way for your mail server to receive reports when other servers fail to deliver email to you over a secure connection — pairs with MTA-STS.
TLS (Transport Layer Security) — The encryption that puts the 'S' in HTTPS. It scrambles data so nobody between you and a website can read it.
Related Guides
Email Security Posture (Composite): Understand and Use the Results
Single-call composite that fans out across SPF, DKIM, DMARC, and DMARCbis tree-walk
SPF Check: Understand and Use the Results
Validate SPF record syntax, DNS lookups, and policy
DMARC Check: Understand and Use the Results
Analyze DMARC policy, alignment, and reporting
DKIM Check: Understand and Use the Results
Discover and validate DKIM signing keys
Need Programmatic Access?
Automate domain intelligence with 100+ API endpoints and a free MCP server for AI integration.