Skip to main content
GaidmeGaidme
Guide

Email Deliverability Checklist: SPF, DKIM, DMARC & BIMI

A technical guide to 2024 email deliverability. Learn to configure SPF, DKIM, DMARC, and BIMI based on Google, Yahoo, and Microsoft's requirements.

By Mauricio Jochinsen
Email Deliverability Checklist: SPF, DKIM, DMARC & BIMI

As of 2024, achieving high email deliverability requires implementing four key protocols: SPF, DKIM, DMARC, and BIMI. Following Google and Yahoo's bulk sender guidelines from February 2024, any domain sending over 5,000 emails daily must have these authentications in place to avoid being marked as spam or rejected. A Valimail study found that domains with DMARC enforcement are 4.75 times less likely to be spoofed. This checklist synthesizes the official 2024 best practices from Google, Microsoft, and the Domain-based Message Authentication, Reporting, and Conformance (DMARC) working group.

TL;DR

  • As of February 2024, Google and Yahoo require DMARC, SPF, and DKIM for senders of over 5,000 emails per day.
  • While DMARC adoption surged in 2024, only about 42% of domains use an enforcement policy (p=quarantine or p=reject), leaving the majority unprotected from spoofing.
  • Implementing BIMI to display a logo in Gmail requires a Verified Mark Certificate (VMC), costing between $749 and $1,499 per year from CAs like DigiCert or GlobalSign.
  • Exceeding the SPF 10-DNS-lookup limit, a common issue for domains using multiple services, causes a PermError that breaks DMARC validation.
  • Microsoft will enforce similar SPF, DKIM, and DMARC rules for high-volume senders to Outlook.com addresses starting in 2025.

What Are SPF, DKIM, DMARC, and BIMI?

Sender Policy Framework (SPF) serves as the foundational layer of email authentication by creating a public list of all servers authorized to send email on behalf of a domain. This is accomplished through a specific DNS TXT record containing a list of approved IP addresses and included sending services. When an inbound mail server receives a message, it checks the sender's SPF record to verify the sending IP is on the authorized list; if it is not, the message fails the SPF check. However, adoption and correct configuration remain significant challenges. A 2024 analysis of the top one million domains found that 39% lacked an SPF record entirely, leaving them vulnerable to spoofing. Of the 59% that had a record, nearly two-thirds were configured in a way that could not produce a definitive 'fail' result, weakening their protection. Further analysis from dmarcian's August 2026 report on top German domains found that 55% of all email authentication errors were related to SPF, a figure that was virtually unchanged from the previous year's study. These statistics highlight that while SPF is a critical first step, its technical nuances, like the 10-DNS-lookup limit, frequently lead to misconfigurations that undermine its security benefits.

DomainKeys Identified Mail (DKIM) provides a layer of protection against message tampering by adding a cryptographic digital signature to the email's header. This process involves a private key, held by the sending server, to sign the message and a corresponding public key published in the domain's DNS records. Receiving servers use this public key to verify the signature, confirming that the email's content has not been altered in transit. Unlike SPF, which authenticates the sending server's IP address, DKIM authenticates the message itself. Data from dmarc.org's 2025 analysis of DKIM keys showed a significant shift toward stronger cryptography; the number of observed 2,048-bit RSA keys increased by 4.5 times from 2020 to 2021, indicating a growing security maturity among adopters. According to a study by Dmarcian, which analyzed the top 100 global banks in 2025, the combination of DKIM with a strong DMARC policy is a key recommendation from the Payment Card Industry to defend against financial fraud. This is crucial, as the Anti-Phishing Working Group (APWG) noted in its Q1 2025 report that the financial sector was the target of 30.9% of all phishing attacks observed.

Domain-based Message Authentication, Reporting, and Conformance (DMARC) unifies SPF and DKIM into a cohesive policy and reporting framework, telling receiving servers how to handle messages that fail authentication checks. A DMARC record, published in DNS, can instruct receivers to monitor failures (p=none), send them to spam (p=quarantine), or block them entirely (p=reject). Critically, DMARC also provides detailed reports back to the domain owner, offering visibility into all mail streams, both legitimate and fraudulent. Despite its power, DMARC enforcement remains low. A November 2026 analysis by DmarcDkim.com of over 1.4 million domains found that 67.7% had no effective DMARC protection, with only 11.9% having a full p=reject policy. However, mandates from providers like Google and Yahoo in February 2024 have spurred significant growth. According to a 2024 Valimail report, DMARC adoption among the top 10 million domains approached the 20% mark, a substantial increase driven by the new requirements. The same report noted that domains with DMARC enforcement are 4.75 times less likely to be spoofed, a statistic derived from analyzing billions of emails in 2020.

