Back to blog
Threat Intel
Phishing Forensics

The DMARC Quarantine Dilemma: Is It Truly Good Enough for BIMI?

Settling for a quarantine policy gets your logo rendered, but leaves your domain exposed to sophisticated spoofing.

MailSleuth Research
Email Security Team
November 12, 20266 min read
Conceptual illustration of an envelope partially protected by a shield with a padlock slipping past it

Getting a verified brand logo to render next to an email feels like the ultimate marketing victory, but security teams know the real prize is the enforcement policy required to get there. When marketing wants the visual branding of a Verified Mark Certificate and security wants to stop domain spoofing, the compromise usually lands on a quarantine policy. It checks the compliance box, satisfies the marketing department, and avoids the terrifying prospect of dropping legitimate mail.

But stopping at that transitional state is a dangerous resting place for a security engineering team. While it meets the technical baseline for logo display, it creates a permanent window of vulnerability. This piece breaks down the operational reality of settling for a bimi dmarc quarantine setup and why mailbox providers still treat your domain with suspicion.

Reading the Spec: Why Quarantine is the Floor, Not the Ceiling

The Brand Indicators for Message Identification specification dictates strict authentication prerequisites. To even be considered for logo display by a receiving mail transfer agent, the sending domain must publish a stringent Domain-based Message Authentication, Reporting, and Conformance policy.

The Baseline Prerequisite

Specifically, the domain must enforce a policy that actively alters the delivery of unauthenticated messages. A policy of none is explicitly rejected by the validators. The standard accepts quarantine as the minimum viable threshold because it acknowledges the operational difficulty of reaching full reject across complex enterprise environments.

The domain MUST have a DMARC policy of quarantine or reject, and the policy MUST apply to all subdomains. — RFC 8905

Treating this minimum threshold as the final objective creates a permanent gap in your defensive architecture. If a message fails Sender Policy Framework alignment under RFC 7208 and DomainKeys Identified Mail alignment under RFC 6376, quarantine simply instructs the receiving mail server to route the message to the spam folder. The payload is still delivered to the target environment. The threat actor still has a foothold on the user system, separated only by a folder boundary.

How Gmail and Apple Mail Handle Marginal Authentication

Mailbox providers do not evaluate authentication policies uniformly. The rendering of your brand logo is entirely at the discretion of the receiving infrastructure, which weights your published policy against their internal threat intelligence.

The Trust Score Variable

Gmail operates with notorious strictness regarding visual indicators. Even with a valid Verified Mark Certificate and a compliant policy, Google evaluates the aggregate sender reputation of the domain. If a spoofed email hits the Google perimeter and gets quarantined, it obviously does not receive the logo treatment. However, even legitimate, fully authenticated emails from a domain sitting at a quarantine enforcement level might occasionally drop the visual branding if the domain reputation dips or spam complaint rates spike.

Privacy Relays and Visual Inconsistency

Apple Mail integrates visual branding natively but relies entirely on the Authentication-Results header stamped by the receiving mail transfer agent before the message reaches the client. When iCloud infrastructure routes a message that fails alignment under a quarantine policy, the message is sunk to the Junk folder where no visual branding is rendered. The operational reality is that relying on quarantine creates highly inconsistent brand presence across different desktop and mobile clients, undermining the primary business justification for the project.

The Percentage Tag Trap and Partial Enforcement

The percentage tag is a critical tool for phased deployment, allowing security teams to sample the impact of enforcement without causing a massive business disruption. You might start by applying enforcement to a small fraction of unauthenticated traffic to analyze the fallout in your aggregate reports.

The visual indicator specification explicitly forbids this gradual approach. To qualify for a certificate, you must enforce the policy on all traffic. If your DNS record specifies a quarantine policy but restricts it to fifty percent of messages, the validation scripts will immediately fail your domain.

v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@example.com;

This creates a psychological trap for IT administrators. Eager to deploy the visual indicators, admins will artificially push the percentage tag to one hundred just to pass the validation checks, operating under the false assumption that they have locked down the domain. They have not secured the perimeter. They have merely instructed receiving servers to dump all unauthenticated, potentially malicious traffic into the spam folders of their employees and customers.

Residual Spoofing Risk in the Spam Folder

The core issue with stopping at a quarantine policy is what happens to the malicious payloads that survive the journey. When a sophisticated threat actor spoofs a domain with this policy, the email still lands on the user device.

Users are conditioned to hunt through their spam folders. Years of legitimate invoices, password resets, and vendor communications ending up in the junk folder due to broken forwarders have trained them to ignore the platform warnings. When an attacker crafts a highly targeted Business Email Compromise payload and it routes to spam, the attacker only needs the target to drag that message back into the primary inbox.

The Forwarding Failure Mode

Consider a scenario involving a forwarded meeting invite from an external vendor. The intermediate forwarding server breaks the sender policy alignment by rewriting the return path. The signature breaks because the forwarder appended a disclaimer to the body, altering the cryptographic hash. The message fails alignment and is quarantined.

The user finds the invite in their junk folder, assumes the corporate spam filter is being overly aggressive again, and trusts the sender. Threat actors rely heavily on this exact behavioral conditioning. Implementing Authenticated Received Chain under RFC 8617 can help preserve authentication results across hops, but the only way to eliminate the attack surface of spoofed domains entirely is pushing the policy to reject.

Confirming Technical Compliance Without Sacrificing Security

Advancing beyond quarantine requires absolute confidence in your email routing architecture. You must identify and map every shadow IT service, every rogue marketing automation platform, and every legacy on-premises application that sends mail on behalf of your organization.

This requires continuous, programmatic monitoring of aggregate reporting data. You cannot safely switch to a strict rejection policy if your primary human resources platform is still emitting messages with unaligned signatures.

Before applying for your certificate, you must validate that your DNS records are perfectly formatted. The assertion record requires strict adherence to the SVG Tiny Portable Secure profile. A single misconfigured tag in your authentication records or a missing parameter in your assertion text will halt the entire deployment and burn cycles with your certificate authority.

The takeaway

Settling for a quarantine policy to achieve compliance for visual indicators is a business compromise, not a security victory. It provides the marketing department with their visual branding while leaving the door wide open for threat actors to deposit sophisticated payloads into the spam folders of your target audience.

The ultimate goal of domain authentication is stopping spoofed mail at the perimeter before a user ever has the chance to make a bad decision. Use MailSleuth.AI to monitor your aggregate reports, identify the root cause of those final alignment failures, and confidently push your domains to full rejection. Anything less is just decorating an open window.

#dmarc#bimi#email-security#spoofing#authentication
MailSleuth Research
Email Security Team

We dissect phishing campaigns and email infrastructure so you don't have to.