BIMI (Brand Indicators for Message Identification) puts your logo where a recipient's eye lands first: the round sender avatar next to your name in their inbox. Instead of a grey circle with an initial, supported mailbox providers render your brand mark on every message. It is a small, persistent signal that the mail is really from you. The payoff is recognition and trust, which tends to lift opens, and a visible cue that your domain is authenticated and hard to spoof.

BIMI rides on top of a fully authenticated, DMARC-enforced domain. Set up DKIM, SPF, and DMARC first. The logo only shows once your mail passes authentication and your DMARC policy is at enforcement.

What BIMI requires

Four things have to be true before a mailbox provider will display your logo. Sendara generates the record and hosts the logo for you, but the DMARC and trademark pieces are yours to satisfy:

A square SVG logo. BIMI requires the SVG Tiny PS profile, a restricted, secure subset of SVG (no scripts, no external references, a 1:1 square aspect ratio, and a solid background). It must be served over HTTPS. Sendara validates the profile on upload and rejects anything that is not compliant.
A BIMI DNS record. A TXT record at default._bimi.<domain> pointing at the logo URL:
v=BIMI1; l=<logo-url>;
A strict DMARC policy. Your DMARC policy must be p=quarantine or p=reject. A relaxed p=none is not enough. This is the security backbone: providers only trust the logo when spoofed mail on your domain is already being quarantined or rejected.
A VMC, for some providers. Gmail and Apple Mail additionally require a paid Verified Mark Certificate (VMC) issued against a registered trademark of your logo, plus a a=<vmc-url> tag added to the record. Yahoo and Fastmail display the logo without a VMC, so you can light up those inboxes immediately and add a VMC later for Gmail and Apple.

Do not publish a BIMI record while your DMARC policy is still p=none. A mailbox provider ignores the logo until the policy is p=quarantine or p=reject. Read the dmarc.at_enforcement flag in the API response to see whether your policy has reached one of those two values.

Get the current state

Read the BIMI state for a verified domain. The response returns the hosted (or supplied) logo_url, the exact TXT record to publish (or null if no logo is set yet), whether your DMARC is already at_enforcement with a recommended policy to copy, whether the record is live (bimi_published), and a vmc_note on which providers need a certificate.

get-bimi.sh

curl https://api.sendara.dev/v1/domains/mail.acme.com/bimi \
  -H "Authorization: Bearer sk_live_xxx"

{
  "logo_url": "https://api.sendara.dev/v1/bimi-logos/asset_7f3a9c21",
  "record": {
    "type": "TXT",
    "name": "default._bimi.mail.acme.com",
    "value": "v=BIMI1; l=https://api.sendara.dev/v1/bimi-logos/asset_7f3a9c21;"
  },
  "dmarc": {
    "at_enforcement": false,
    "recommended": "v=DMARC1; p=quarantine; rua=mailto:[email protected]"
  },
  "bimi_published": false,
  "vmc_note": "Gmail & Apple Mail require a paid VMC certificate tied to a registered trademark."
}

Set your logo

There are two ways to point BIMI at a logo. Either way you get the same response back, including the generated TXT record to publish.

Point at your own URL

If you already host a compliant SVG Tiny PS logo over HTTPS, send its URL. Sendara validates it and builds the record around it. Requires a key with the admin scope.

logo_urlstringOptional

Public HTTPS URL of a square SVG Tiny PS logo. Pass your own CDN URL, or omit it and upload the file so Sendara hosts it for you.

set-bimi.sh

curl -X PUT \
  https://api.sendara.dev/v1/domains/mail.acme.com/bimi \
  -H "Authorization: Bearer sk_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{ "logo_url": "https://cdn.acme.com/brand/logo-tiny-ps.svg" }'

Upload the SVG and let Sendara host it

Do not have anywhere to host the file? Send the SVG as multipart/form-data with a filepart (SVG, max 1 MiB). Sendara validates the SVG Tiny PS profile, hosts it on a stable HTTPS URL, and returns the record pointing at it.

upload-logo.sh

curl https://api.sendara.dev/v1/domains/mail.acme.com/bimi/logo \
  -H "Authorization: Bearer sk_live_xxx" \
  -F "[email protected]"

Hosting with Sendara is the simplest path. You skip running your own HTTPS endpoint, and the URL never changes, so the BIMI record stays valid even if you redesign your CDN.

Publish the record

Take the record from the response and publish it as a TXT record at your DNS provider, exactly as returned:

Type	Name / Host	Value
TXT	default._bimi.mail.acme.com	v=BIMI1; l=https://api.sendara.dev/v1/bimi-logos/asset_7f3a9c21;

Once DNS propagates and your next message authenticates against an enforced DMARC policy, supported inboxes start rendering your logo. Yahoo and Fastmail light up first. Gmail and Apple follow once you have added a VMC and its a= tag to the record.

Set it in the dashboard

Prefer not to touch the API? In the Sendara dashboard, open a verified domain and go to its Brand logo (BIMI) section. Upload your SVG (or paste a URL), and Sendara hosts the logo, generates the TXT record, and shows whether your DMARC policy is strict enough yet. Copy the record into your DNS provider and you are done. Use one logo per verified domain.

BIMI checklist

Authenticate the domain; DKIM, SPF, and DMARC all passing and aligned.
Move DMARC to p=quarantine or p=reject and confirm dmarc.at_enforcement is true.
Prepare a square SVG Tiny PS logo, then upload it (or point at your own HTTPS URL).
Publish the generated TXT record at default._bimi.<domain>.
Gmail and Apple Mail additionally require a VMC, which you buy from a certificate authority against your registered trademark. Sendara does not supply one. Add its a= tag to the record.