Brand Indicators for Message Identification (BIMI) is the newest standard in the authentication stack, providing a visual cue of trust by allowing a verified, trademarked brand logo to appear next to authenticated emails in the inbox. BIMI acts as a reward for senders who have properly implemented DMARC at an enforcement policy of p=quarantine or p=reject, as this is a prerequisite for a logo to be displayed. The primary function of BIMI is not to improve deliverability directly but to increase recipient trust and engagement by making legitimate emails instantly recognizable. Research from the Email Authentication Working Group, cited by Skysnag in an April 2026 analysis, shows that BIMI implementation can lead to a 23% higher open rate and an 18% improvement in click-through rates. The same analysis highlighted that on Gmail, BIMI-enabled emails saw open rates increase by 28.7% compared to a baseline. To qualify, a brand must not only have a strict DMARC policy but also obtain a Verified Mark Certificate (VMC) to validate ownership of the trademarked logo, ensuring that only legitimate brand owners can leverage this powerful visual indicator.

Protocol Primary Function DNS Record Type What It Authenticates Enforcement Control
SPF Lists authorized sending IP addresses. TXT The message's envelope (Return-Path). None. Only provides a pass/fail signal.
DKIM Adds a cryptographic signature to verify message integrity. TXT The message content and specific headers. None. Only provides a pass/fail signal.
DMARC Unifies SPF/DKIM and sets a policy for failures. TXT Alignment of SPF/DKIM domains with the visible 'From' domain. Yes (p=quarantine or p=reject).
BIMI Displays a verified brand logo in the inbox. TXT The sender's brand identity (requires DMARC enforcement). No, it's a visual indicator, not an enforcement mechanism.
Verification Method IP address lookup in the published list. Public key cryptography check. Checks for SPF/DKIM pass AND domain alignment. Checks for a valid VMC and DMARC enforcement.

SPF Configuration: Preventing PermError and Staying Under the 10-Lookup Limit

The Sender Policy Framework (SPF) specification, defined in RFC 7208, imposes a strict maximum of 10 DNS lookups for each SPF evaluation. This limit is a critical defense mechanism designed to prevent denial-of-service (DoS) attacks, where a malicious actor could craft a complex SPF record that forces receiving mail servers into an endless loop of DNS queries, exhausting their resources. Every time a receiving server checks an email, it must perform this evaluation, and certain parts of an SPF record require the server to look up information in the DNS. The mechanisms that consume one lookup each are include:, a:, mx:, exists:, and the redirect= modifier. Conversely, mechanisms that provide explicit information without needing a new query, such as ip4:, ip6:, and the final all mechanism, do not count against this 10-lookup budget. Understanding this distinction is fundamental to crafting a compliant and effective SPF record that doesn't inadvertently break its own authentication.

Exceeding the 10-lookup limit results in a permanent error, known as a PermError, which immediately causes the SPF check to fail. This is not a soft failure or a neutral result; it is a definitive signal that the domain's published SPF record is broken and could not be interpreted. The consequences of a PermError are severe, as it creates a cascading failure within the email authentication stack. DMARC (Domain-based Message Authentication, Reporting, and Conformance) relies on either SPF or DKIM passing and aligning. When SPF returns a PermError, it cannot contribute to a DMARC pass, placing the entire burden of authentication on DKIM. If DKIM also fails for any reason, such as a signature breaking during email forwarding, the message will fail DMARC authentication entirely. For domains with a p=quarantine or p=reject DMARC policy, this failure can lead directly to legitimate emails, from invoices to marketing campaigns, being sent to spam or rejected outright by major mailbox providers like Google and Microsoft.

