Should email authentication data show for unidentified ESPs?
Published 18 Aug 2026
Updated 23 Oct 2026
10 min read
Summarize with

Updated on 23 Oct 2026: We clarified missing authentication results, aggregate report limits, and how to investigate unidentified sending sources.
Yes. Email authentication data should show even when the sending email service provider (ESP) cannot be identified. ESP identification and authentication answer different questions. Identification asks who probably operated the sending system. SPF, DKIM, and DMARC results show what the receiver evaluated for this specific message. Hiding those results because the provider name is unknown removes the evidence needed to diagnose the message.
Use an "Unidentified ESP" label beside the available authentication results, with confidence and evidence kept separate. An unknown provider is not automatically malicious, and a recognized provider is not automatically authorized. The interface should preserve that distinction instead of turning an incomplete attribution into a security verdict.
Recommended default
Show available authentication results for every message and label missing data explicitly. Treat ESP detection as optional attribution, label uncertainty plainly, and keep the raw evidence available for investigation.
Why unidentified ESPs still have useful authentication data
Authentication does not depend on recognizing a commercial platform. A receiving mail system evaluates the envelope sender, SPF-authorized IPs, DKIM signatures, the visible From domain, the domain match required by DMARC, and the domain's published policy. Those checks still produce useful results when a sender uses private infrastructure, a smaller provider, a reseller, or a provider whose identifying headers changed.
Provider detection normally relies on fingerprints such as return-path domains, DKIM signing domains, header patterns, sending IP ranges, or reverse DNS. Each clue can be shared, customized, proxied, or removed. Authentication has a narrower purpose. It reports whether the identities presented in the message passed the receiver's checks and whether an authenticated domain matched the visible From domain under DMARC rules.
ESP identification
- Attributes a message to a likely sending platform.
- Uses infrastructure and header fingerprints.
- Includes a confidence level or an unknown state.
Email authentication
- Evaluates identities and authorization for one message.
- Uses DNS records and signatures to produce receiver results.
- Shows each mechanism's reported result, including absence and error states.
A message can therefore have an unidentified ESP and a clean DMARC pass. It can also come through a recognized ESP and fail because the customer account lacks correct domain authentication. The two outcomes belong in separate fields so readers do not infer one from the other.
What the interface should show
The useful default is a compact summary with expandable evidence. Put the provider label at the top, but do not let it control whether authentication rows render. A reader should see the result, the evaluated identity, and the reason for a failure without opening raw headers. Preserve raw headers when available, and label views based on aggregate reports separately.
|
|
|
|---|---|---|
Provider | Unidentified ESP and attribution confidence | Prevents false attribution |
SPF | Reported result, evaluated domain, and source IP | Shows IP authorization for the envelope domain |
DKIM | Each reported result, signing domain, and selector | Identifies the signature and DNS key |
DMARC | Result, matching mechanism, and policy domain | Explains the visible From domain check |
Receiver disposition | Reported action and override reason, if supplied | Separates handling from authentication |
Source IP | Connecting address and network owner, if known | Adds an infrastructure clue, not proof of the sending application |
Evidence source | Trusted receiver or report generator and observation period | Shows where and when the checks were performed |
Recommended fields for an unidentified sending source
For SPF, show the evaluated MAIL FROM domain and source IP, even when the check fails. For a null MAIL FROM, SPF derives that identity using HELO/EHLO. For DKIM, show each reported signature result, signing domain (d=), and selector (s=). For DMARC, show which mechanism supplied the matching domain and which policy domain supplied the record, including an inherited subdomain policy.

