With BIMI 1), a logo file should be displayed in the receiver inbox.
Even if a trademark certificate is not requested by BIMI, most email providers require one, making it difficult for small companies to implement it.
When all requirements pass, the email provider will look up a TXT record where the content starts with v=BIMI1. In this record, it will find:
With a TTL equivalent of 1 hour, the value of the TXT record could be:
v=BIMI1;l=https://example.com/brand-logo.svg
A Verified Mark Certificate (VMC) is a proof that the logo has been validated.
You can add a verified mark certificate if you have requested one with the a attribute
v=BIMI1;l=l=https://example.com/brand-logo.svg;a=l=https://example.com/vmc-certificate.pem
The full record example value if the BIMI group reference is:
default._bimi.example.com in txt
"v=BIMI1; l=https://www.example.com/path/to/logo/example.svg; a=https://www.example.com/path/to/vmc/VMC.pem;"
A BIMI record has three attributes:
The BIMI record is retrieved from the domain identified within the DKIM domain (ied=) value.
A single global BIMI Record at the apex domain (organization domain) will cascade down to other subdomains
BIMI supports selectors allowing the same domain to publish multiple but separate records.
It could be used to segment different logos.
The base selector is default.
The DNS name should look similar to this default._bimi.example.com
BIMI requires:
The logo URL (ie referenced by the l=):
The BIMI standard does not require your logo to be a registered trademark to get a VMC 3)
But most providers do.
See Get your Verified Mark Certificate (VMC)
The SVG file requirements are:
Google guidelines for compatibility
The list of provider that supports BIMI can be found at this address: https://bimigroup.org/bimi-infographic/