Why Isn't My BIMI Logo Showing?
A BIMI logo not displaying after setup is most commonly caused by one of three categories: a configuration error (missing certificate, wrong DNS location, invalid SVG), a timing issue (propagation delay, provider recognition delay), or a provider-specific constraint (the provider doesn’t support BIMI, or requires a certificate type you haven’t provided). This article covers post-setup display absence — if you’re seeing a specific validation error, see Common BIMI Validation Errors.
Post-Setup Display Diagnostic
| Condition | Category | How to Check / Resolve |
|---|---|---|
| DNS not yet propagated | Timing | Wait 24–48 hours after DNS publication before testing. Run the BIMI checker to confirm the record resolves globally. |
| Certificate URL not yet live or returning error | Config | Confirm the URL in the a= tag returns a direct HTTP 200 with no redirects. CAs sometimes take time to provision the hosted certificate after issuance. |
| Gmail recognition delay | Timing | Gmail has its own validation cycle separate from DNS propagation. As of mid-2026, newly published BIMI records can take up to 7 days to begin displaying in Gmail. This is normal; no action needed. |
| Provider does not support BIMI | Provider | Not all providers display BIMI logos. Microsoft 365 does not use the BIMI infrastructure as of mid-2026. See Does Microsoft 365 Support BIMI? |
| Provider requires VMC but only CMC is present | Provider | Gmail requires a VMC for blue checkmark display. A CMC will not satisfy the Gmail requirement for the verified indicator. Other providers may accept either. |
| SVG not SVG Tiny PS compliant | Config | A standard SVG 1.1 file fails BIMI format validation. The file may display correctly in a browser but fail provider-side validation. Re-validate with BIMI Readiness Assessment. |
| Logo showing inconsistently (some messages, not others) | Provider | Some providers apply additional sender reputation signals beyond BIMI compliance. High bounce rates, spam complaints, or inconsistent sending volume can suppress display. BIMI compliance does not override sender reputation or BIMI logo display behavior. |
| Logo showing in some inboxes but not others for same provider | Timing | Provider-side caching means individual inboxes may update at different times after a new record is published. Usually resolves within a few days without intervention. |
| Certificate is expired | Config | An expired VMC or CMC causes immediate display loss. The certificate expiry date is encoded in the certificate file. See What Happens When a VMC Certificate Expires? |
When to Escalate
If the BIMI checker confirms the record resolves correctly, the certificate URL returns a valid 200, the SVG passes Tiny PS validation, and DNS has been propagated for more than 7 days — and Gmail still shows no logo — the most likely remaining cause is the provider’s own cache or recognition queue. In most cases this resolves without intervention within 2 weeks of correct publication.
Persistent absence beyond 2 weeks with a fully passing BIMI checker result warrants contacting the certificate provider’s support to confirm the certificate itself is correctly formed and the hosted URL is set up as expected.
Frequently Asked Questions
My BIMI checker shows everything passing. Why is Gmail still not showing the logo?
a= tag and that DMARC is at full enforcement with pct=100. Persistent absence beyond 2 weeks warrants contacting your certificate provider's support.The logo shows in Gmail but not in Outlook. Is something broken?
The logo was showing before and stopped. What could have caused this?
p=none. Run the BIMI checker to identify which element has changed.