Invalid SPF configurations are a persistent and often invisible problem affecting email deliverability across the internet. A February 2026 analysis of over 5.4 million domains by DMARCguard found that 148,655 domains had SPF records that exceeded the 10-lookup limit, representing 4.8% of all domains with SPF deployed in the study. This means roughly one in every 21 domains publishing an SPF record had a configuration that would result in a PermError. A separate 2024 analysis of the top one million domains by dmarcchecker.app found that 2% of all domains had an invalid SPF setup causing a PermError, with the most common issue being the presence of multiple SPF records, which is also forbidden. These errors frequently arise from an accumulation of include: statements as companies add third-party services like CRMs, marketing automation platforms, and helpdesks, each adding to the lookup count. Stale entries for decommissioned services are another common cause, contributing to a separate two-void-lookup limit that can also trigger a PermError.

DKIM Signing: Ensuring Message Integrity with Cryptographic Keys

DKIM signing fundamentally relies on a cryptographic pairing of a private key, kept secret on the sending server, and a public key published in the domain's DNS records. When an email is sent, the mail server generates a unique digital signature using the private key and adds it to the message as a DKIM-Signature header. This process, defined in RFC 6376, allows a receiving server to verify two critical facts: that the message was authorized by the owner of the sending domain and that its signed content was not altered in transit. The receiver fetches the public key from a specific TXT record in the sender's DNS, identified by a unique "selector" tag within the signature. This public key is the only way to decrypt and validate the signature, confirming the message's authenticity without ever exposing the private key. This public-key cryptography system provides a robust method for associating a message with a specific domain, forming a verifiable chain of responsibility that is independent of the email's transmission path.

The DKIM signature provides a tamper-proof seal by creating a cryptographic hash of key message components, including specified headers and the entire message body. The h= tag within the DKIM-Signature header explicitly lists which headers are included in the signature, always covering critical fields like the From: header to prevent sender impersonation. The bh= tag contains a computed hash of the message body, ensuring its integrity from sender to receiver. If any part of the signed headers or the body is modified in transit, even by a single character, the hash will change, and the signature verification will fail upon arrival. This mechanism is what allows DKIM to guarantee that the message received is the same one that was sent. According to a 2022 security analysis published in the USENIX Security Symposium, which analyzed 9.5 million DKIM records, proper configuration is essential, as even minor misconfigurations can invalidate this protection. The integrity check is so precise that it acts as a digital equivalent of a sealed envelope, proving the contents have not been opened or altered.

A primary advantage of DKIM over SPF is its resilience during email forwarding, a common scenario where SPF authentication frequently fails. SPF validates the IP address of the sending server against a list published in the domain's DNS; when an email is forwarded by an intermediary, like a mailing list or a university's alumni service, the new sending IP address no longer matches the original sender's SPF record, causing the check to break. In contrast, the DKIM signature is part of the email message itself and remains valid as long as the signed portions of the message are not altered by the forwarder. This makes DKIM a more robust and reliable signal for DMARC alignment, which requires either SPF or DKIM to pass. As noted in RFC 9989, domains implementing a strict p=reject DMARC policy must use valid DKIM signatures and should not rely solely on SPF for this exact reason. This resilience is critical in complex mail flows, ensuring legitimate, forwarded messages are not incorrectly marked as spam or rejected due to the inherent limitations of IP-based validation.

The security of DKIM hinges on the cryptographic strength of the key pair, with modern standards mandating longer keys to protect against forgery. In 2018, RFC 8301 officially increased the minimum required key size, stating that signers MUST use RSA keys of at least 1024 bits and SHOULD use 2048-bit keys. Verifiers are now required to treat any signature from a key shorter than 1024 bits as invalid. Despite this clear guidance, adoption of stronger keys has been slow. A 2025 analysis of the top one million domains by software developer Andreas Wulf revealed that out of 476,617 DKIM records found, 1,726 domains were still using keys with fewer than 1024 bits. Wulf demonstrated in a proof-of-concept attack that a weak 512-bit key could be cracked in under four days on a standard cloud server, allowing him to forge valid signatures for the compromised domain. This highlights a significant real-world risk, as many hosting panels and older mail platforms still generate deprecated 1024-bit keys by default, leaving domains vulnerable without their knowledge.

DMARC Enforcement: From Monitoring to Rejecting Unauthenticated Email