Unknown ESP identification displayed separately from SPF, DKIM, and DMARC results
The interface also needs a clear provenance label. Display the Authentication-Results authserv-id and accept results only from the receiving system's configured trust boundary. A familiar identifier or header position alone does not establish trust. RFC 8601 explains why forged or untrusted headers must not become authoritative authentication results.
Separate missing authentication data from failed checks
|
|
|
|---|---|---|
No trusted result available | The input does not supply a trusted verdict. | Show "Not available" and explain the missing evidence. |
none | A recorded absence, such as no DKIM signature or no DMARC policy. | Keep the mechanism-specific result; do not substitute fail. |
temperror | A temporary evaluation error, such as a DNS timeout. | Preserve the error and the receiver's diagnostic reason. |
permerror | An unrecoverable evaluation error for that check. | Preserve the error and investigate the affected configuration or message. |
Missing evidence and reported authentication errors need different labels
Keep SPF neutral and softfail distinct from fail. For SPF permerror, check for multiple SPF records or an exceeded SPF lookup limit. RFC 7208 caps evaluation at ten terms that trigger DNS queries, counting nested includes. A DMARC result of none means no policy was found; a published p=none is a monitoring policy that can accompany either a DMARC pass or fail.
How to interpret an unknown source safely
Start with the visible From domain and the final receiver's trusted authentication results. A DMARC pass means a policy was found and at least one qualifying path passed: SPF or DKIM with the required domain match. It does not prove that the message content is safe or that the ESP has been identified. A DMARC fail means a policy was found but neither qualifying path passed. The requested policy and the receiver's handling decision are separate fields.
Condensed receiver authentication resulttext
Authentication-Results: mx.example; spf=pass smtp.mailfrom=bounce.sender.example; dkim=pass header.d=sender.example header.s=s1; dmarc=pass header.from=sender.example
In this example, the provider can remain unidentified while DKIM passes with a signing domain that exactly matches the visible From domain. SPF uses bounce.sender.example, which meets the domain-matching requirement under relaxed SPF mode (aspf=r), but not strict mode (aspf=s). The DKIM pass still satisfies DMARC in either SPF mode. SPF passing for an unrelated bounce domain while DKIM fails would not satisfy DMARC. These domain-matching rules are defined in RFC 9989.
Do not equate unknown with unsafe
An unknown ESP label describes an attribution gap. Judge authentication, authorization, content, and source reputation with their own evidence. Escalate only when those signals justify it.

Gmail Show original view with passing SPF, DKIM, and DMARC results
Mailbox views like this are useful for one-message checks, but they do not establish whether an unfamiliar source sends repeatedly across the domain. Aggregate reporting provides that wider view. It groups source IPs, authentication outcomes, message counts, and policy disposition over time, which makes recurring unknown infrastructure easier to classify. In aggregate XML, auth_results contains the underlying SPF and DKIM results, while policy_evaluated reports their DMARC domain-matching outcomes. RFC 9990 defines these separate fields. Aggregate reports contain summaries rather than original messages or raw headers, cover participating receivers, and arrive after a reporting interval.
A practical investigation workflow
When an unfamiliar sender appears, preserve the authentication data and work outward. Start with DMARC because it connects the visible identity to SPF or DKIM. Then inspect the mechanism that produced the result, followed by infrastructure clues and sending history. This order prevents a recognizable IP owner from overriding stronger message-level evidence.
- Use Authentication-Results from the configured trusted receiver, and retain its authserv-id.
- Record the DMARC verdict and visible From domain, with the requested policy and receiver disposition kept separate.
- Identify whether SPF or DKIM supplied the matching identity, or why neither qualified.
- Review the connecting source IP, reverse DNS, signing domain, selector, and return path. An IP owner can be a hosting network or forwarder rather than the original ESP.
- Compare volume, first-seen date, failure rate, and the approved sender inventory.
Suped's DMARC checker confirms the currently published policy and catches syntax errors. For a wider check of the domain's authentication setup, use Suped's checker below. Current DNS does not prove which records the receiver saw when the message arrived, and it does not identify the sending application. Preserve the receiver's original results when investigating older messages.
?
What's your domain score?
Deep-scan SPF, DKIM & DMARC records for email deliverability and security issues.
Next, compare the unknown source against the organization's approved sender inventory. Ask who owns the visible From domain, whether a team recently added an application, and whether a vendor sends through shared infrastructure. An approved business relationship still requires correct domain authentication. If a legitimate source passes only for unrelated provider domains, configure DKIM signing with the organization's domain or a custom return path that meets DMARC's domain-matching requirement, then retest a delivered message.
Low-volume failures deserve context. Forwarding changes the connecting IP and can break SPF; message changes by a mailing list can invalidate DKIM. A validated Authenticated Received Chain (ARC) from a trusted intermediary can inform the receiver's handling decision, as described in RFC 8617. Keep that decision separate from the receiver's current SPF, DKIM, and DMARC results. Repeated volume and stable domain clues help attribution. The process in troubleshooting DMARC failures helps separate configuration faults from unauthorized traffic.
Finally, record the decision. Mark the source as authorized, unauthorized, forwarding-related, or unresolved. Keep the original evidence and the reason for the classification. That history prevents the same source from being rediscovered each week and gives policy owners a defensible basis for moving DMARC toward enforcement.
How Suped handles unknown sources at scale
A mailbox extension helps with a single message. Domain owners also need aggregate visibility because the same unidentified infrastructure can send thousands of messages without landing in the mailbox being inspected. Suped's DMARC monitoring groups report data by source, shows authentication health, and keeps verified and unverified senders distinct.
In Suped, an unverified source is one the domain owner has not confirmed as legitimate. That is different from an unidentified ESP or a failed authentication check. A recognized provider can still be unverified, and a DMARC pass does not establish business authorization.

