BIMI · Inbox logos
BIMI: the logo beside your email — after two gates, not one DNS record
- Is your DMARC at p=quarantine (100%) or p=reject — organisational and sending domains? No → BIMI is later; the rollout is now.
- Is sp anything but
none, and does your mail pass DMARC with alignment? No → fix policy first. - For Gmail: do you hold a registered trademark (→ VMC) or a logo with 12+ months of public use (→ CMC)? Neither → Gmail display is ~a year away whatever you do; Yahoo/Fastmail may still be open (table below).
The record and the logo file
v=BIMI1; l=https://yourdomain/logo.svg; a=https://…/certificate.pem- Selectors exist (
<selector>._bimi) for different brands/streams;defaultis the standard one. - With a certificate, the certificate's PEM file itself embeds the logo; Google's certified route uses an empty
l=with the cert ata=— Google states the standalone-SVG route is not supported in Gmail. - The SVG is a strict profile (SVG Tiny PS): square, a
<title>naming your organisation, no scripts, no external references, no animation. Google adds: at least 96×96 px absolute dimensions; ≤32 KB is a recommendation. Fastmail's bar is tighter — under 16 KB — so build to 16 KB and satisfy everyone. - Display timing: Google says the logo may take up to ~48 hours to appear after everything validates.
Receiver reality — the table the hype skips
| Receiver | What it takes (their documentation) |
|---|---|
| Gmail | Gate + certificate mandatory: VMC or CMC. Checkmark: VMC only. No cert, no display — the strictest house. |
| Yahoo | Four conditions in Yahoo's words: valid BIMI record/SVG, DMARC quarantine/reject, bulk mail, and “sufficient reputation and engagement.” No certificate mentioned — and no thresholds published, so a low-volume sender may qualify on paper and never display. Receiver discretion, honestly labelled. |
| Apple Mail | BIMI supported (iOS 16+/macOS Ventura 13+/iCloud.com); Apple's text requires evidence documents (“VMCs and other forms of BIMI Evidence Documents”) and — unusually — requires both sender and receiving provider to qualify. Whether Apple accepts the CMC is not stated by Apple; treat Apple+CMC as unconfirmed. (Apple's separate Branded Mail in Business Connect is NOT BIMI: a raster logo upload + a “Mail Verified” badge, iOS 18.2+ — a parallel program some businesses will prefer.) |
| Fastmail | Self-asserted works: publish record + compliant SVG (<16 KB); a VMC is an optional step in its own sender guide. The friendliest receiver — a good first proof. |
| Microsoft (Outlook.com) | No receiver-side BIMI display — Microsoft supports BIMI for senders only (per Microsoft's own Q&A). Your logo project buys nothing in Outlook inboxes; plan expectations accordingly. |
The mark-evidence ladder (and the two clocks)
| Evidence | Requirement | Unlocks |
|---|---|---|
| VMC | Registered trademark for the logo, verified by the CA | Gmail logo with checkmark; the broadest acceptance |
| CMC | Logo with ≥12 months of public use (DigiCert's stated requirement) — no registration needed | Gmail logo, no checkmark (Google's own announcement, Sept 2024) |
| Self-asserted | Just the record + SVG | Fastmail; partial elsewhere — never Gmail |
The two clocks: trademark registration runs ~6–12 months (Google's stated range); the CMC's prior-use requirement is 12 months. Both clocks start from things you do outside this guide (file the mark; use the logo publicly and keep evidence). A business launching today should start one clock now and treat BIMI as next year's project — which is also exactly how long the DMARC climb in gate 1 deserves.
The setup ladder (once the gates pass)
- DMARC enforcement confirmed by lookup (gate checker above) — including
sp. - Build the SVG to Tiny PS, ≤16 KB, square, titled; validate it (the BIMI Group publishes guidance/validators).
- Obtain the certificate (VMC or CMC) from a current issuer; host the PEM over HTTPS.
- Publish
default._bimiwith the certified shape (emptyl=, cert ata=) — or self-asserted shape where you're targeting self-asserted receivers first. - Verify with lookups + a real send to Fastmail/Gmail test inboxes; allow Google's ~48 h.
- Re-verify after any DMARC change — dropping back below enforcement quietly revokes the logo everywhere.
FAQ
My logo shows in Fastmail but not Gmail. Broken?
No — that's the receiver table working as documented. Fastmail accepts self-asserted; Gmail requires a certificate. The fix is evidence (VMC/CMC), not DNS.
We're at p=quarantine but pct=50 during rollout. Close enough?
The spec's exact asymmetry: quarantine with pct<100 is not accepted (reject tolerates partial percentages in the draft's text — don't build a plan on that wrinkle; go to 100%). Finish the climb, then BIMI.
Is the checkmark worth the trademark?
Only your brand strategy can price a blue check. What this guide can say: logo-without-check (CMC) covers the visual goal at Gmail for marks with a year of use; the checkmark is a trust garnish, not extra deliverability.
Sources
BIMI specification draft (gate conditions, record format, SVG profile) & BIMI Group guidance · Google — Set up BIMI + its Sept 2024 CMC announcement (certificate rules, checkmark, SVG sizing, 48 h) · Yahoo sender FAQ (four display conditions) · Apple — BIMI/evidence-document support pages · Fastmail sender guide (self-asserted, 16 KB) · DigiCert — VMC/CMC product & pricing pages (12-month prior use; pricing as printed) · Sectigo/Entrust transaction reporting.
Did this guide work for you?
Your reaction tells us whether this guide solved the problem it promised to solve.