Suped

Does DMARC require both SPF and DKIM to pass?

Michael Ko profile picture
Michael Ko
Co-founder & CEO, Suped
Published 12 Apr 2025
Updated 19 Sep 2025
6 min read
Email security padlock with separate SPF and DKIM shields
A common question many people have when delving into email authentication is whether DMARC absolutely requires both SPF and DKIM to pass. The short answer is no, it does not. DMARC, or Domain-based Message Authentication, Reporting & Conformance, is designed to succeed if either SPF or DKIM passes and aligns with the sender's domain. This flexibility ensures that even if one authentication method fails, your email can still be considered legitimate and avoid being marked as spam or blocked.
While DMARC only technically needs one of the two to pass, implementing both SPF and DKIM is considered a best practice for robust email security and deliverability. Having both provides redundancy and a stronger signal to receiving mail servers about the authenticity of your emails. It also offers protection against various types of email fraud, like phishing and spoofing.

Understanding DMARC's authentication reliance

DMARC acts as a policy layer on top of SPF and DKIM. Its primary role is to inform receiving mail servers what to do with emails that fail authentication. This policy is defined in a DMARC record published in your domain's DNS. For an email to pass DMARC, it must pass either SPF or DKIM authentication, and critically, the domain used for authentication must align with the "From" domain visible to the recipient. This alignment check is what makes DMARC powerful in combating impersonation.
Example DMARC record (DNS TXT record)DNS
v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com; ruf=mailto:dmarc@yourdomain.com; fo=1;
The policy tag (p=) dictates the action. It can be set to none, quarantine, or reject, providing varying levels of protection. The key is that DMARC reports (RUA/RUF) give you visibility into email authentication results, allowing you to identify and resolve issues even when authentication failures occur. This data is invaluable for continuous improvement of your email security.
This means that if you've configured DMARC, your emails can still pass DMARC if only one of the underlying authentication mechanisms, SPF or DKIM, is correctly set up and aligns with your domain. For instance, an email could pass DMARC with a valid SPF alignment but a failed DKIM check.

SPF and DMARC alignment

SPF, or Sender Policy Framework, verifies the sender's IP address against a list of authorized sending IP addresses published in the domain's DNS records. For DMARC to pass via SPF, two conditions must be met. First, the email must originate from an IP address listed in your domain's SPF record. Second, the domain specified in the MailFrom (or Envelope-From) header must align with the domain in the From header that recipients see.

SPF limitations to consider

While essential, SPF has limitations. It breaks easily during email forwarding, as the MailFrom domain can change. Also, SPF records are limited to ten DNS lookups. Exceeding this limit leads to PermError failures, causing legitimate emails to fail authentication. Using SPF flattening can help manage this complexity.
An SPF pass means the sending server's IP address is authorized, and the `MailFrom` domain matches the `From` header or a sub-domain of it. If these conditions are met, DMARC considers the SPF authentication aligned and valid, contributing to a DMARC pass. This verification step is fundamental for email receivers to trust the origin of incoming messages.

DKIM and DMARC alignment

DKIM, or DomainKeys Identified Mail, provides a cryptographic signature that verifies the sender's identity and ensures the email content has not been tampered with in transit. The DKIM signature is added to the email header and includes a hash of the email's content and certain headers.
Detailed email authentication process with magnifying glass
For DMARC to pass via DKIM, the domain specified in the DKIM signature's "d=" tag must align with the domain in the "From" header. This alignment can be either strict (exact match) or relaxed (subdomain match). Unlike SPF, DKIM is resilient to forwarding and can withstand some modifications to the email body or headers without breaking authentication, making it a robust authentication method.

The strength of DKIM

DKIM is often preferred for its cryptographic integrity and resilience. It ensures that mail content hasn't been altered during transit and provides a verifiable sender identity. This makes it particularly effective against phishing and email spoofing attempts, even when SPF might fail due to forwarding issues.

The benefits of deploying both

While DMARC only requires one method to pass, configuring both SPF and DKIM provides a layered defense, significantly enhancing your email security and deliverability. If one method fails, the other can still pass, giving your legitimate emails a higher chance of reaching the inbox. This redundancy is especially valuable given the complexities of email routing and potential modifications by intermediate servers.

One authentication method

  1. Single point of failure: If the sole authentication method breaks, DMARC will fail.
  2. Lower deliverability: Receiving servers might be more skeptical, increasing spam folder placement.
  3. Less protection: More vulnerable to specific types of email fraud.

Both SPF and DKIM

  1. Redundancy: If one fails, the other can still ensure DMARC passes.
  2. Improved deliverability: Stronger trust signals for receiving mail servers.
  3. Comprehensive security: Better protection against a wider range of attacks.
For comprehensive visibility into how both SPF and DKIM are performing and their impact on your DMARC compliance, a robust DMARC monitoring tool is essential. Suped provides AI-powered recommendations to help you fix issues and strengthen your policy, real-time alerts for any authentication failures, and a unified platform for monitoring DMARC, SPF, DKIM, blocklist status, and general deliverability insights. This integrated approach ensures your email infrastructure is fully protected and optimized.

Ensuring robust email authentication

While DMARC technically allows for a pass if either SPF or DKIM aligns, striving for both to pass and align provides the highest level of email security and deliverability assurance. It creates a robust defense against various email threats and builds stronger trust with receiving mail servers. Regularly monitoring your DMARC reports is key to maintaining this strong posture.
Understanding these mechanisms is crucial, especially when facing DMARC authentication failures. With tools like Suped's DMARC monitoring platform, you can gain insights into why your emails might be failing and receive actionable recommendations to resolve these issues. This ensures that your email reputation remains high and your messages consistently reach their intended recipients.
By proactively managing your email authentication with both SPF and DKIM, and leveraging detailed DMARC reports, you can protect your domain from abuse and significantly boost your email deliverability. This proactive approach helps secure your brand's communication channels and maintain recipient trust.

Frequently asked questions

DMARC monitoring

Start monitoring your DMARC reports today

Suped DMARC platform dashboard

What you'll get with Suped

Real-time DMARC report monitoring and analysis
Automated alerts for authentication failures
Clear recommendations to improve email deliverability
Protection against phishing and domain spoofing
    Does DMARC require both SPF and DKIM to pass? - DMARC - Email authentication - Knowledge base - Suped