trustyourinbox

BIMI in plain English

BIMI (Brand Indicators for Message Identification) lets receivers display your logo next to your messages, instead of a generic initial avatar. The setup has three required pieces, two of which are work and one of which can cost real money. Whether it's worth doing depends on whether your customers will see the difference where they actually read mail.

What BIMI actually does

Open your inbox. Most senders show up with either a generic colored circle and a letter (the first letter of the sender's name), or a tiny photo if you have one in your contacts. BIMI replaces that initial avatar with a domain-controlled logo, the actual brand mark a recipient already associates with you.

That's the whole feature. It's not a security mechanism in the way DMARC is; it's a presentation mechanism that piggybacks on DMARC's authentication. BIMI's whole pitch is "the recipient can see at a glance that this message is from a real, authenticated sender." Visual trust signal at the point of the inbox.

Receivers that honor BIMI include Gmail, Apple Mail (iOS, iPadOS, macOS), Yahoo Mail, AOL, Fastmail, and La Poste, each with the certificate caveats below. Outlook and Microsoft 365 do not display BIMI logos today.

The three required pieces

Piece 1: DMARC at p=quarantine or p=reject (not in test mode)

BIMI does not display unless your DMARC policy is at p=quarantine or stricter, applied to 100% of mail. p=none is explicitly disqualifying: receivers won't show the logo regardless of the rest of your setup.

This is the gate that filters out most BIMI deployments before they start. If you haven't already progressed past p=none, do that first. BIMI is a downstream reward for the harder authentication work.

Piece 2: a properly-formatted SVG logo (Tiny SVG profile)

Your logo must be saved as an SVG that conforms to the SVG Tiny Portable/Secure profile ("SVG Tiny PS", a profile of SVG Tiny 1.2). It's a constrained subset of SVG: no scripts, no animations, no external references, no foreign content. Square aspect ratio, with the mark centered.

Most enterprise logos need an explicit re-export to comply. Designers comfortable with SVG can usually produce a compliant version in 10-15 minutes. There are also free online "BIMI SVG validators" that will tell you which parts of your existing SVG are out of profile.

Piece 3: hosting + DNS

Host the SVG file at a stable HTTPS URL (anywhere: your CDN, S3, your marketing site). Then publish a DMARC-style TXT record at default._bimi.<your-domain>:

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

The l= tag is the SVG location. The a= tag is optional. It points to the Verified Mark Certificate (see next section). If you skip a= entirely, BIMI still works in some inboxes; in others (notably Gmail), it doesn't.

The Verified Mark Certificate question

A VMC is a certificate issued by a Mark Verifying Authority (DigiCert and Entrust are the established issuers). It attests "this organization owns this trademark and may display this logo." The receiver checks the cert chain before showing your logo.

The catch: getting one requires a registered trademark on the logo. Pending applications don't count; common-law marks don't count. The certificate is a yearly fee set by the issuer, and it covers the registered logo only: change the mark and you need a reissue.

Receivers handle certificates differently:

  • Gmail: a certificate is required. A VMC shows the logo and the blue verified check mark; since 2024 a CMC (below) shows the logo without the check mark. With neither, no logo.
  • Apple Mail: a VMC is required (support arrived with iOS 16 and macOS Ventura in 2022).
  • Yahoo / AOL: display a self-asserted SVG without a certificate, as long as DMARC is enforced and the sender's reputation and volume are high enough.

The CMC option (Common Mark Certificate) is the alternative for senders without a registered trademark: the same issuers verify that the logo has been in documented use for at least a year instead of checking a trademark register. Gmail accepts one for the logo; Apple's published support names only the VMC, so receiver coverage is narrower than with a VMC.

What it's worth

An assessment, not a sales pitch:

  • Brand recognition lift: most visible in mobile inboxes, where the logo occupies comparatively more of the rendered row. Large B2C senders report modest lifts in opens; treat a vendor's case study as a vendor's case study.
  • Phishing signal: the absence of your logo on a forged message is a visual cue, but only for recipients who already know your real logo and are using a BIMI-aware client. Don't deploy BIMI for security; deploy DMARC p=reject for security.
  • Operational cost: if you don't have the trademark already, registering it is a multi-month process plus a filing fee that varies by jurisdiction. The ongoing VMC fee is the easier part.
  • Audience matters: if your customer base is mostly Gmail-on-mobile, the VMC investment shows its benefit. If they're mostly Outlook-on-desktop, the benefit is invisible (Outlook doesn't render BIMI logos today).

The decision rule we'd suggest:

  • You already have a registered trademark and you're at p=reject: do it. The marginal cost is the VMC fee and a designer-hour for the SVG. Visual brand at the inbox is valuable for recognized brands.
  • You're not yet at p=reject: wait. Get authentication right first; BIMI without enforcement does nothing.
  • You don't have a registered trademark: try the SVG-only path (no a= tag) for Yahoo and AOL, or a CMC for Gmail. It costs designer time plus the CMC fee, and you can move to a VMC later if you trademark the mark.
  • You're a small B2B SaaS with a niche audience: probably not worth it today. The receivers your customers use heavily likely aren't the strong-BIMI ones, and the ROI on the VMC fee is hard to defend.

What we do for you

The checking half exists today. Our free BIMI validator reads any domain's record, confirms DMARC is enforced, validates the SVG against the Tiny PS profile, and inspects the VMC. On a monitored domain, the BIMI tab runs the same checks every six hours and tells you when the DMARC prerequisite is met.

The publishing half is yours: the DNS record, hosting the SVG on your own site, and the certificate purchase and renewal stay with you (or your designer, your registrar, and the issuer). We check them; we don't host them.

Common deployment mistakes

Publishing BIMI before reaching p=quarantine

The BIMI DNS record is allowed; it just won't display anywhere. Recipients see no change. We see this regularly. The fix is to either complete the DMARC progression first or to remove the BIMI record until you do.

Using a non-Tiny SVG

Your standard logo SVG probably has metadata, scripts, or external font references that make it non-compliant with Tiny PS. Receivers reject non-compliant SVGs silently: no logo, no error, no notification. Validate before publishing.

Hosting the SVG on a flaky URL

Receivers fetch the SVG on their schedule, with their own caching. If your URL is occasionally 404 or 500, BIMI display becomes flaky. Static hosting (CDN, S3, your marketing site) is far better than a dynamic endpoint.

Forgetting to renew the VMC

Annual cert. Lapses silently. Set a calendar reminder a month out.

Fix DNS issues with one click. See the exact change before it goes live.

Click the fix. We email you the exact record, wait five minutes, write it to Cloudflare or AWS Route 53, and read it back from public DNS. On any other DNS host, you get the record and a link to the right page. Included on every plan.

Was this page helpful?

Keep reading.

Start with one domain. See it with your own data.

Free for one domain, no card. Add one DNS record and the first reports usually arrive within a day.

  1. Monitoring
  2. Quarantine
  3. Reject