Skip to main content
  1. Knowledge base
  2. Email security

BIMI DMARC Policy Not Enforced: Why Your Logo Never Shows

A BIMI DMARC policy not enforced finding means your domain publishes a BIMI record, but its DMARC policy is p=none or covers less than 100% of mail. Mailbox providers then skip the logo without any error. Move DMARC to p=quarantine or p=reject with pct=100, then retest.

BIMI is an email standard that lets a domain publish a brand logo in DNS so that mailbox providers can display it beside messages that pass authentication. The logo is a reward for proving the domain is protected. A DNS record alone does not switch it on.

What causes a BIMI logo to never appear?

Teams often treat BIMI as a branding project. Marketing buys a Verified Mark Certificate (VMC), design prepares an SVG, and someone publishes the record:

default._bimi.example.com. 3600 IN TXT "v=BIMI1; l=https://example.com/brand/logo.svg; a=https://example.com/brand/vmc.pem"

The record is valid and the certificate is valid, yet nothing shows up. BIMI is only evaluated for mail that passes DMARC, and the sending domain's policy has to be enforcing. A typical gap looks like this:

_dmarc.example.com. 3600 IN TXT "v=DMARC1; p=none; rua=mailto:[email protected]"

Other variants cause the same result:

  • p=quarantine; pct=25, where only a quarter of failing mail is subject to the policy.
  • A strong policy on the organizational domain, but a weak sp=none that covers the subdomain you send from.
  • A policy that enforces, but legitimate mail fails alignment, so those messages never qualify.

Requirements differ by mailbox provider, and some also require the VMC or a similar certificate before they show anything. Check each provider's current documentation. Enforced DMARC is the common prerequisite, and it is the one most often missing.

The missing logo points to a bigger problem. If DMARC is at p=none, receivers are told to deliver spoofed mail anyway, so anyone can send messages that claim to be from your domain and reach inboxes. The article on the DMARC p=none trap covers that exposure in detail.

An auditor flags the combination because what the organization says and what it enforces don't match. You are paying for brand assurance while leaving the domain open to impersonation.

The costs are concrete:

  • The VMC fee and design work produce no visible result.
  • Phishing that uses your exact domain is not blocked.
  • Support and fraud teams spend time on abuse that enforcement would have stopped.
  • Customers cannot tell real mail from fake, and trust in the brand drops.

Attackers can also exploit half-finished BIMI deployments. See how a fake brand logo can be displayed without a VMC for what happens when the checks around BIMI are weaker than assumed.

How do I detect the enforcement gap?

Query the DMARC record and read the policy tags:

dig +short TXT _dmarc.example.com

Then confirm the BIMI record exists at the default selector:

dig +short TXT default._bimi.example.com

Check these fields in the DMARC output:

Tag Passing value Failing value
p quarantine or reject none or missing
pct absent or 100 any value below 100
sp absent, or enforcing none

If you send from a subdomain, query _dmarc on that subdomain too. A subdomain with no record of its own inherits the organizational policy. A subdomain with its own record uses that record instead.

DNS only tells you what is published. To learn whether real mail passes, read the aggregate reports sent to your rua address. They show which sources pass SPF or DKIM with alignment, and which fail. If a legitimate sender fails alignment, fix that first. The DMARC alignment bypass article explains why SPF and DKIM can pass while DMARC still fails.

How do I fix a BIMI DMARC policy that is not enforced?

Work in stages so you do not block your own mail.

  1. Collect reports. Keep p=none with a rua address for a few weeks and list every source sending as your domain.
  2. Fix alignment. Configure DKIM signing with your own domain for each legitimate service, and align the return-path where you rely on SPF.
  3. Ramp up gradually. Move to p=quarantine with a low pct, then raise it as reports stay clean:
_dmarc.example.com. 3600 IN TXT "v=DMARC1; p=quarantine; pct=25; rua=mailto:[email protected]"
  1. Reach full enforcement. Set pct=100, or remove the tag since 100 is the default. Many teams then move to reject:
_dmarc.example.com. 3600 IN TXT "v=DMARC1; p=reject; sp=reject; rua=mailto:[email protected]"
  1. Verify. Rerun the dig commands, send test mail to accounts at the providers you care about, and allow time for caches and provider re-evaluation. Display is not instant, and providers may cache their decisions.

DMARC itself is defined in RFC 7489, which is the reference for tag behavior such as pct and sp.

How would monitoring catch this?

A one-time check misses regressions. Someone can loosen pct during an incident, or a new subdomain can launch with no policy. Continuous validation should compare three things on every run: a BIMI record is present, the DMARC policy is enforcing for the exact sending domain, and pct is 100. It should alert when the BIMI record exists but DMARC does not meet the bar. That pairing is the signal, because a BIMI record alone looks healthy.

Common questions

Does BIMI work with DMARC p=none?

No. A p=none policy does not meet the enforcement requirement, so providers that support BIMI will not display your logo. Mail may still be delivered normally, and nothing will tell you the logo was skipped. Move to quarantine or reject first.

Can I use p=quarantine with a pct below 100?

Generally not. The expectation is that the policy applies to all mail, so a pct below 100 leaves part of your traffic unenforced and typically disqualifies the domain. Treat a partial rollout as a temporary step and set pct=100 before you expect any logo.

Why is my BIMI record valid but no logo appears?

A valid record is only one condition. The logo also depends on DMARC enforcement, authenticated messages, a correctly formatted SVG, and, at providers that require it, a valid certificate. Start with the DMARC policy, since it is the most common silent failure.

Key takeaways

  • BIMI needs enforced DMARC: p=quarantine or p=reject with full coverage.
  • Providers skip the logo silently, so a missing logo is your only signal.
  • Check p, pct and sp on the exact domain you send from.
  • Raise enforcement in stages, guided by aggregate reports.
  • SetEnforce scans for the BIMI record and the DMARC policy together, so a published logo with a non-enforcing policy is reported as a finding.

Check whether your own domain gets this right. Scanning is free and needs no account.

Scan your domain

All articles