A DMARC policy, defined by the p= tag in a domain's DNS record, explicitly tells receiving mail servers how to handle emails that fail authentication checks. Senders can choose one of three policy levels: p=none, p=quarantine, or p=reject. The p=none policy acts as a monitoring-only mode, allowing unauthenticated emails to be delivered normally while sending aggregate reports back to the domain owner for analysis. This initial step provides crucial visibility into all services sending on the domain's behalf without any risk to deliverability. The next level, p=quarantine, instructs receivers to treat failing messages as suspicious, typically by placing them in the recipient's spam or junk folder. This offers a tangible layer of protection against spoofing. The final and most secure policy, p=reject, is the ultimate goal; it directs servers to completely block any email that fails DMARC, preventing it from reaching the recipient at all. Progressing through these stages sequentially, from monitoring to full enforcement, is a foundational best practice for securing a domain against fraud and improving deliverability.

The February 2024 email sender requirements from Google and Yahoo served as a massive catalyst for DMARC adoption, making it a baseline necessity for any organization sending over 5,000 emails daily. These mandates required bulk senders to publish, at a minimum, a p=none DMARC record, alongside valid SPF and DKIM configurations. The immediate effect was a historic surge in adoption; one analysis from MailMend noted that monthly new DMARC domain publications doubled in 2024, from 55,000 to 110,000, directly following the enforcement. Similarly, a study by EasyDMARC cited in Fundraising.co.uk found that DMARC uptake among .org domains doubled from 3.98% to 7.78% between March 2023 and March 2024, with researchers attributing the growth directly to the new provider rules. While this push successfully established DMARC as a standard practice, the low barrier of a p=none policy meant many organizations stopped at compliance rather than progressing to a security-focused enforcement policy, creating a significant gap between having a record and being protected.

Despite the surge in adoption, a significant 'enforcement gap' persists, leaving many domains vulnerable. A 2026 analysis from Valimail, detailed in a DomainScan.in report, found that while 78% of the top million domains now have a DMARC record, only 42% have an enforcement policy of quarantine or reject. This leaves a 36-point gap where domains are monitoring for fraud but not actively stopping it. A key prerequisite for closing this gap is achieving 'identifier alignment', a core DMARC mechanism that requires the domain in the visible From: header to match the domain authenticated by SPF or DKIM. As explained by Dmarceye, an email passes DMARC only if SPF or DKIM passes and aligns with the From: domain. Without alignment, an email can pass authentication checks using an unrelated domain but still fail DMARC, a common scenario for organizations using multiple third-party sending services. This complexity is a primary reason many domains remain at p=none, as moving to reject without first ensuring all legitimate mail streams are aligned risks blocking valid corporate emails.

DMARC Policy Action on Failing Email Primary Purpose Impact on Deliverability Protection Level
p=none Delivered to recipient as normal. Monitoring & Reporting: Gain visibility into all sending sources without affecting mail flow. None. Satisfies the minimum Google/Yahoo 2024 requirement for bulk senders. Zero. Provides no protection against spoofing or phishing.
p=quarantine Sent to the recipient's spam or junk folder. Transitional Enforcement: Filter suspicious emails while minimizing the risk of blocking legitimate mail. High. Legitimate but unaligned mail may be missed by recipients if it lands in spam. Medium. Prevents spoofed emails from reaching the primary inbox.
p=reject Blocked entirely by the receiving server. Full Enforcement: Prevent all unauthenticated and fraudulent emails from being delivered. Highest. Misconfigured but legitimate mail will be permanently rejected, causing delivery failures. Maximum. Provides the strongest protection against domain spoofing and phishing.
p=quarantine with pct=10 10% of failing emails are sent to spam; 90% are delivered normally. Gradual Rollout: Test the impact of an enforcement policy on a small percentage of mail. Low. Affects only a small, random sample of mail, allowing for low-risk testing. Low. Protects against only a fraction of spoofed emails.
p=reject with pct=50 50% of failing emails are blocked; 50% are delivered normally. Confident Testing: Widen the enforcement test before moving to 100% rejection. Moderate. Risk of legitimate mail being blocked increases significantly. Partial. Protects against half of all spoofing attempts.

BIMI and VMCs: Displaying a Verified Logo for Brand Trust

Brand Indicators for Message Identification, or BIMI, fundamentally requires senders to have a strict DMARC authentication policy in place before any logo can be displayed. Mailbox providers will only check for a BIMI record if the sending domain's DMARC policy is set to an enforcement mode of p=quarantine or p=reject. A policy of p=none, which only monitors for authentication failures, is insufficient and will cause providers like Gmail to skip the BIMI lookup entirely. Furthermore, the policy must apply to 100% of the domain's mail, which means the pct=100 tag must be set or the pct tag omitted altogether, as a percentage less than 100 is not considered a full enforcement policy. This prerequisite ensures that the brand has taken the necessary steps to secure its email channel against unauthorized use and spoofing, which is the foundational security principle upon which BIMI's branding benefits are built. As of early 2026, a DMARCguard State of Email Authentication 2026 report found that 57.9% of domains with a DMARC record were still using a p=none policy, making them ineligible for BIMI. This highlights the significant technical hurdle that DMARC enforcement represents for many organizations, acting as the primary barrier to BIMI adoption.

