A missing BIMI logo does not tell you which component of your setup broke. To isolate what went wrong, check three things separately: one received message, the DNS records and files published for it, and the recipient’s provider and client. Even when every technical check passes, display is not guaranteed, because the draft’s display model leaves final rendering decisions entirely to receiver discretion. The guide chapter BIMI: showing your logo in the inbox covers the broader deliverability picture.
Define your exact symptom before changing records: an absent brand avatar, a missing verified checkmark, or no message in the inbox at all. Gmail can display a CMC-backed avatar without its verified checkmark, because the checkmark belongs to the VMC path, as explained in Google’s avatar and checkmark distinction. If the real problem is a message that never arrived, changing certificates answers a different question.
Preserve the evidence for this message
Save the full received source, message ID, transmission and receipt timestamps, visible From domain, sending service, and whether the delivery route was direct or forwarded. Document the mailbox provider separately from the desktop or mobile client, noting application version, destination folder, and view. Evaluate only the Authentication-Results header injected by the receiving mail system; a success header added by your outbound sending relay is not receiver validation (RFC 8601 on the trust boundary).
For DMARC, a passing SPF or DKIM identifier must align with the visible From domain. An unaligned pass does not count, but only one of the two mechanisms needs to align. Even a DMARC pass does not establish business authorization, message safety or inbox placement (DMARC message authentication, RFC 9989).
Record the exact DMARC and BIMI TXT strings, query hostnames, and observation timestamps. For standard diagnosis, query default._bimi.<From-domain>, looking for a single valid record beginning with v=BIMI1. With custom selectors or subdomain fallback, trace the exact lookup path rather than assuming an apex domain check covers the message. These mechanisms come from BIMI draft 14, a work in progress, and do not represent identical behavior across all receivers. See the draft’s assertion discovery and assertion record definition.
Fetch the exact HTTPS URLs referenced in the record without authentication, saving response headers and file contents. A successful fetch establishes access from your location at that time, nothing more. Inspect the certificate authority status and the actual certificate file, not merely a .pem filename extension. The web host’s TLS certificate secures HTTPS transport; the mark certificate inside the PEM is a separate credential. Google’s file checks and the draft’s VMC retrieval transport cover this retrieval stage.
For a VMC, inspect digital signatures, certificate chain, validity window, revocation status, certificate profile, and embedded SVG, following the draft’s issuance and profile checks; receiver trust-store membership and Certificate Transparency acceptance remain checks that the receiver controls. Verify the certificate’s SAN relationship to the assertion domain and selector (VMC domain checks). This fetch specification is also a work-in-progress draft.
What does the recipient’s provider require for BIMI?
Provider documentation checked: 15 September 2026.
Gmail: Google requires a VMC or CMC, with the certified SVG and issued chain hosted in a public HTTPS PEM file, including intermediate and root certificates in the specified order. A documented empty l=; tag next to an a= PEM URL is not automatically an error (Google’s BIMI setup).
Inspect the vector graphic embedded in the certificate. Google requires SVG Tiny PS with absolute width and height of at least 96 pixels, excluding root x or y attributes, external links, scripts, and animations. A centered square, solid background, maximum size of 32 KB, and a desc element are recommendations (Google’s BIMI setup).
Google’s documentation still requires p=quarantine or p=reject with pct=100 in its BIMI setup, whereas RFC 9989 removes pct and defaults to non-testing mode t=n (DMARC testing mode, removal of the percentage tag). This documentation discrepancy does not establish Google’s deployed protocol behavior, so don’t tighten DMARC in order to debug a logo.
Yahoo: Yahoo requires a BIMI record referencing valid SVG, DMARC at quarantine or reject, bulk email volume, and sufficient reputation and engagement for the sending address. No numerical score is published. A VMC is not currently mandatory, though providing one informs eligibility. On desktop, Yahoo and AOL document the logo in opened messages; on mobile, in message lists and opened messages (Yahoo’s BIMI criteria).
Apple Mail: Client support begins with macOS Ventura 13, iOS 16, and iPadOS 16. The receiving email service must be listed for BIMI, verified by Apple, check message and domain compliance, validate trusted Evidence Documents, and append required headers. Outbound sender headers cannot satisfy receiver duties, and Apple’s documentation does not confirm blanket CMC acceptance (Apple’s receiving-provider requirements).
Troubleshooting a dual failure: broken hosting and unaligned mail
The following is an invented evidence log, not a performed test. Suppose a bulk newsletter from updates@cedar.example is opened in Gmail web’s Spam folder without an avatar (initial observation T0). No profile or contact avatar is configured. Assume cedar.example acts as Author and Organizational Domain, with one From header, no BIMI-Selector, no forwarding, no trusted ARC or local-policy exception and no alternate aligned signature.
The active DMARC policy is p=quarantine, with relaxed alignment, no sp=none, and no testing request. Its existing pct=100 is an example input, not a publication recommendation; under current standards pct is obsolete and absent t defaults to n.
The query default._bimi.cedar.example returns exactly one applicable record: v=BIMI1; l=https://cedar.example/identity/mark.svg; a=https://cedar.example/identity/mark.pem. No custom or local-part selector applies.
Assume that an unauthenticated fetch of that SVG returns HTTP 200, MIME type image/svg+xml, and expected vector paths. Recorded format checks verify SVG Tiny PS, absolute width="120" and height="120", with no root x or y, external resources, scripts, or animations. Its square canvas, solid background, 18 KB size, and desc tag satisfy Google’s recommendations. These are assumed fixture properties.
Evidence at T0 | What it establishes | Next check and unresolved status |
|---|---|---|
| Record and files | The ordinary record and SVG checks above pass; the exact mark.pem URL returns HTTP 404. | The hosting or configuration owner must make the intended issued PEM available, then retrieve and inspect it again. Keep the failed response. |
| Certificate | A note says a VMC was requested. Issuance, validity, SAN coverage, embedded SVG, chain, revocation and receiver trust are unknown. | Obtain issuer status and inspect the issued file against the certificate checks above. A request is not issuance. |
| Received message | Trusted receiver results show spf=pass smtp.mailfrom=relay.example.net, dkim=pass header.d=relay.example.net and dmarc=fail header.from=cedar.example. The service domain is unrelated; neither identifier aligns even in relaxed mode. | The sending-service owner investigates aligned authentication for this stream. Verify a later authorized test with the same intended From; repairing the hosting cannot change this message’s authentication. |
| Provider and client | Gmail web’s missing logo is observed. The receiver’s BIMI decision, fetched or cached version, private eligibility and display reason are unavailable. | Keep these unknown. Do not assign caching or reputation as the cause. |
The log identifies two distinct problems: a broken HTTPS link (HTTP 404) and a failed DMARC check. It does not prove that Gmail fetched the failing URL, because authentication can stop BIMI processing before assertion discovery happens. The incidents chapter on diagnosing DMARC failures covers authentication troubleshooting.
Now suppose, hypothetically, that at T1 the exact URL returns the issued complete PEM. Issuer evidence confirms current, non-revoked status; the chain and profile checks and the cedar.example domain checks succeed; the embedded mark matches the intended SVG. A new direct message with the same From shows dkim=pass header.d=cedar.example and dmarc=pass header.from=cedar.example. SPF may still pass for the unrelated relay.example.net, which is acceptable: an aligned passing DKIM signature satisfies DMARC (DMARC message authentication, RFC 9989).
Keep the policy, selector, SVG and client unchanged. If a certificate check fails, document the defect before proceeding. If the logo still does not appear after authentication and certificates both pass, record the T1 observation with source, timestamps, URLs and file identities for provider or client troubleshooting. Gmail’s private trust, eligibility and cache state remain unknown, and no universal waiting period guarantees display (receiver caching limits, BIMI display model).
For next steps, consult Check provider and certificate readiness or Publish the corrected BIMI record and files.
Frequently asked questions
Does a passing DMARC check mean the logo has to appear?
No. Even when every technical check passes, display is not guaranteed because the draft display model leaves final rendering decisions entirely to receiver discretion.
Why does Gmail show the avatar but not the verified checkmark?
Gmail can show a CMC-backed avatar without its verified checkmark, because the checkmark belongs to the VMC path.
Which Authentication-Results header counts when diagnosing BIMI?
Use only the Authentication-Results header added by the receiving mailbox provider. An authentication header injected by your own outbound sending server does not reflect receiver evaluation.
Do both SPF and DKIM need to align for DMARC?
No. DMARC requires that only one passing mechanism aligns with the visible From domain. If DKIM passes with domain alignment, SPF does not need to align.
Should I tighten DMARC to debug a missing logo?
No. Do not tighten your DMARC policy from quarantine to reject solely to debug a missing logo. The discrepancy between Google’s documented pct=100 condition and current RFC 9989 does not establish Google’s deployed protocol behavior.


