What is BIMI, and why DMARC comes first
BIMI only kicks in after DMARC has done its job. A receiver that follows the BIMI specification first checks that the message passed DMARC and that your domain's DMARC policy is at enforcement (p=quarantine or p=reject, on both the From domain and its organizational domain). If either check fails, it doesn't even look up your BIMI record. So the logo project can't start before the DMARC project ends.
BIMI (Brand Indicators for Message Identification) lets you publish a DNS record that points to your logo, which supporting mailbox providers may show next to your authenticated mail. For the basics, see What is BIMI on our main site. This article is about the part that trips teams up: what DMARC has to look like before BIMI does anything.
BIMI DMARC requirements: what the receiver checks
BIMI is still a draft specification. Before any BIMI processing, a receiver must check the following:
- One From address. If there's more than one From header, or one From header with more than one address, there's no BIMI.
- DMARC passes for the From domain. If it doesn't, the receiver may still treat the message as a DMARC pass for BIMI, for example through a trusted ARC chain, a trusted-forwarder list, or local policy. Otherwise "BIMI processing MUST NOT be performed."
- The policy isn't
p=none. That applies to the From domain and to its organizational domain. - The subdomain policy isn't
sp=none. If the record has ansptag set tonone, there's no BIMI. - No partial
pct. Forp=quarantine, apcttag, if present, must bepct=100.
On the domain owner's side, that means a quarantine or reject policy on both the organizational domain and the Header From domain. A subdomain policy, if you publish one, must not be none. In short: DMARC must be at enforcement on the organizational domain and subdomains. Policies of none, or a pct value below 100, are not accepted.
The mailbox providers agree. Google requires p=quarantine or p=reject, and its BIMI page still says pct must be 100. Yahoo lists "A DMARC policy of quarantine or reject is in place" as a condition for showing a logo.
Why the order is this way round
DMARC at enforcement is the anti-spoofing control. BIMI only adds a picture to mail that has already passed it. If receivers showed logos on mail that wasn't authenticated and enforced, they'd be handing phishers a free trust signal. That's why the gate sits in the spec itself, not in a best-practice guide.
It also means the logo can't be used to hurry DMARC along. Getting to enforcement safely takes aggregate reports, an inventory of everything that sends as your domain, and aligned SPF or DKIM for each of those senders (A safe rollout: p=none to quarantine to reject). Schedule the logo work after that. If your domain has been sitting at p=none for a while, Why staying at p=none is a problem covers what that costs you beyond BIMI.
The business case for doing it in this order is on our main site: Why DMARC enforcement is the foundation of successful BIMI deployment. The broader sequence is in The right order: SPF, DKIM, DMARC, then BIMI.
What a BIMI-ready DMARC record looks like
A record on _dmarc.example.com that meets every check above:
v=DMARC1; p=quarantine; sp=quarantine; rua=mailto:dmarc-reports@example.com
p=reject works just as well. What matters is that neither p nor sp is none.
These records block BIMI:
v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com
v=DMARC1; p=reject; sp=none; rua=mailto:dmarc-reports@example.com
v=DMARC1; p=quarantine; pct=50; rua=mailto:dmarc-reports@example.com
Two leftovers need care:
pct.pctis historic. Don't add it, and remove it from old records (pct is historic: how to phase in DMARC enforcement now). Some BIMI documents still mentionpct=100because they follow the older DMARC standard. Apctbelow 100 disqualifies BIMI.t=y. This is the current DMARC testing flag. There's no established rule for how BIMI receivers treat it, so remove it before you rely on BIMI (DMARC tags explained: p, sp, np, adkim, aspf, rua, ruf, fo, and t).
Check subdomains separately. A separate _dmarc record on a sending subdomain at p=none takes BIMI away from mail sent from that subdomain, even when the parent domain is at p=reject (Subdomain policy (sp)).
Enforcement is necessary, not sufficient
Passing every DMARC check gets you into BIMI processing. It doesn't guarantee a logo.
- Publishing a record "is not sufficient." The domain owner "may also need to have a sufficiently strong reputation," and the receiver may apply its own reputation heuristics.
- Yahoo shows logos only on bulk mail, and only when it sees "sufficient reputation and engagement for the sending email address."
- Gmail requires a VMC or CMC.
- Microsoft hasn't documented BIMI logo display in Outlook.com or Microsoft 365.
And BIMI doesn't move mail into the inbox. BIMI does not change message delivery; it is a display signal on top of strong authentication. More on that in Why BIMI is not a deliverability shortcut.
What else BIMI needs, once DMARC is ready
- A BIMI DNS record at
default._bimi.example.com(BIMI requirements checklist). - A logo in the SVG Tiny PS format (SVG Tiny PS logo requirements).
- A VMC or CMC where the provider requires one. Gmail does; Yahoo doesn't. A VMC is issued against a registered trademark. A CMC is for a logo that has been used on your own website, on the same domain, for at least 12 months, checked through the Internet Archive. The official requirements list additional CMC routes. More on choosing: Is VMC still worth it now that CMC exists?
The full rollout, in order, is in How to move from DMARC enforcement to BIMI.
Common mistakes
- Ordering a VMC or CMC while the domain is still at
p=none. The certificate won't do anything until DMARC is enforced. - Enforcing the apex but leaving
sp=none, or a subdomain_dmarcrecord atp=none. - Leaving a legacy
pctbelow 100, ort=y, in the record. - Assuming a vendor stream passes DMARC when it isn't aligned. Check the exact stream in your aggregate reports first (A field-by-field walk-through of a DMARC aggregate report, How to add a third-party sender without breaking DMARC).
- Treating BIMI as the security control. DMARC enforcement is the control. BIMI is the display on top.
Free DMARC account
Your logo needs DMARC enforcement first
Monitor DMARC on the way to quarantine or reject. Once you're there, our team can help with your VMC or CMC and your BIMI record.
- DMARC results per sender before you enforce
- A clear view of what still fails alignment
- Help with your VMC or CMC and BIMI record
FAQ
Does BIMI require DMARC?
Yes, at enforcement. Receivers following the BIMI draft skip BIMI unless the message passes DMARC and the policy is p=quarantine or p=reject.
Can we set up BIMI while DMARC is at p=none?
You can publish the record, but nothing will happen. BIMI processing "MUST NOT be performed" at p=none, and Google and Yahoo both require quarantine or reject.
Does the subdomain policy matter?
Yes. sp=none stops BIMI, and so does a subdomain's own _dmarc record at p=none (Subdomain policy (sp)).
Do we still need pct=100?
Leave pct out. It's historic. If an old record still has it, remove it, and never leave it below 100 (pct is historic: how to phase in DMARC enforcement now).
Will the logo show everywhere once we're at enforcement?
No. Each provider decides, and some also weigh reputation and volume. If it doesn't show, work through Why your BIMI logo is not showing.