A marketing lead asks why the brand logo still doesn’t appear next to messages in Gmail two weeks after BIMI was set up. The DNS record is there, the SVG renders, the VMC is paid for. The logo still won’t show. BIMI quietly demands four things to be true simultaneously: DMARC at enforcement, a published BIMI record, a valid SVG Tiny Portable/Secure, and a Verified Mark Certificate. Any one of them broken, and the logo silently doesn’t render — receivers don’t surface why.
What’s happening
BIMI (Brand Indicators for Message Identification) lets receivers display a verified brand logo next to messages from an authenticated domain. Gmail requires DMARC at p=quarantine or p=reject (with pct=100 and sp= set), a default._bimi.<domain> TXT record referencing an SVG and a VMC, the SVG hosted over HTTPS in SVG Tiny P/S format, and the VMC issued by a CA Gmail trusts (DigiCert, Entrust, IdenTrust, SSL.com). Yahoo, Apple, and Microsoft have similar but not identical rules.
How to verify
Walk the four prerequisites:
dig +short TXT _dmarc.example.com
dig +short TXT default._bimi.example.com
curl -I https://example.com/path/to/logo.svg
curl -I https://example.com/path/to/vmc.pem
Then run the record through bimigroup.org/bimi-generator (validator mode) or easydmarc.com/tools/bimi-record-checker. Common failure modes the validator catches: SVG is not Tiny P/S, VMC chain incomplete, DMARC at p=none, or DMARC pct below 100.
The fix
- Confirm DMARC is at
p=quarantineorp=rejectwithpct=100on both the apex and any subdomain you want logos for.sp=must also be at enforcement.p=nonewill never qualify, period. - Validate the SVG with the BIMI Group validator. SVG Tiny P/S has strict rules: no scripts, no external references, square viewBox, max file size around 32 KB. Most marketing SVGs need a manual rewrite to comply.
- Verify the VMC chain with
openssl x509 -in vmc.pem -textand confirm the issuer is on the receiver’s trusted list. Self-signed and DV certificates do not work. - Host SVG and VMC over HTTPS with no redirects, no auth gates, and a valid certificate. A 301 to www breaks BIMI on some receivers.
- Wait 48–72 hours after publication. Gmail caches BIMI lookups and won’t pick up changes immediately. If nothing renders after a week, recheck the record against the validator before assuming the receiver is at fault.
For brand and engineering teams that share responsibility for BIMI, Stack Harbor coordinates the SVG, VMC, and DMARC pieces under managed cPanel operations so the logo lights up on the first deploy.