Skip to content
  • There are no suggestions because the search field is empty.

Why your BIMI logo is not showing

A BIMI logo doesn't show when any link in the chain breaks: the mailbox doesn't display BIMI for that message, DMARC doesn't pass at enforcement, the BIMI record or the SVG has an error, the VMC or CMC is missing or doesn't match, or the provider decides your mail doesn't qualify. There's no bounce or error message to tell you which link broke, so work through the checks in order. The first three are quick to rule out.

For the broader picture of how display works across email clients, see Ensuring BIMI display across email clients on our main site. This article is the step-by-step diagnosis.

Step 1: Does this mailbox show BIMI at all?

Test in a place that's documented to show logos, with mail that qualifies:

  • Gmail shows BIMI logos with a VMC or CMC, on the web and in the apps. The checkmark appears only with a VMC, and "Non-Gmail web apps do not support this feature". Google also says the checkmark isn't shown in "Apple Mail or other mail applications."
  • Yahoo and AOL show logos in their mobile apps (message list and read view) and in the read view of desktop webmail. They show them only on bulk mail.
  • Apple Mail supports BIMI on iOS 16, iPadOS 16, macOS Ventura 13 or later, and iCloud.com. Logos appear only if both the sender and the recipient's email provider meet the requirements. Apple says BIMI works with "VMCs (Verified Mark Certificates) and other forms of BIMI Evidence Documents."
  • Microsoft: Microsoft hasn't documented BIMI logo display in Outlook.com or Microsoft 365.

Two common false alarms come from this step. One is checking in Outlook or a third-party mail app. The other is sending a single personal message to a Yahoo account, which won't show a logo because Yahoo shows them only on bulk mail.

Step 2: Does the message pass DMARC at enforcement?

This is the first thing to rule out, because it's entirely in your hands. Under the BIMI draft (§7.1), the receiver skips BIMI entirely unless all of this is true:

  • DMARC passes for the From domain of that specific message.
  • The policy on the From domain and its organizational domain isn't p=none.
  • The record doesn't have sp=none.
  • If p=quarantine and a pct tag is present, it's pct=100. Better: remove pct, which is historic (pct is historic: how to phase in DMARC enforcement now).

Also remove t=y. No BIMI source says how receivers treat it.

Two things catch people out here:

If the receiver adds a BIMI result to the Authentication-Results header, look for it in a test message. Typical values include bimi=skipped (message failed DMARC), bimi=none (no record found), bimi=fail (record, discovery, or validation error), and bimi=declined. Not every receiver adds it, so a missing result doesn't prove anything.

Step 3: BIMI record not published, or not valid?

If receivers can't find exactly one valid record where they look, nothing after this step happens. Check:

  • The name. It's a TXT record at default._bimi.example.com, or at the selector your mail uses if you set a BIMI-Selector header.
  • Exactly one record. Two TXT records at that name, or none, means no BIMI.
  • v=BIMI1 first, in exactly that case. Receivers "MUST NOT attempt to fix syntactical or capitalization errors" (§4.3). v=bimi1 is ignored.
  • l= is an HTTPS URL to the SVG, and a= is an HTTPS URL to the PEM. Without a=, Gmail has no certificate to check.
  • Subdomain fallbacks. A From subdomain with no record of its own uses the organizational domain's record. A declination record on the subdomain (v=BIMI1; l=; a=;) turns it off deliberately. Check nobody published one by mistake.

The full record checklist is in BIMI requirements checklist.

Step 4: Can the logo be fetched, and is it valid SVG Tiny PS?

  • The file isn't SVG Tiny PS. Look for a wrong baseProfile, a missing <title>, an embedded raster image, scripts, or x/y on the root element (SVG Tiny PS logo requirements).
  • For Gmail, the file is smaller than 96 px, or uses relative dimensions such as width="100%".
  • Retrieval fails. Typical causes: HTTP instead of HTTPS, or a TLS problem; blocked user agents, geo or IP restrictions, or hotlink protection; the wrong Content-Type (it should be image/svg+xml) or forced-download headers; redirect chains that end on the wrong file.
  • The file is too big. The profile says it SHOULD NOT exceed 32 KB, and receivers may refuse larger files.

A quick check from any terminal is curl --head https://example.com/bimi/logo.svg. You want a 200 and Content-Type: image/svg+xml.

Step 5: Is the VMC or CMC valid and matching?

  • Expired. Mark certificates are valid for at most 398 days.
  • Not retrievable. The PEM isn't publicly reachable over HTTPS, or the intermediate and root certificates aren't appended.
  • Logo mismatch. The SVG at l= differs from the logo embedded in the certificate. When both are present, the receiver must check they're identical. Point l= at the exact file that was certified, or re-issue the certificate.
  • Domain not covered. The Mark Certificate Requirements tie display to domains in the certificate's Subject Alternative Name field. If you send from a domain the certificate doesn't list, check with your certificate authority.

Gmail needs one of the two. 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?

Step 6: Is the provider choosing not to show it?

Some causes aren't in your DNS at all.

  • Reputation. Publishing a record "is not sufficient." Receivers may require "a sufficiently strong reputation" or apply their own reputation heuristics. Providers "can choose not to display your logo if they think your reputation is questionable."
  • Yahoo's conditions. Yahoo wants bulk mail and "sufficient reputation and engagement for the sending email address." It doesn't publish a volume threshold: "We will not specify a volume threshold".
  • Gmail's filtering. "Verified emails go through Gmail's normal anti-abuse checks. If the emails pass, the sender's verified brand logo is shown".

None of this means your mail is being filtered because there's no logo. BIMI doesn't change delivery (Why BIMI is not a deliverability shortcut).

Step 7: Have you waited long enough?

It can take up to 48 hours for your logo to show in Gmail. Client caches can take longer, so wait and re-check with fresh mail. At Yahoo, changes can take time to propagate; check on the web at mail.yahoo.com with a clear cache. Don't change three things at once and then re-check an hour later. Fix one item, send fresh mail, and wait.

Common mistakes

  • Testing with one personal message to Yahoo. That isn't bulk mail, so no logo is shown, by design.
  • Testing in Outlook or a third-party client instead of the provider's own app.
  • Checking the apex _dmarc record while the mail comes from a subdomain with its own p=none.
  • Fixing the SVG but not re-issuing the certificate that embeds the old logo.
  • Editing again within 48 hours and never letting caches settle.

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

Create a free DMARC accountTalk to an expert

FAQ

It shows in Gmail but not Yahoo. Why?

Yahoo shows logos only on bulk mail from senders with enough reputation and engagement. A Gmail-ready setup can still fall short of that.

Why doesn't BIMI show in Outlook?

Microsoft hasn't documented BIMI logo display in Outlook.com or Microsoft 365.

We fixed it. How long until it shows?

Up to 48 hours in Gmail. Client caches can take longer.

Is our mail being filtered because there's no logo?

No. BIMI "does not change message delivery."

If you haven't set BIMI up yet, start with What is BIMI, and why DMARC comes first and the rollout in How to move from DMARC enforcement to BIMI.