BIMI requirements checklist
BIMI requirements come in five groups: DMARC at enforcement, an SVG Tiny PS logo, HTTPS hosting, a VMC or CMC where the mailbox provider requires one, and a single BIMI record in DNS. Miss any one item and the logo won't show, and you won't get a bounce telling you which item it was. Work through the list below in order, because the later items depend on the earlier ones.
The rules come from the BIMI specification, the SVG Tiny PS logo profile, the certificate requirements, and each provider. They don't always agree. Where they differ, this checklist follows the stricter requirement and says so.
1. DMARC (do this first)
- [ ]
p=quarantineorp=rejecton your organizational domain and on the From domain you send from. The BIMI draft requires a "strong" policy on both, and Google and Yahoo require quarantine or reject. - [ ]
spisn'tnone. If the record has a subdomain policy, it must not benone. Check any separate_dmarcrecord on a sending subdomain too, because one atp=nonedisqualifies that subdomain (Subdomain policy (sp)). - [ ] No
pctbelow 100.pctis historic, so leave it out and remove it from old records (pct is historic: how to phase in DMARC enforcement now). Google still requires thatpctnot be below 100, and apctbelow 100 percent is not accepted for BIMI. - [ ] No
t=y. There's no established rule for how BIMI receivers treat the DMARC testing flag. Remove it. - [ ] Mail actually passes DMARC. Your policy alone isn't enough: the specific stream that should show the logo has to pass with aligned SPF or DKIM. Aligned DKIM as preferred, and an ESP that can't set a custom Return-Path is fine if its DKIM aligns. Aligned DKIM also survives forwarding, where SPF can break (Email forwarding, SRS, and ARC). Confirm each stream in your aggregate reports (A field-by-field walk-through of a DMARC aggregate report).
Why DMARC has to come first: What is BIMI, and why DMARC comes first.
2. Logo file
Full detail is in SVG Tiny PS logo requirements. The short version:
- [ ] SVG Tiny PS. The root
<svg>element hasxmlns="http://www.w3.org/2000/svg",version="1.2", andbaseProfile="tiny-ps". - [ ] A
<title>that's present once and not empty. It SHOULD be 64 characters or fewer. - [ ] Nothing disallowed. That means no scripts, animation, links, embedded raster images, multimedia, or interactive elements.
- [ ] Gmail's extras. A minimum of 96 × 96 px, set in absolute pixels, is required. A square, centered logo on a solid background, 32 KB or smaller, is recommended. No
x=ory=on the root element. - [ ] The same logo everywhere. The SVG you submit to the certificate authority is the one embedded in your VMC or CMC. Google: "Your SVG file (logo) and VMC/CMC are embedded in the PEM file."
3. Hosting
- [ ] HTTPS only. The logo (
l=) and certificate (a=) URLs must use HTTPS. Use TLS 1.2 or later. - [ ] Served as
image/svg+xml, and publicly retrievable. No login, geo or IP restrictions, bot filtering, or hotlink protection, and no redirect chains that end on the wrong file. These are all common reasons fetches fail. - [ ] The PEM is publicly fetchable too, with the full chain. To append the intermediate and root CA certificates to the PEM "in the order issued."
4. VMC or CMC
Requirements differ by provider:
- [ ] Gmail: a certificate is required, either a VMC or a CMC, and a VMC is the recommended choice. The checkmark appears only for senders verified with a VMC.
- [ ] Yahoo: "We currently do not require VMCs." If your record includes one, Yahoo uses it "to inform the overall BIMI eligibility". Yahoo's page doesn't mention CMCs.
- [ ] Apple Mail: Apple says BIMI works "with VMCs (Verified Mark Certificates) and other forms of BIMI Evidence Documents," and the recipient's mail provider has to meet Apple's requirements as well. Apple doesn't say whether a CMC counts.
- [ ] Microsoft: Microsoft hasn't documented BIMI logo display in Outlook.com or Microsoft 365.
On eligibility:
- A VMC is issued against a registered trademark. See VMC certificate.
- A CMC is for a logo that has been used on your own website, on the same domain, for at least 12 months, checked through the Internet Archive. The official requirements list additional CMC routes.
- Either way, a certificate is valid for at most 398 days. Put the renewal on someone's calendar.
Choosing between them: Is VMC still worth it now that CMC exists?
5. The BIMI record
The BIMI record is a DNS TXT record at default._bimi.<your-domain>. A BIMI record example for example.com:
default._bimi.example.com. TXT "v=BIMI1; l=https://example.com/bimi/logo.svg; a=https://example.com/bimi/vmc.pem"
- [ ]
v=BIMI1first, exactly as written. The value "MUST match precisely" and receivers "MUST NOT attempt to fix syntactical or capitalization errors." Some published examples use lowercasev=bimi1. Don't copy them. - [ ]
l=holds the HTTPS URL of your SVG. The tag is required. - [ ]
a=holds the HTTPS URL of your PEM. The BIMI specification makes it optional, but Gmail requires a certificate, so in practice you need it. You can leavel=empty when the PEM carries the logo. Filling in both also works with Gmail. - [ ] Only one BIMI record at that name. Two records, or none, means no BIMI.
- [ ] Subdomains are covered. Receivers look for a record on the From domain first, then fall back to the organizational domain's record. One record at the organizational domain covers your subdomains, and a subdomain record overrides it. It honors subdomain records but prefers "BIMI and DMARC to be set up at the organizational domain level."
- [ ] Opt-outs are explicit. To stop a subdomain inheriting the logo, publish the declination record
v=BIMI1; l=; a=;on it.
Two optional tags exist for advanced setups: lps= (local-part selectors) and avp= (brand logo or personal avatar preference, default brand). Most domains don't need either.
6. Sending profile and expectations
- [ ] Yahoo: bulk mail only ("we don't display brand logos for personal emails"), plus "sufficient reputation and engagement." Yahoo doesn't publish a volume threshold.
- [ ] Any receiver may require a sufficiently strong reputation or apply its own heuristics.
- [ ] Wait. It can take up to 48 hours for your logo to show.
If everything is ticked and there's still no logo, use Why your BIMI logo is not showing. For the rollout in project order, with who does what, see How to move from DMARC enforcement to BIMI.
Common mistakes
- Apex at
p=rejectwithsp=noneleft in, or a subdomain_dmarcrecord still atp=none. - Lowercase
v=bimi1, orapv=instead ofavp=. Both appear in examples online. - Two TXT records at
default._bimi, for example an old test record nobody removed. - Logo on HTTP, behind a CDN bot filter, or served as
text/plainorapplication/octet-stream. - SVG exported with
baseProfile="tiny", or withx/yon the root element. - A different logo at
l=from the one embedded in the certificate. - An expired certificate.
- A new vendor sending as the BIMI domain before it's aligned (How to add a third-party sender without breaking DMARC).
Free DMARC account
Your logo needs DMARC enforcement first
Monitor DMARC on the way to quarantine or reject. Once you're there, our team can help with your VMC or CMC and your BIMI record.
- DMARC results per sender before you enforce
- A clear view of what still fails alignment
- Help with your VMC or CMC and BIMI record
FAQ
Do we need a VMC for Yahoo?
No. It doesn't require one, but uses one if your record includes it.
Can one BIMI record cover all our subdomains?
Yes. Receivers fall back to the organizational domain's record, and a subdomain record overrides it. DMARC still has to be at enforcement for those subdomains.
Is a= required?
The BIMI specification itself doesn't require a=. But Gmail requires a VMC or CMC, and a= is where the record points to it.
Is ticking every box a guarantee?
No. Providers decide display themselves, and some also weigh reputation and volume.