Skip to main content
BIMI (Brand Indicators for Message Identification) is a DNS record naming the logo you want shown beside your messages. Mailbox providers that support it draw that logo in the recipient’s inbox. A message in Gmail showing the sender's logo as a circular avatar beside the sender name and address The record itself is one TXT entry and takes a minute to publish. Everything it points at takes longer, so work through the three requirements below before you add it.

What BIMI requires

Raise your DMARC policy

A domain added to mailkube gets a DMARC record with p=none, which asks receivers for reports and changes nothing about delivery, and BIMI ignores every domain sitting at that policy. The specification requires either quarantine at an effective 100%, or reject at any percentage. Enforcement is read at the organizational domain, not only at the subdomain you send from. A sending domain of mail.example.com needs _dmarc.example.com at enforcement as well, and the parent record should carry a matching sp= so the policy reaches subdomains.
Editing the policy does not un-verify the domain, because mailkube checks the record for its own rua and ruf addresses and reads nothing else. Keep both of those addresses exactly as the dashboard shows them, and change only the p= and sp= values.
p=reject instructs receivers to drop mail that fails authentication. Read your DMARC reports until nothing legitimate is failing, then tighten. Moving straight to reject on a domain with unknown senders rejects real mail.
The file is an SVG in the Portable/Secure profile, a restricted subset of SVG Tiny 1.2. A general purpose SVG exported from a design tool will not pass. Transparency is the rule most often missed, because each provider places the logo on a background of its own choosing and a transparent file disappears against roughly half of them. Host the file anywhere that serves it over HTTPS with the correct content type, then run it through the BIMI Group validator, which reports the rules it breaks. The a= tag points at a certificate proving the logo belongs to you. Leaving it empty is called self-assertion, and support for it varies by provider. Gmail reads the certificate rather than the SVG URL, so a record with an empty a= shows nothing there. DigiCert, GlobalSign, and SSL.com issue both certificate types, and each runs its own verification before it signs, so begin that process well ahead of any launch built around the logo.

Publish the record

1

Build the record value

A full record names the logo and the certificate:
Both URLs must be HTTPS. For a self-asserted record, leave the a= value empty rather than removing the tag.
2

Add it at your DNS provider

Publish a TXT record at default._bimi.example.com. Most DNS panels append the zone to whatever you type, so the Name or Host field takes default._bimi on its own. Pasting the full name into a panel that appends the zone publishes default._bimi.example.com.example.com.
3

Publish it at the organizational domain

default is the selector every message uses unless a BIMI-Selector header names another one. Publishing the default record at your organizational domain lets subdomains inherit it, so one record covers every sending subdomain.

Confirm it

Query the record once DNS has propagated:
A valid record is necessary and not sufficient. Providers weigh sending reputation before drawing a logo, and a domain with high complaint or bounce rates keeps a blank avatar with every record in place. Each provider also refreshes on its own schedule, so allow days rather than minutes.
  • Domains covers the SPF, DKIM, and DMARC records a sending domain needs first.
  • Plans & limits lists how many domains each plan carries.