Issues page showing verified and unverified source sections for reviewing sending sources
The verified and unverified source view supports this workflow. Review message volume and authentication results, confirm the source with its business owner, then verify a legitimate sender or dismiss an unauthorized one. Suped tracks issues and authentication-failure alerts for verified sources. Add a comment with the owner and reason for the decision so later reviews retain that context. Suped's source documentation describes this verification workflow.
Design defaults that reduce mistakes
A good interface shows the useful data by default and reserves advanced evidence for expansion. If unidentified senders require an optional setting, explain that setting during setup and show a visible indicator when the filter is active. Otherwise users can assume that no unknown sources exist when the product is simply hiding them.
- Render available authentication for identified and unidentified sources, and label missing results explicitly.
- Use a neutral "Unidentified ESP" label for an attribution gap.
- Show provider confidence apart from authentication status.
- Expose reported domains, selectors, IP data, and trusted raw headers when available.
- Distinguish unidentified, unverified, and authentication-failed states in filters and exports.
Filters should change presentation, not data collection. Keep unknown sources in exports, counts, and audit history even when a user chooses a quieter inbox view. If a badge fails to appear after activation, the interface should surface permission status, processing state, and the relevant unidentified-source setting instead of leaving the user to guess.
Frequently asked questions
No. It means the product could not confidently attribute the sending infrastructure to a provider. Review DMARC, SPF or DKIM domain matching, source history, authorization, and message content before classifying the email.
Yes. DMARC passes when SPF or DKIM passes with the domain match required for the visible From domain. The receiver does not need to know the ESP's commercial name.
Show the DMARC result and policy, the visible From domain, SPF result and evaluated MAIL FROM domain, reported DKIM results and signing domains, the source IP, and the trusted receiver that produced the verdicts. Label missing fields as unavailable, and keep receiver disposition separate from authentication.
Private infrastructure, reseller arrangements, custom return paths, shared IP space, new sending ranges, and changed headers can defeat provider fingerprints without affecting the receiver's authentication checks.
Authentication should remain available by default. A preference can reduce visual noise, but it should not remove unknown sources from reports, exports, counts, or audit history.
No. A missing trusted result means the available data does not establish the verdict. Display "Not available" instead of inventing a fail. Preserve explicit none, temperror, and permerror results because they describe different conditions.

