When DKIM passes but SPF fails in DMARC reports

A DMARC report showing no failed DKIM checks but many failed SPF checks usually means your messages are being authenticated by their digital signature, while the sending infrastructure is not authorised under your domain’s SPF record. This pattern is common when email is sent through several platforms, including marketing systems, help desks, invoicing services and customer relationship tools.

The result is not automatically a sign of spoofing or a broken mail system. It often reflects SPF’s dependence on the visible sending server and DKIM’s ability to preserve authentication as a message moves between services. Understanding the difference helps domain owners decide whether to update DNS, investigate an unauthorised sender or adjust their DMARC policy.

What the report is actually measuring

SPF checks whether the IP address that delivered an email is listed in the domain’s SPF record. DMARC then compares that authenticated SPF domain with the domain shown in the visible From address. If the IP is missing, the SPF result is fail. If the authenticated domain also differs from the From domain, the result can be treated as misaligned even when the sending IP is technically approved elsewhere.

DKIM works differently. The sender applies a cryptographic signature to the message, and the receiving server checks it using a public key published in DNS. A DKIM pass that aligns with the From domain is sufficient for DMARC to pass, even if SPF fails. This explains why a report can show a healthy DKIM result alongside a large volume of SPF failures.

Common reasons SPF fails at scale

The most frequent cause is an incomplete SPF record. A business may have authorised Microsoft 365 but forgotten its email marketing platform, accounting provider or support ticket system. Australian organisations operating across Sydney, Melbourne and Brisbane often add services gradually, leaving DNS records that reflect old systems as well as current ones.

Forwarding can produce the same result. When a recipient’s mail server forwards a message, the final receiving system sees the forwarder’s IP address rather than the original authorised sender. DKIM can survive this process because the signature travels with the message, while SPF commonly fails. Mailing lists and gateway services can create similar results.

Third-party senders need careful alignment

Check every source shown in the aggregate report, including bulk mail providers, CRM platforms, website forms and cloud-based payroll or billing systems. A provider may send on your behalf while using its own envelope-from domain. In that case, SPF could pass for the provider’s domain but fail DMARC alignment with your visible From domain.

Look for custom return-path or bounce-domain settings in each service. Publishing the provider’s recommended DKIM record and configuring a branded tracking or bounce domain usually gives DMARC a reliable aligned authentication path. Avoid adding random IP addresses to SPF simply because they appeared in a report; first establish who controls them and whether the service is still required.

DNS records can create hidden problems

SPF supports a maximum of ten DNS-based lookups. Multiple include statements, nested provider records and unnecessary mechanisms can push a domain over that limit, causing a permanent SPF failure. This is particularly easy to miss when several agencies or SaaS vendors manage email independently.

Review the record for duplicate entries, obsolete providers and excessive redirects. Keep one SPF record at the root of the domain, because separate TXT records can produce a permerror. Changes may take time to propagate, and DMARC aggregate reports commonly arrive a day or two after the underlying messages were sent.

Use reports alongside sender reputation checks

A DMARC report identifies authentication outcomes, but it may not fully explain whether an unfamiliar source is legitimate. Compare the reported IP addresses with your approved vendors, mail servers and known sending regions. A reputation check can add useful context when an address appears repeatedly or sends an unexpected volume; check an IP’s reputation before treating it as an approved source.

For an Australian domain, authentication also supports broader anti-abuse obligations. The Spam Act 2003 and guidance from the Australian Communications and Media Authority make sender identification and consent important considerations for commercial electronic messages. Strong DKIM, SPF and DMARC controls help reduce the likelihood that customers mistake a fraudulent message for a genuine communication from a .au business.

A practical path to remediation

Start with a complete inventory of legitimate senders. Confirm the platforms used by marketing, finance, customer service, recruitment and transactional systems. Then configure aligned DKIM wherever possible, simplify SPF, and monitor reports for several sending cycles. A DKIM pass is valuable, but it should not conceal an unauthorised service that is sending with your brand.

After legitimate sources are stable, consider moving from a monitoring policy such as p=none to quarantine or reject in stages. Review both aggregate and forensic reporting where available, while handling message data in line with internal privacy procedures. Tools such as Trusted Sender Score can support domain trust checks and authentication troubleshooting as part of that review.