Guides BIMI

What is BIMI?

BIMI links a logo to mail from your domain. You arrange the sender checks, logo and any required proof that you may use the logo. The receiving mail provider decides whether to show it.

Your logo can appear beside mail from example.com. You provide a suitable logo file and publish its location in your domain settings. BIMI provides that link. The receiving mail provider must support BIMI and decides whether to display the logo.

Check BIMI on your own domain

You send a message as info@example.com. You have published where your logo is available with example.com. The receiving mail provider first checks that the message meets its sender requirements. It can then look up the logo reference, check the file and display the logo beside the message.

The receiving provider decides whether to show the logo, even when your information is correct. Start by checking the requirements of the mail provider where you want the logo to appear.

First make sure your own mail passes its checks

A logo should not simply appear beside someone impersonating your sender address. The receiving provider therefore first wants evidence for the domain behind that address. This can come from permission for the sending server or from a valid digital signature. Those checks are called SPF and DKIM. Linking their results to the visible sender domain is called DMARC. The relationship between those domains is called alignment.

For a logo, the BIMI specification also requires you to ask for suspicious handling or rejection of mail that fails that domain check. The policy values for those requests are p=quarantine and p=reject. Monitoring alone, p=none, is not enough.

Do not tighten that policy just to obtain a logo. First inventory legitimate sending services, check real messages and review DMARC reports. Fix failures before requesting stricter handling, so your own mail is not caught by it. See the DMARC guide for details of this check and a safe rollout.

Publishing a logo and DNS record

The public domain settings are called DNS. The receiver looks for the logo reference at a fixed name with your domain, usually default._bimi.example.com. The first part, default, chooses which logo record to use. This choice name is called a selector.

Ask your designer for a logo using the BIMI SVG Tiny PS profile. An ordinary SVG export or a PNG renamed to .svg is not enough. The draft names SVG and SVGZ, but receivers may impose further profile and file requirements. Use the SVG tools under Sources and check the requirements of the provider you want to support.

Have your web administrator serve the logo publicly over a secure web connection (HTTPS) and check the retrieved contents too. Then have your DNS administrator publish exactly one BIMI record for the chosen selector. A complete record for the default selector looks like this:

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

Replace the domain and URL with your own values. v=BIMI1 comes first. l= points to the logo. Some DNS panels append the domain automatically: enter only default._bimi as the name there. Some providers will not accept this record without mark evidence.

If the chosen provider requires an evidence document, add its real HTTPS URL in a= in the same record. Example: "v=BIMI1; l=https://example.com/bimi/logo.svg; a=https://example.com/bimi/evidence.pem;". Have the issuer and provider confirm the required contents and chain. Do not publish a fictitious evidence file.

VMC, CMC and choosing a provider

A Verified Mark Certificate (VMC) is one form of evidence for using a logo, typically for a registered trademark or government mark. A Common Mark Certificate (CMC) provides another route, for example for marks with established prior use. These are mark certificates, not the TLS server certificates that provide HTTPS for your website.

The a= tag is optional in the BIMI protocol. A receiving provider may nevertheless require evidence and decides which documents it accepts. Gmail, for example, requires a VMC or CMC. Other providers may have different requirements. Check the current provider and issuer requirements before applying for a certificate. The links under Sources can help.

Later: sending from a subdomain

If you send from news.example.com rather than example.com, check two levels. In this example, example.com is the Organizational Domain: the parent under which news.example.com falls. The BIMI profile requires enforcing DMARC policy at both the sender domain and that Organizational Domain. The BIMI specification is still in development and is called an Internet-Draft.

After those checks, you could use a record such as: _dmarc.example.com TXT "v=DMARC1; p=quarantine; sp=quarantine". A separate p=none at news.example.com still blocks BIMI there. Conversely, p=reject at the subdomain alone is not enough if the organizational domain has p=none. A published sp=none also blocks eligibility under the BIMI profile.

The BIMI draft still uses older DMARC rules than DNS Radar's general DMARC check. For example, an old pct=50 alongside p=quarantine blocks the BIMI requirement. The newer DMARC RFC no longer supports pct: do not add that tag back for BIMI, but have obsolete rollout settings removed carefully once every mail stream has been checked. This helps explain why DMARC and BIMI results can differ.

Correct record, but no logo: what next?

If the logo does not appear, check these in order:

  • An actual received message: does DMARC pass, or does the receiver accept another authentication path, and which From domain and selector does it use?
  • The published BIMI record and policies at both the sender and organizational domains.
  • The actual logo file: reachable over HTTPS and compliant with the required SVG profile?
  • Any mark evidence: valid, matching the logo and accepted by this provider?
  • Then the receiver's own display and reputation policies.

DNS Radar assesses the published record syntax, address values and DNS-visible DMARC prerequisites. It does not retrieve the logo or evidence document, or measure a DMARC pass for a message it has not received. A lookup failure remains unknown, not proof that the record is absent. The scan checks the default selector and cannot list every possible selector.

BIMI does not prevent lookalike domains or copied logos. SPF, DKIM and DMARC check the sender domain. Mail that passes these checks may still contain harmful content. The receiver assesses it further and decides on delivery and logo display.

A selector is the name used to choose a BIMI record. Without an explicit choice in the message, it is default. A sending service can choose another selector in the BIMI-Selector header, such as brand. The lookup then uses brand._bimi.<sender-domain>.

If no record for that selector is found at a subdomain, the receiver may look for the same selector at the organizational domain. A missing default record therefore does not automatically mean that no message can use BIMI.

To decline logo use for a selector, "v=BIMI1; l=; a=;" is an explicit choice not to participate. This differs from deleting the record, which can allow a logo to be inherited from the organizational domain. An empty record at a subdomain can prevent that inheritance.

Primary sources

Frequently asked questions

Do I always need a VMC?

A provider may require evidence that you may use the logo. A VMC is a mark certificate that can serve this purpose. A CMC is another kind of mark certificate. Not every provider has the same requirement. Gmail accepts VMC or CMC. Check the receiver's current requirements before spending money. The provider still decides whether to display the logo.

Can I use an ordinary SVG?

Not automatically. The logo must meet a specific version of the SVG file format, usually the BIMI SVG Tiny PS profile, plus your provider's requirements. An .svg address does not prove its contents are correct. Have the designer check the file with the BIMI tools.

Why is BIMI blocked when DMARC looks good in the report?

BIMI additionally requires enforcing policy at two domain levels, and the draft still uses the older DMARC profile. A separate p=none, sp=none or an old partial quarantine rollout may therefore block it. Read the specific BIMI reason. Do not blindly enable a stricter policy.

Does BIMI improve deliverability?

A logo does not guarantee inbox placement. Good authentication is useful, but the receiver also considers reputation, contents and local policy. Use BIMI for recognition, not as a fix for delivery problems.

Check BIMI on your own domain →