A message may display [email protected] as its sender even though an unrelated server delivered it. SPF or DKIM can authenticate sending infrastructure or a signing domain, yet neither automatically proves that the visible From address belongs to the authenticated identity. DMARC connects those signals through domain alignment and lets domain owners request how receivers assess failures. Correct deployment requires DNS policy discovery, an inventory of legitimate senders, reporting analysis and careful exception handling. The May 2026 DMARC standard also changed how organizational domains are discovered, making older public-suffix-list assumptions a potential implementation error.
A message can pass SPF for the SMTP envelope domain yet fail DMARC when that domain does not align with the visible From address. Examining DKIM’s signing domain and alignment separately prevents an SPF pass from being mistaken for proof of visible sender identity, a practical email-authentication distinction addressed in the CompTIA Security+ certification.
DMARC validates use of the visible author domain, not message honesty
Email has several identities. The address a person sees in the From header is defined by RFC 5322 and is commonly called the Author Domain in DMARC. The SMTP transport has its own envelope sender and connecting server, while DKIM signatures carry a signing domain. These identities can be different for legitimate reasons: an outsourced billing service might transmit on behalf of a company, and a mailing list can alter the route or message body.
Domain-based Message Authentication, Reporting, and Conformance (DMARC) determines whether an authenticated SPF or DKIM identifier aligns with the visible Author Domain. A message receives a DMARC pass when at least one eligible mechanism passes authentication and its domain passes the required alignment check. A message need not pass both aligned mechanisms. Conversely, an SPF pass for an unrelated bulk-mail sender is not enough merely because that server was permitted to send mail for its own domain.
Passing DMARC validates an authorized relationship to the domain; it is not proof that the content is truthful, the sender’s account is uncompromised, or the recipient should trust every instruction. A criminal with control of a real mailbox can send a correctly authenticated fraudulent request. A lookalike domain can be authenticated for itself while misleading a hurried recipient. Domain authentication is therefore one layer in a wider email-security process, not a substitute for fraud analysis and recipient behavior safeguards.
SPF and DKIM contribute distinct authentication results; DMARC checks whether a passing authenticated domain aligns with the From domain the recipient sees. A message can have a valid DKIM signature from a third-party service and still fail alignment with the claimed author. Even a DMARC pass does not certify that the message’s content is safe or that a payment request is legitimate. Email policy must therefore combine domain authentication with transaction and content controls.
SPF and DKIM produce evidence with different failure modes
Sender Policy Framework (SPF) evaluates the connecting mail server’s authorization to send for the SMTP envelope domain, typically using DNS-published policy. That protects an SMTP identity, not automatically the visible From address. Forwarding often changes the connecting server and can cause SPF to fail at the final receiver even when the original sender was legitimate. The correct DMARC analysis checks both the SPF result and whether its authenticated domain aligns with the Author Domain.
DomainKeys Identified Mail (DKIM) verifies a digital signature covering selected message headers and a body canonicalization result. The signature’s d= domain supplies the authenticated identifier. DKIM can survive forwarding when the forwarded message retains signed material; modifying a signed subject, body or selected headers can break the signature. A valid signature from an unrelated domain still fails DMARC alignment if no eligible SPF or other DKIM pass aligns.
Relaxed alignment permits an authenticated identifier and the Author Domain to share the same organizational domain. Strict alignment requires the domain identifiers to match exactly. The domain owner can specify the desired modes with DMARC tags. Relaxed alignment helps complex sending operations in which permitted subdomains and service domains vary, while strict alignment can be appropriate where exact identity binding is operationally feasible. Neither setting should be chosen without checking real sending streams.
| Signal | It establishes | It does not establish alone |
|---|---|---|
| SPF pass | The connecting sender meets the envelope domain’s authorization rule | That the visible From domain matches |
| DKIM pass | Signed message elements validate for a signing domain | That the author is authorized by that signing domain |
| DMARC pass | At least one authenticated identifier aligns with the Author Domain | That content, links or instructions are safe |
An SPF pass can coexist with a spoofed visible From address because SPF authenticates the envelope identity. Before trusting an email-authentication result, check whether a passing SPF or DKIM domain aligns with the recipient-visible From domain before concluding DMARC passes. Inspect the actual headers and DNS records instead of relying on a dashboard label; even correctly authenticated mail can contain a fraudulent payment request.
DNS policy records express a sender’s request, not an absolute receiver command
DMARC policy is published as a DNS TXT record under a _dmarc label. The owner can request monitoring with p=none, a quarantine-oriented response with p=quarantine, or rejection with p=reject. These are the domain owner’s assessment preferences for messages that fail DMARC. Mail receivers can consider additional evidence, local anti-abuse policy and operational conditions; a published p=reject is not a guarantee that every receiver will reject every failing message.
An initial policy might resemble v=DMARC1; p=none; rua=mailto:[email protected]. The exact syntax must be validated by the implementation, and any reporting address should be controlled and secured by the organization. A monitor-only policy helps reveal legitimate services using the From domain without aligned SPF or DKIM. Moving to quarantine or reject before fixing those legitimate streams can disrupt critical customer, supplier or transactional mail.
Policies can also distinguish subdomains and non-existent author domains. RFC 9989 retains domain-policy concepts while defining tags such as sp and np for applicable subordinate cases. Their effect depends on which DNS record is discovered and whether a particular author domain exists. Avoid copying a record from one domain to every namespace without checking delegated administration, mailing arrangements and DNS policy ownership.
Mail routing and message authentication are related but not interchangeable. MX records identify where mail for a domain is normally delivered; they do not decide whether a message claiming a From domain passes SPF, DKIM or DMARC. A deployment review should separately inspect inbound delivery paths, outbound authorized services, DNS authentication records and the receivers’ observed validation results.
RFC 9989 replaced the old public-suffix assumption with a DNS Tree Walk
The May 2026 IETF RFC 9989 obsoletes RFC 7489 and RFC 9091 as the base DMARC standard. One important change concerns how receivers determine the relevant organizational and policy domains. Older material often describes deriving an Organizational Domain through Public Suffix List data. RFC 9989 instead defines a bounded DNS Tree Walk that looks for applicable DMARC policy records in the DNS hierarchy. Implementations that still assume “take the last two labels” or rely exclusively on public-suffix lists can make incorrect decisions for complex namespaces.
The receiver first checks for an applicable policy at the Author Domain and, as needed, walks parent names in the DNS hierarchy. The procedure is deliberately bounded to avoid excessive DNS lookup work when a domain name has many labels: no single Tree Walk may require more than eight DNS queries. An optional psd=n tag can explicitly identify an Organizational Domain, while psd=y can identify a Public Suffix Domain; other algorithmic rules resolve cases without those tags. A receiver must implement the actual RFC procedure rather than infer that these two values always appear in every record.
The discovered policy and Organizational Domain support different tasks. Finding a policy identifies the sender’s requested assessment for a message; determining organizational boundaries helps test relaxed alignment between authenticated identifiers and the visible Author Domain. Strict alignment can be evaluated by comparing the exact domain identifiers. Some transitions from legacy discovery can change which policy is found or how identities align, so a mature email program should test nested domains and delegated namespaces rather than assume all receiving systems behave identically.
This is a protocol-correctness issue as well as a deliverability issue. A mistaken boundary can create a false pass or fail, cause unintended filtering, or conceal a misconfigured third-party sender. Organizations operating complex namespace hierarchies should test with receivers and diagnostic tooling that clearly state whether they implement RFC 9989’s discovery and alignment semantics.
Aggregate and failure reports are evidence for a measured rollout
DMARC reporting helps domain owners discover how their name is being used. Aggregate reports summarize authentication and policy observations across receiver populations; failure reports can contain additional information about particular failed messages when supported and appropriate. The 2026 IETF standards separate these report formats from the base protocol: RFC 9990 addresses aggregate reporting, and RFC 9991 covers failure reporting. Neither standard guarantees that every receiver will send complete reports for every message.
Aggregate data can reveal an unregistered vendor sending legitimate invoices, an old application using a misaligned envelope domain, or apparent spoofing attempts from unrelated infrastructure. Analysts should correlate report counts with authorized senders, campaign periods and known application owners. High numbers of failures alone do not prove successful compromise, and an absence of reports may reflect receiver participation rather than absence of suspicious mail.
Failure reports can include message-specific content or personal information. Their use therefore creates privacy, handling and storage obligations. Apply access controls, retention and purpose limitations to reports and review whether full message evidence is necessary. Do not route sensitive diagnostic content into a broadly accessible shared mailbox simply because the report address is easy to configure.
Make report analysis an operational loop. Classify expected platforms, align SPF or DKIM for each, identify unrecognized infrastructure, validate DNS publication, and check whether changes affect legitimate traffic before tightening policy. Include clear ownership for each sender and a rollback path if a critical service begins failing. A successful DMARC program reduces unauthorized use of a domain without silently blocking its own legitimate business communications.
Inventory actual senders before changing enforcement policy
A large organization may authorize more mail sources than its central IT group knows about: help-desk systems, HR platforms, payment providers, email marketing, ticketing, cloud alerts, and acquisitions with legacy mail infrastructure. A DMARC deployment begins by mapping those sources to organizational owners and verifying what domain they use in the visible From header, their envelope sender, and their DKIM signatures. Third-party marketing or transactional services should be tested as real configured senders, not assumed compliant because the vendor advertises “supports DMARC.”
Under a monitoring policy, compare aggregate reports with the inventory and seek evidence from the mail platform itself. A service might pass SPF for the provider’s domain while failing DMARC because the visible author domain is yours. The provider may offer custom return-path configuration, aligned DKIM signing, or a different From-domain arrangement. Choose the option that creates a controlled, supportable identity relationship and does not allow unrelated senders to impersonate the organization.
Forwarders and mailing lists require separate consideration. Forwarding can invalidate SPF at the final recipient, while a list that modifies signed content may break DKIM. Such messages can fail authentication without being malicious. RFC 9989 explicitly cautions that user domains associated with general-purpose mail and list behavior must study interoperability carefully before aggressive rejection. Do not set a universal “everyone must reach p=reject” target divorced from actual mail patterns and operational requirements.
After legitimate streams are aligned, assess a policy change in a controlled period, including high-volume campaigns and rarely used business workflows. Communicate expected changes to owners, review support complaints, inspect receiving-domain differences and establish how to reverse a harmful change. Subdomain policy, delegated DNS and sender identities should be included in change testing. The useful completion criterion is measured reduction in unauthorized domain use without unacceptable legitimate-mail loss.
DMARC reduces direct spoofing but cannot make every message trustworthy
An attacker may register a lookalike domain, compromise a real mailbox, abuse a vendor’s authorized sending service or insert a harmful link into an otherwise legitimate message. These messages can carry valid SPF, DKIM and DMARC results. Domain authentication makes it harder to spoof the exact protected From domain but it does not authenticate the honesty of the human behind the content or guarantee that attachments and web destinations are safe.
Other controls remain necessary: mailbox access policies, phishing-resistant authentication, malicious-link analysis, attachment isolation where appropriate, business-process verification for payment changes, anomaly detection and recipient education. Security teams may also use web and email inspection to detect harmful content and access patterns that domain authentication intentionally does not classify. Each layer has different evidence and failure modes; no single pass/fail indicator replaces the whole security decision.
Investigations should preserve actual authentication details rather than relying on the message’s displayed sender alone. Inspect Authentication-Results, relevant Return-Path fields, DKIM signing identifiers and message routing evidence alongside the visible From header. These values can be malformed, missing or forged inside untrusted material; their interpretation depends on which server inserted them and the receiving infrastructure’s trust boundary. Analysts should distinguish a trustworthy receiver-generated result from arbitrary header text supplied by an attacker.
DMARC also affects response after a domain is abused. Examine the failed author domain and source IP patterns, check whether the sending infrastructure belongs to a legitimate partner, and determine whether a sudden spike reflects a new malicious campaign or an authorized system whose configuration changed. A strong team can distinguish those cases and choose an appropriate remediation, rather than broadly blocking all messages whenever a report shows failure.
Validate DNS, aligned mail streams, reporting and receiver behavior together
A useful verification exercise sends controlled messages through each approved production sender, examines the received headers and records whether SPF, DKIM and DMARC evaluate as expected. Repeat with known legitimate forwarding or mailing-list paths. For a complex subdomain, test policy discovery against the RFC 9989 DNS Tree Walk rather than assuming an older public-suffix-list-based tool is authoritative. Capture actual test results and receiver identity, because behavior can differ among mail services.
Test negative cases in a safe lab or approved simulation: an unrelated envelope sender, a valid DKIM signature for the wrong domain, a broken signature, and a message from a nonexistent subdomain. Document whether the receiving service identifies the DMARC failure and what action it actually takes. A domain owner publishes a preference; it does not control every recipient’s local filtering. If the monitoring data conflicts with message-level evidence, investigate the implementation or reporting limitations before changing policy.
After deploying changes, monitor deliverability, legitimate failure patterns, delegated DNS changes, new SaaS senders and the handling of incident reports. Assign ownership of DMARC reporting and alert when an authorized vendor stops signing correctly. Review reporting mailbox access and privacy controls, and avoid letting an obsolete DNS record or abandoned vendor configuration remain a permanent hole in the organization’s mail policy.
The operational model matters more than memorizing RFC numbers. SPF evaluates the SMTP identity and authorized sending infrastructure, DKIM verifies signed message elements, and DMARC evaluates alignment with the displayed From domain and the sender’s policy. Validate DNS and authorized senders during rollout, examine reports for legitimate forwarding and third-party services, then keep phishing and business-email-compromise defenses separate from domain authentication. When applying SY0-701 email-security concepts, a DMARC decision depends on SPF or DKIM identifier alignment rather than whether either underlying mechanism passed in isolation.