No. BIMI does not move cold email from the spam folder to the inbox. BIMI Group's FAQ for senders states that BIMI does not change message delivery and calls it a display signal on top of strong authentication. It controls one thing: whether your logo appears next to the sender name, in mail apps that support it, after the message has already passed DMARC.
For cold outreach that makes BIMI an optional branding layer with strict entry rules. On the sending domains my team builds, SPF, DKIM and DMARC are live before the first email goes out, every new mailbox warms up for 10 to 14 days, and volume rises only after that. BIMI comes later, if at all, and usually on the main company domain, where buyers already know the name.
Delivery and display are two separate issues
Deliverability asks whether a message lands in the inbox. Display asks what it looks like once it is there. BIMI only touches display.
An IETF guidance draft for BIMI implementers says BIMI is not meant to instill additional trust in messages, and that a valid BIMI result tells you nothing about whether a message is spam, malware or phishing. The draft also leaves receivers free to run their own checks, such as sender reputation, before they show a logo. It does not discuss inbox placement.
So the dependency runs in one direction. Poor sender reputation can keep your logo hidden. The reverse never works - a logo cannot fix a bad sender.
The same draft describes BIMI as a driving factor for adopting authenticated email. I read that as the design intent: the logo rewards senders who authenticate properly, and it was never built to stand in for authentication. Google's BIMI setup page fits that reading. It walks through DMARC, logo files, certificates and DNS records and makes no promise about inbox placement.
What decides a cold campaign sits underneath all of this. In the campaigns my team runs, about 1 reply per 100 emails is a normal result, and it slides toward 0.5% once a campaign sends thousands a day.
The list, the offer and the sending setup move that number. A buyer decides after checking you out: your LinkedIn profile, your website, your published results. The logo is a small square in that check.
The DMARC requirement: enforcement or no logo
This is where most cold domains drop out. Google's BIMI requirements start with DMARC: messages must be authenticated by DMARC, so SPF or DKIM has to pass first. The policy then has to meet these conditions:
- The policy option (p) is set to quarantine or reject. Google says BIMI does not support p=none
- The percent option (pct) is set to 100, and Google's BIMI troubleshooting page repeats that any other pct value is unsupported
- SPF or DKIM aligns with the visible From domain, because BIMI Group ties the logo to that From domain through DMARC alignment
Yahoo's sender page also asks for a DMARC policy of quarantine or reject. It says nothing about pct or alignment.
If your DMARC record still reads p=none, BIMI stops right there, whatever logo or certificate you pay for. Fix the policy first and think about logos afterwards.
The logo file rules most guides skip
A lot of setups fail a second time at the file. Google says BIMI logos must be SVG files, specifically SVG Tiny Portable/Secure (SVG Tiny PS), a restricted version of SVG. BIMI Group's guide to BIMI logo files sets the root element's baseProfile attribute to tiny-ps and its version attribute to 1.2.
The remaining rules, at the time of writing:
- No scripts, animation or other interactive elements, no external links, and no x= or y= attributes on the root svg element (BIMI Group)
- A title element inside the file, which BIMI Group lists as required
- A square aspect ratio (BIMI Group)
- The image centered, because apps may crop it to a circle or a square with rounded corners (BIMI Group)
- A solid background color, which BIMI Group recommends because transparent backgrounds may not display as expected
- A file of 32 KB or smaller, which Google words as a recommendation ("should")
- Hosting on a web server that uses HTTPS (Google)
Check your exported file against these attributes before you order a certificate. The certification covers the logo as well as the domain, so a file you later have to redraw means paying for the process twice.
VMC vs CMC: which certificate Gmail wants
Gmail will not show a logo from a plain SVG record. Google requires third-party certification, either a Verified Mark Certificate (VMC) or a Common Mark Certificate (CMC).
Your trademark decides which one. For a VMC, the logo has to be trademarked with an intellectual property office that VMC issuers recognize. Without a trademark, Google says you can set up BIMI with a CMC instead.
Google recommends the VMC, and only the VMC is tied to the Gmail checkmark: Google says Gmail shows a checkmark next to senders verified with a VMC and mentions no checkmark for CMC senders.
The CMC is still fairly new. BIMI Group announced Common Mark Certificates in September 2024 as an option beyond the VMC, which needs a trademark or a registered government mark. Some older material has not caught up. BIMI Group's own sender FAQ still says Gmail and Apple require a VMC. For Gmail I follow Google's page, which accepts both.
| VMC (Verified Mark Certificate) | CMC (Common Mark Certificate) | |
|---|---|---|
| What your logo needs | A trademark with an IP office that VMC issuers recognize | No trademark |
| Logo in Gmail | Yes | Yes |
| Gmail checkmark | Yes, per Google | Google mentions none |
| Google's position | Recommended | Accepted |
| Documented effect on inbox placement | None | None |
For a founder the rule is short. With a registered trademark, a VMC gets you the logo and the checkmark. Without one, a CMC is Gmail's route to the logo. I have no verified certificate price to quote, and issuers set their own, so get a written quote that names every domain you want covered.
Where the logo actually shows
Gmail is covered above. Yahoo and Microsoft work differently.
Yahoo does not require a VMC for logos to appear in its apps. The catch sits in its other conditions. Yahoo shows logos only on bulk mail sent to a large number of recipients, does not display them on personal emails, and wants sufficient reputation and engagement for the sending address.
It publishes no volume threshold. A young cold domain with modest daily volume and little engagement history is a weak candidate. Do not count on a logo there.
Microsoft is the gap that matters most in B2B. Its BIMI page on Microsoft Learn, last updated July 2026, covers BIMI for mail sent through Customer Insights - Journeys, the marketing product in Dynamics 365. It says mail sent from other Microsoft products, such as Exchange Online, does not support BIMI yet.
That sentence is about sending. On whether Outlook inboxes display BIMI logos, I found no Microsoft statement. BIMI Group's infographic, last updated May 2025, places Microsoft on the "does not support" side, though its provider names sit inside images.
| Mailbox or product | Logo shown? | What it needs | Source |
|---|---|---|---|
| Gmail | Yes | DMARC at enforcement, SVG Tiny PS logo, VMC or CMC, BIMI record | Google Workspace Admin Help |
| Yahoo | Yes, on bulk mail | DMARC at quarantine or reject, enough reputation and engagement; no certificate | Yahoo Sender Hub |
| Mail sent from Dynamics 365 Customer Insights - Journeys | Can be set up; display depends on the receiving app | SVG logo on HTTPS, properly authenticated mail | Microsoft Learn |
| Mail sent from Exchange Online | Not supported yet, per Microsoft | Nothing applies | Microsoft Learn |
| Outlook inboxes | No Microsoft statement; BIMI Group lists Microsoft as not supporting | Nothing documented | BIMI Group infographic |
Before spending on a certificate, check which providers host the domains on your list. If most of your buyers sit on Microsoft mailboxes, you are paying for a logo they may never see.
Should a cold sending domain get BIMI?
Usually not. When my team runs cold email, we use separate sending domains, typically 10 to 20 of them carrying 20 to 40 mailboxes, and more when the client is a large company. Prospects have never seen those domain names, so a logo on them confirms very little about who you are.
Yahoo's conditions work against these domains too. New domains have thin engagement history, and Yahoo wants reputation and engagement before it shows anything.
Certificate scope is another open question. I have not found an official source that explains how certification works across a set of separately registered sending domains. Ask the issuer to confirm in writing before you assume one certificate covers them all.
Spend that budget on the basics first. Verified lists that keep bounces under 0.5% and a full warm-up for every mailbox decide whether mail lands. A logo changes neither. When a cold campaign stalls, I look at the list before the copy, and BIMI does nothing for either.
| Domain | BIMI? | Why |
|---|---|---|
| Main company domain (proposals, invoices, client email) | Consider it once DMARC is at enforcement | Buyers know the name, so the logo confirms it is really you |
| Newsletter or nurture domain | Consider it | Readers opted in, and Yahoo only shows logos on bulk mail |
| Cold sending domains | Skip | Unknown names, thin engagement history, unclear certificate scope |
| Any domain still warming up | Skip | No reputation yet for a receiver to rely on |
A checklist before you pay for a certificate
Work down the list and stop at the first no.
- SPF and DKIM pass on the domain you want to brand and align with its From address
- The DMARC record meets Gmail's enforcement rules described above
- Bounces and complaints on recent sends are under control
- Your domain reputation in Google Postmaster Tools has held steady for several weeks
- The domain is one buyers already recognize, usually the main company or newsletter domain
- A large share of your list reads mail in Gmail or Yahoo
- The logo file passes the SVG Tiny PS rules
- You know whether the logo is trademarked, so you know whether you need a VMC or a CMC
With a yes on every line, BIMI on that one domain is a reasonable branding step. When a cold campaign goes quiet, check DNS records, bounce numbers and the offer before anything visual. Fix the funnel first. The logo comes after.
Setting up a sending domain and wondering what is worth paying for? Book a call and I will help you decide whether BIMI belongs on your list.
Questions founders ask about BIMI for cold email
What does a BIMI record look like in DNS?
It is a TXT record at default._bimi.yourdomain. Google's example reads v=BIMI1;l=;a= followed by the HTTPS address of the certificate PEM file (the certificate file your issuer sends you, with the logo inside), with l= left empty because the SVG sits inside the PEM. Google says the logo can take up to 48 hours to appear after you add the record.
Can I publish BIMI without a certificate?
You can publish the record, but Gmail will not use it, because Google says it supports BIMI only with PEM files. BIMI Group's implementation guide calls the certificate step highly recommended but optional, and warns that self-asserted records have limited support across mailbox providers. Yahoo is the main exception, under its bulk mail conditions.
Do subdomains need DMARC enforcement too?
For BIMI, yes. BIMI Group's implementation guide says the DMARC policy must be at enforcement on the organizational domain (your main domain, such as yourcompany.com) and its subdomains, written for example as p=quarantine; sp=quarantine. The sp tag sets the subdomain policy. Google's page does not mention sp, so treat BIMI Group's rule as the stricter one to follow.
Which mailbox providers show BIMI logos?
BIMI Group's sender FAQ links support pages for Apple, AU, Fastmail, Gmail, Laposte, Onet Poczta, Yahoo, Zoho Mail, Zone and Zoner, and notes the list may be incomplete. Microsoft is not on it. For a B2B list, the useful question is how much of it runs on Google Workspace and how much on Microsoft.
Does Apple Mail show BIMI logos?
It does, under its own rules. Apple's developer page expects a verified BIMI evidence document, for example a VMC trusted by the mail provider. Apple uses the VMC as its example and does not name the CMC, so if many of your readers use Apple Mail, a trademarked logo with a VMC is the safer route.