How BIMI works

BIMI is maintained by the BIMI Group and documented as an Internet-Draft at the IETF. It builds on existing authentication rather than adding a new check. The flow looks like this:

  1. A message arrives claiming to be from example.com.
  2. The receiver evaluates DMARC. The message must pass, and the domain’s policy must be quarantine or reject.
  3. The receiver looks up a BIMI record at default._bimi.example.com.
  4. If the record is valid, the receiver fetches the logo (and certificate, if present) and may display it next to the message.

The BIMI record is a TXT record with two main tags:

default._bimi.example.com.  TXT  "v=BIMI1; l=https://example.com/bimi/logo.svg; a=https://example.com/bimi/vmc.pem"

l= points to the logo file and a= points to the certificate (the “authority evidence”). Both must be served over HTTPS. Senders can also publish records under other selectors and choose one per message with a BIMI-Selector header, which is useful when sub-brands share a domain.

Logo requirements

BIMI logos must use the SVG Tiny Portable/Secure (SVG Tiny PS) profile, a restricted form of SVG with no scripts, animation, or external references. According to Google’s BIMI setup guide, the logo should be square, centered, use a solid background, and be at least 96 by 96 pixels, with a recommended file size of 32 KB or less. Most design tools don’t export SVG Tiny PS directly, so the file usually needs conversion and validation.

Mark certificates: VMC and CMC

A certificate ties the logo to your organization, issued by an authorized certificate authority after verifying your identity.

  • Verified Mark Certificate (VMC): requires the logo to be a registered trademark. In Gmail, senders with a VMC also get a verified checkmark.
  • Common Mark Certificate (CMC): for logos that aren’t trademarked. Gmail accepts it for logo display, without the checkmark.

Gmail displays BIMI logos only with one of these certificates. Requirements differ at other providers, and the BIMI Group site lists supporting mailbox providers and certificate issuers. Certificates cost money and must be renewed, and trademark registration can take months, so plan ahead if you want a VMC.

Why BIMI matters

BIMI doesn’t change spam filtering. Its value comes from two places.

Recognition. A familiar logo in the inbox helps recipients identify your mail at a glance and makes impersonation of your brand easier to spot.

The prerequisites. Getting to BIMI forces a domain to have SPF and DKIM aligned for every legitimate sender and DMARC at enforcement. Google’s guide also requires the policy to apply to all mail (pct=100). That work protects your domain from spoofing and strengthens the authentication signals mailbox providers already use, whether or not the logo ends up displaying everywhere.

How to get BIMI working

  1. Reach DMARC enforcement. Move from p=none to quarantine or reject with pct=100, after reports confirm legitimate mail passes.
  2. Check subdomain policy. If you set sp=none in your DMARC record, subdomains sending under BIMI may not qualify.
  3. Prepare the logo in SVG Tiny PS and validate it.
  4. Obtain a VMC or CMC if you want the logo in Gmail.
  5. Publish the BIMI record and host the logo and certificate at stable HTTPS URLs.
  6. Test by sending to accounts at each target provider. Display can take time, and some providers also weigh sending volume and reputation.

Where RocketVerifier helps

Before investing in BIMI, use the free email deliverability checker to confirm your SPF, DKIM, and DMARC records are in place and enforced. A logo can’t fix a weak reputation, so pair authentication with bulk email verification to keep bounce rates low on every send.