schedule 15-min read

What Is a BIMI Record? Tags, Location and Examples

DMARC AI editorial team · Last updated

A BIMI record is a DNS TXT record at default._bimi that points to your logo and mark certificate. Every tag, real examples, errors and dig checks.

01

What is a BIMI record?

A BIMI record is a DNS TXT record, published at default._bimi.<domain>, that tells mailbox providers where to find your brand logo (l=) and the mark certificate that proves you may use it (a=). Providers read the BIMI record only for mail that passes DMARC at a domain with a quarantine or reject policy.

BIMI stands for Brand Indicators for Message Identification. This article is about the record itself: where it lives, what each tag means, how receivers find and check it, and the mistakes that stop a logo appearing. For the concept, read what BIMI is and how it relates to DMARC. For the policy prerequisites, read BIMI requirements: why DMARC enforcement comes first. The BIMI guide covers the whole topic.

02

Key takeaways

  • The BIMI record is a TXT record at default._bimi.example.com. The label default is the selector, and _bimi is fixed.
  • v=BIMI1 must come first. l= holds the HTTPS URL of an SVG Tiny PS logo, and a= holds the HTTPS URL of a PEM evidence document (a VMC or CMC).
  • Gmail needs a=. Records with only l= (self-asserted) work at a few providers, such as Yahoo, but not at Gmail.
  • v=BIMI1; l=; a=; is an explicit opt-out, which is different from publishing nothing.
  • Receivers check DMARC first. A perfect BIMI record does nothing on a domain at p=none or with sp=none.
03

Where is a BIMI record published?

A BIMI record lives at <selector>._bimi.<domain>. With no selector specified, the selector is default, so the usual host name is default._bimi.example.com. Receivers look up the record at the exact From domain first, then fall back to the organizational domain if nothing is published there.

The current specification is the IETF Internet-Draft draft-brand-indicators-for-message-identification. At the time of writing it is revision 15, an individual draft rather than an RFC. Section 4.4 states that "The selector 'default' is the default Assertion Record."

In a zone file, the record looks like this:

default._bimi.example.com.  3600  IN  TXT  "v=BIMI1; l=https://brand.example.com/bimi/logo.svg; a=https://brand.example.com/bimi/vmc.pem"

In a DNS provider's web panel, you usually enter only default._bimi as the host, because the panel appends the zone name. Google's detailed steps for adding a BIMI TXT record use default._bimi. followed by the domain, and suggest a TTL of one hour (3600 seconds).

The lookup order matters for subdomains. Mail from news.example.com triggers a query for default._bimi.news.example.com. If that returns nothing, the receiver queries default._bimi.example.com. So one record at the organizational domain can cover every subdomain that uses the same logo. If discovery returns more than one BIMI record for a name, the draft says processing stops, so never publish two.

04

What tags does a BIMI record contain?

A BIMI record is a list of tag=value pairs separated by semicolons. Revision 15 of the draft defines five tags: v= (required, first), l= (logo location), a= (evidence location), and two newer optional tags, lps= and avp=. The draft says unknown tags must be ignored.

Tag Required? Value What it does
v= Yes, and must be first BIMI1 Identifies the TXT record as a BIMI record. Anything else is discarded
l= Yes (may be empty) One HTTPS URL Location of the logo, in SVG (or compressed SVGZ) using the SVG Tiny PS profile
a= Optional in the draft, needed for Gmail One HTTPS URL Location of the evidence document: a PEM file holding a Verified Mark Certificate (VMC) or Common Mark Certificate (CMC)
lps= Optional Comma-separated local-part prefixes Lets a receiver derive a selector from the sender's local-part (the part before the at sign)
avp= Optional, default brand brand or personal Avatar preference: whether to show the brand logo or a sender's personal avatar when both exist