To display a verified logo in Gmail and earn the associated blue verified checkmark, a domain must obtain a Verified Mark Certificate (VMC) from a recognized Certificate Authority (CA). As of 2026, the primary CAs issuing VMCs include DigiCert, GlobalSign, and Sectigo. A VMC is a specialized digital certificate that cryptographically binds a brand's trademarked logo to its sending domain, providing a high level of assurance that the sender is legitimate. The core requirement for a VMC is that the logo must be a legally registered trademark with an intellectual property office recognized by the CAs, such as the United States Patent and Trademark Office (USPTO) or the European Union Intellectual Property Office (EUIPO). The validation process is rigorous, requiring the CA to confirm the organization's identity, its control over the domain, and the active status of the trademark registration. While Google began accepting a newer, non-trademark certificate called a Common Mark Certificate (CMC) in late 2024 for logo display, only a VMC will grant the coveted blue checkmark that signals the highest level of sender verification to Gmail's 1.8 billion users.

The financial and administrative investment required for a Verified Mark Certificate is a significant factor in the slow adoption of BIMI. A VMC requires a legally registered trademark, a process that itself can cost between $1,000 and $3,500 in legal and filing fees and take over a year to complete. Once a trademark is secured, the annual cost for the VMC itself ranges from approximately $749 to over $1,500, depending on the issuing Certificate Authority and the reseller. For example, as of January 2025, a DigiCert VMC was priced at $1,550 for a one-year term from one reseller, while other providers like FairSSL listed it at €1,501 per year. These direct costs are in addition to the indirect costs of implementing and maintaining the prerequisite DMARC enforcement policy, which can range from $100 to over $5,000 annually for a monitoring platform. This combination of high costs, complex prerequisites, and lengthy timelines has kept BIMI out of reach for many small and mid-sized businesses. Consequently, as of early 2026, BIMI adoption remains low; one scan of 5.5 million domains in February 2026 found that only 0.4% (20,518 domains) had published a BIMI record. However, the ecosystem is growing, with a projected 9,079 new certificates to be issued in 2026, representing a 24% increase from 2025.

The 2024 Bulk Sender Requirements from Google, Yahoo, and Microsoft

The email landscape shifted fundamentally in February 2024, as Google and Yahoo began enforcing new, stricter authentication requirements for bulk senders. Any domain sending approximately 5,000 or more emails per day to personal Gmail or Yahoo accounts must now have Sender Policy Framework (SPF) and DomainKeys Identified Mail (DKIM) records correctly configured and a Domain-based Message Authentication, Reporting, and Conformance (DMARC) record published in their DNS. This initial DMARC policy can be set to p=none, which is a monitoring-only mode, but the presence of the record itself is mandatory for compliance. According to Google's official sender guidelines, a domain is permanently classified as a bulk sender once it crosses the volume threshold, meaning all future mail from that domain, including transactional and marketing streams, falls under these rules. This industry-wide alignment effectively makes robust email authentication a prerequisite for reliable inbox placement, moving SPF, DKIM, and DMARC from technical best practices to foundational requirements for any significant email operation.

Beyond the core authentication protocols, the 2024 requirements from Google and Yahoo introduced equally critical mandates regarding sender behavior and message content. A key operational metric is the spam complaint rate, which bulk senders must keep below 0.3% as measured within Google Postmaster Tools. Google's official guidance further recommends that senders actively aim for a rate below 0.1% to ensure optimal deliverability, as even rates between 0.1% and 0.3% can negatively impact reputation. Furthermore, all marketing and subscribed messages must now support one-click unsubscribe, a mechanism defined in RFC 8058. This requires senders to include specific headers (List-Unsubscribe and List-Unsubscribe-Post) that allow recipients to opt out directly from their email client's interface, with the request to be honored within two days. This rule, which had a grace period until June 2024 for some senders, explicitly excludes transactional messages like password resets or order confirmations.