A few details from the draft are worth knowing:

  • v=BIMI1 uses the digit one. Google's help warns that the characters 1, I and l look alike, and a record starting v=BIMl is discarded.
  • Only HTTPS is allowed. Section 4.3 says of l=: "The only supported transport is HTTPS." The same applies to a=, and the server's TLS certificate must chain to a root the receiver trusts.
  • Tag order is free after v=. The other tags can appear in any order.

We have not found mailbox provider documentation confirming support for lps= or avp=. They are in the draft, so they are valid, but treat them as optional extras and test before relying on them. Most deployments publish only v=, l= and a=.

05

What are the logo requirements for the l= tag?

The l= URL must point to an SVG file in the SVG Tiny Portable/Secure (SVG Tiny PS) profile, served over HTTPS. That profile is a restricted SVG: baseProfile="tiny-ps", version="1.2", a <title> element, and no scripts, animation or external references. Most design-tool exports need editing before they qualify.

The BIMI Group guide to creating SVG logo files and Google's Set up BIMI page together give this checklist:

  • baseProfile="tiny-ps" and version="1.2" on the root <svg> element.
  • A <title> element that reflects the company name.
  • No x= or y= attributes on the root element (some design tools add them by default).
  • No scripts, animation, interactive elements or external links.
  • A square image, centred, with a solid background rather than transparency.
  • At least 96 x 96 pixels and 32 KB or smaller (Google's figures).

A minimal skeleton looks like this:

<svg xmlns="http://www.w3.org/2000/svg" version="1.2" baseProfile="tiny-ps" viewBox="0 0 512 512">
  <title>Example Ltd</title>
  <rect width="512" height="512" fill="#ffffff"/>
  <!-- logo paths here -->
</svg>

06

What does the a= tag point to?

The a= tag points to a BIMI Evidence Document. In practice, that is a PEM file containing a mark certificate issued by a certification authority. It proves the domain owner may use the logo. A VMC covers registered trademarks and government marks. A CMC covers marks without a registration, such as prior use marks.

Google states that "you must get a VMC (recommended) or a CMC," and that Gmail shows a checkmark only "next to senders verified with a VMC." The PEM file must hold the full chain: the entity certificate, then any intermediate certificates, then the root.

The certificate also embeds the logo. That is why Google's own example leaves l= empty:

default._bimi.example.com.  TXT  "v=BIMI1;l=;a=https://images.example.com/brand/certificate.pem"

Gmail accepts that form. The BIMI Group implementation guide template fills both tags, which also serves receivers that read l=. When you fill both, the SVG at l= should be the same logo that is in the certificate.

A record with l= and no a= is self-asserted. The BIMI Group page on certificate types says only "a few mailbox providers" support self-asserted logos, naming Yahoo, Fastmail and La Poste. Google describes the SVG-only option as not supported in Gmail. For the business choice between a VMC and a CMC, see how BIMI can improve brand trust in the inbox.

07

How do you use a selector other than default?

You publish a second record under another selector, such as marketing._bimi.example.com, and add a BIMI-Selector header to the messages that should use it. The receiver then looks up that selector instead of default. This lets one domain show different logos for different mail streams, such as a sub-brand.

The header looks like this:

BIMI-Selector: v=BIMI1; s=marketing;

Two rules from the draft matter:

  • Sign the header. The draft says the BIMI-Selector header "SHOULD be included in the DMARC-aligned DKIM signature." If it is not signed, receivers should ignore it and fall back to default.
  • Unknown selectors fall back. A custom selector that does not exist at the From domain falls back to the same selector at the organizational domain, not to default.

Most organisations never need a custom selector. Confirm that your sending platform can add and sign custom headers before you plan one. See how to set up DKIM for signing on the main platforms.

08

How do you decline BIMI for a domain?

Publish a record with both l= and a= empty: v=BIMI1; l=; a=;. The draft calls this "an explicit refusal to participate in BIMI." Receivers record the result as bimi=declined. That is different from publishing nothing, which gives bimi=none and lets the receiver fall back to the organizational domain record.

default._bimi.legacy.example.com.  TXT  "v=BIMI1; l=; a=;"

A declination record is useful when the organizational domain has a logo but one subdomain should not show it, for example a subdomain used by a third party or a brand you are retiring.

09

How do receivers check a BIMI record?

A receiver checks DMARC first, then discovers and validates the BIMI record, then fetches and validates the logo and evidence. Only when every step passes does it add headers that let the mail client show the logo. A failure anywhere means no logo, never a bounce.

The sequence in Section 7 of the draft is roughly:

  1. DMARC result. The message must pass DMARC. The policy for the From domain and the organizational domain must be quarantine or reject. If p=none, or a published sp=none, applies, BIMI processing "MUST NOT be performed."
  2. Selector. Use the selector from a signed BIMI-Selector header, otherwise default.
  3. Discovery. Query <selector>._bimi.<From domain>, then the organizational domain if nothing is found. Discard TXT records not starting with v=BIMI1.
  4. Retrieval and validation. Fetch the l= and a= files over HTTPS, check the SVG profile, and validate the evidence document.
  5. Headers. Remove any incoming BIMI headers, then add BIMI-Location and BIMI-Indicator (the logo, base64-encoded) and an Authentication-Results entry.

The draft defines these bimi= results: pass, none, fail, temperror, declined and skipped. An illustrative header from a receiver looks like this:

Authentication-Results: mx.example.net; bimi=pass header.d=example.com header.selector=default policy.authority=pass

Two provider notes. Yahoo's BIMI page adds conditions beyond the record: bulk mail only, with "sufficient reputation and engagement", and a preference for BIMI and DMARC at the organizational domain. Apple's BIMI support page says "BIMI compliance is managed by the mail provider on the server," so Apple Mail shows a logo only when the recipient's provider has done these checks and added the headers.

What about the old DMARC percentage tag?

The draft and Google's help still say the old percentage tag must be 100. RFC 9989, which obsoletes RFC 7489, removed that tag, so a DMARCbis record simply leaves it out. A record without the tag meets the BIMI condition, because 100 was the old default. pct has been removed explains staging without percentages.

10

What are the most common BIMI record errors?

Most failures are silent. The record exists but sits at the wrong name, points to a file receivers reject, or sits on a domain whose DMARC policy disqualifies it. Check the items below in order before blaming the provider.

Error Example Fix
Wrong location Record at _bimi.example.com or bimi.example.com Publish at default._bimi.example.com
Doubled zone name Host entered as default._bimi.example.com in a panel that appends the zone, giving default._bimi.example.com.example.com Enter default._bimi only, then check with dig
Wrong version string v=BIMl (lowercase L) or v=BIMI Use v=BIMI1 with the digit one, as the first tag
HTTP instead of HTTPS l=http://example.com/logo.svg Host on HTTPS with a publicly trusted TLS certificate
SVG not Tiny PS Plain SVG export, missing baseProfile="tiny-ps", or x=/y= on the root Convert to SVG Tiny PS and validate
No certificate for Gmail Self-asserted record with no a= Obtain a VMC or CMC and add a=
Incomplete PEM chain PEM file holds only the entity certificate Include intermediate and root certificates
DMARC not at enforcement p=none, or t=y still set Move to p=quarantine or p=reject, then remove t=y
Subdomain policy sp=none on the organizational domain Remove sp= or set it to quarantine or reject
Two BIMI records Old and new records both published Keep exactly one record per selector

The t=y row is a judgement rather than a quoted rule. The draft does not mention the RFC 9989 test flag, but a domain asking receivers not to apply its policy is not one you should expect a logo on. DMARC for subdomains explains how sp= is inherited.

11

How do you verify a BIMI record with dig?

Query the TXT record at default._bimi with dig, then check the DMARC record for the same domain and its organizational domain. Then confirm that both URLs load over HTTPS and that the files are what receivers expect. The commands below cover all four checks.

# 1. The BIMI record (and the organizational domain fallback)
dig +short TXT default._bimi.example.com
dig +short TXT default._bimi.news.example.com

# 2. The DMARC policy that gates BIMI
dig +short TXT _dmarc.example.com

# 3. The logo: HTTPS status, content type and SVG profile
curl -sI https://brand.example.com/bimi/logo.svg
curl -s https://brand.example.com/bimi/logo.svg | grep -o 'baseProfile="[^"]*"'

# 4. The certificate chain in the PEM file
curl -s https://brand.example.com/bimi/vmc.pem -o vmc.pem
openssl crl2pkcs7 -nocrl -certfile vmc.pem | openssl pkcs7 -print_certs -noout

A long a= URL can push the record past 255 characters, so DNS may split it into several quoted strings. The draft says multiple strings are handled as in SPF (RFC 7208 Section 3.3): they are joined with no spaces. If dig shows two strings, check that the join does not break a URL. For browser checks, use our DNS lookup tool and the DMARC checker.

12

How should an MSP roll out BIMI records across clients?

Treat the BIMI record as the last change in a DMARC project, made under the same change control as any DNS edit. Confirm enforcement, prepare and host the files on a URL the client controls, publish one record per domain, and add the record to your monitoring so later changes do not silently remove the logo.

  1. Confirm the DMARC gate on the sending domain and organizational domain: p=quarantine or p=reject, no sp=none, no t=y. See how to move from monitoring to enforcement safely.
  2. Choose the evidence route with the client: VMC, CMC, or self-asserted for providers that accept it. Record the decision.
  3. Produce the SVG Tiny PS logo and check it against the BIMI Group rules.
  4. Host the files on a stable HTTPS path owned by the client, such as brand.<client domain>/bimi/, outside website rebuilds.
  5. Generate the record with the BIMI record generator and review the value before publishing.
  6. Publish under change control at default._bimi, with the ticket, client approval and rollback value recorded.
  7. Verify with dig and a test send to Gmail and Yahoo, allowing Google's stated 48 hours.
  8. Monitor and renew. Track certificate expiry per client, and alert on DMARC changes, logo URL failures or new subdomains that need a declination record.

For UK clients, the NCSC's email security guidance puts anti-spoofing controls first. That fits BIMI's order of work: enforcement is the protection, and the record is the visible result. DMARC AI for MSPs supports that enforcement work across a client portfolio.

13

FAQ

What is the difference between a BIMI record and a DMARC record?

A DMARC record at _dmarc.example.com tells receivers how to handle mail that fails authentication. A BIMI record at default._bimi.example.com tells them which logo to show for mail that passes. Receivers read the DMARC result first, and the BIMI record is ignored unless DMARC passes at an enforcing policy.

Is the a= tag required in a BIMI record?

Not by the draft, where a= is optional. In practice Gmail requires it: Google states that you need a VMC or CMC, and that the SVG-only option is not supported in Gmail. Yahoo, Fastmail and La Poste can show self-asserted logos without a=, subject to their own conditions.

Can I have more than one BIMI record on a domain?

You can have one record per selector, such as default._bimi and marketing._bimi. A message picks the second one with a DKIM-signed BIMI-Selector header. Two records under the same selector break discovery, because the draft says processing stops when more than one record is found.

Do subdomains need their own BIMI record?

No. If default._bimi does not exist at the sending subdomain, receivers fall back to the record at the organizational domain. Publish a subdomain record only to show a different logo, or publish v=BIMI1; l=; a=; to opt that subdomain out while the main domain keeps its logo.

How long does a BIMI record take to work?

DNS changes propagate according to the TTL, and Google suggests one hour for the BIMI record. Google also says a logo can take up to 48 hours to appear in Gmail after setup. Yahoo adds volume and reputation conditions, so a correct record does not guarantee an immediate logo there.

14

Related articles

Related tools

Ready to Implement?

Get authenticated mail moving in minutes: start free, book a guided demo, or talk to the team about your stack.