Following the precedent set by Google and Yahoo, Microsoft announced it would enforce nearly identical requirements for domains sending over 5,000 emails per day to its consumer mailboxes, including Outlook.com, Hotmail.com, and Live.com. Enforcement of these rules began on May 5, 2025, closing a significant gap and creating a unified standard across the three largest consumer mailbox providers. The Microsoft requirements mirror those of its peers: mandatory SPF and DKIM authentication, and a published DMARC record with a policy of at least p=none. While Microsoft's initial announcement did not specify a spam complaint rate threshold like Google's 0.3% limit, it emphasized that non-compliant mail from high-volume domains would first be routed to the junk folder, with outright rejection as a subsequent enforcement step. This alignment solidifies the new baseline for email deliverability, making it clear that unauthenticated bulk email is no longer viable for reaching customers on any major platform.

A crucial and often misunderstood component of DMARC compliance for all providers is the concept of identifier alignment. Simply having SPF and DKIM records is not sufficient; for DMARC to pass, the domain in the visible From: header, the one the user sees, must align with the domain authenticated by either SPF or DKIM. SPF alignment compares the From: header domain to the domain in the email's hidden Return-Path address, while DKIM alignment compares it to the domain specified in the DKIM signature. This requirement directly prevents a common spoofing technique where an attacker uses their own domain (which passes SPF/DKIM) while forging a trusted brand in the From: header. Without alignment, the authentication is technically valid but proves nothing about the visible sender. DMARC closes this loophole by binding the authentication result to the sender identity the recipient trusts, making it a critical control for preventing phishing and brand impersonation.

Related reading

Frequently Asked Questions

What happens if I don't implement SPF, DKIM, and DMARC in 2024?

Failure to implement SPF, DKIM, and DMARC will cause significant email delivery problems. Following mandates from February 2024, bulk senders (domains sending over 5,000 emails daily) that do not have these three protocols in place will have their emails rejected or marked as spam by major providers like Google and Yahoo. Even for those sending lower volumes, not having at least SPF or DKIM can lead to messages being treated as suspicious and landing in spam folders. Ultimately, this damages your domain's reputation, disrupts communication, and leaves your domain vulnerable to being impersonated by attackers.

How much does it cost to implement BIMI for my domain?

Implementing BIMI requires purchasing a Verified Mark Certificate (VMC), which has a significant cost. As of late 2024, VMC prices from Certificate Authorities like DigiCert and GlobalSign range from approximately $750 to $1,500 per year. This cost is for the certificate that verifies your trademarked logo and is a prerequisite for displaying your logo in supported inboxes like Gmail. Some vendors may also charge one-time integration fees, and you must also factor in the potential costs of registering a trademark if you do not already have one.

Can I use DMARC without having SPF and DKIM configured?

No, you cannot effectively use DMARC without having at least one of SPF or DKIM configured. DMARC is designed to work on top of SPF and DKIM; it checks the results of those two protocols to determine if a message is authentic. For an email to pass DMARC, it must pass either the SPF check or the DKIM check and also be in alignment with the domain in the "From" header. While you could technically publish a DMARC record without them, it would be ineffective and all your mail would fail DMARC checks, likely causing severe delivery issues.

How do I check if my domain has a DMARC record?

You can check for a DMARC record using a free online DMARC checker tool. Many vendors like Mimecast, Valimail, and EasyDMARC offer tools where you simply enter your domain name, and it will look up the DMARC record from your DNS. These tools parse the record and confirm if it is valid and what policy is set. Alternatively, you can use command-line tools like nslookup on Windows or dig on macOS and Linux to query the TXT record directly at the _dmarc subdomain (e.g., nslookup -type=TXT _dmarc.yourdomain.com). If the tool or command returns no record, then DMARC is not configured for your domain.

What is the difference between DMARC p=quarantine and p=reject?

The primary difference lies in how a receiving mail server is instructed to handle an email that fails DMARC authentication. A policy of p=quarantine tells the receiver to treat the message as suspicious, which usually means sending it to the recipient's spam or junk folder. In contrast, p=reject is a stricter policy that instructs the server to block the email entirely, so it is never delivered to the recipient at all, and the sending server receives a bounce notification. While p=quarantine provides a safety net, p=reject offers the strongest protection against spoofing and is the ultimate goal for DMARC enforcement.

Last updated: November 2026