BIMI Technical Reference
How BIMI works underneath: the record syntax and lookup rules, the DMARC policy receivers demand, the SVG Tiny PS profile, what a VMC or CMC adds, and how to find out why no logo shows.
Quick Overview
What BIMI Is, and What It Is Not
BIMI (Brand Indicators for Message Identification) is a DNS record that tells a receiving mail provider which logo belongs to your domain. The provider shows that logo only after the message has passed DMARC under an enforcing policy and, at the largest providers, after it has validated a mark certificate that binds the logo to your organisation. The record is a request, never a guarantee: the receiver decides whether anything is displayed.
The protocol is specified in an Internet-Draft maintained by the BIMI Group (draft-brand-indicators-for-message-identification). The certificates are governed by the BIMI Group's Minimum Security Requirements for Mark Certificates. BIMI does not authenticate mail itself; it sits on top of SPF, DKIM and DMARC.
This page is the technical reference. For the setup steps in order, use the BIMI setup guide. For certificate prices and whether a VMC is worth buying, see BIMI certificate cost: VMC vs CMC. For the route without a VMC, see BIMI without a VMC.
BIMI Record Syntax
A BIMI assertion record is a TXT record at <selector>._bimi.<domain>. The selector is "default" unless the message names another one. The record is a semicolon-separated list of tags: v= comes first, the rest may follow in any order, and receivers ignore tags they do not know.
| Tag | Required | Value | Notes |
|---|---|---|---|
| v | yes | BIMI1 | Must be the first tag and match exactly, or the record is ignored. |
| l | yes, may be empty | HTTPS URL of the SVG logo | SVG or SVGZ in the SVG Tiny PS profile only. Left empty when the logo comes from the certificate. |
| a | no | HTTPS URL of a PEM evidence document | The VMC or CMC. Empty or absent means no evidence. Gmail requires it. |
| avp | no | brand or personal | Added in recent drafts: whether a provider that shows personal avatars should prefer the logo. Default brand; support varies. |
# Certificate-backed, as Google documents it (the logo is inside the PEM)
default._bimi.example.com. 3600 IN TXT "v=BIMI1; l=; a=https://example.com/bimi/vmc.pem"
# Certificate plus SVG URL, as many issuers and generators produce it (also valid)
default._bimi.example.com. 3600 IN TXT "v=BIMI1; l=https://example.com/bimi/logo.svg; a=https://example.com/bimi/vmc.pem"
# Self-asserted SVG only (Gmail and Apple Mail do not display these)
default._bimi.example.com. 3600 IN TXT "v=BIMI1; l=https://example.com/bimi/logo.svg"
# Declination: this subdomain explicitly takes no part in BIMI
default._bimi.shop.example.com. 3600 IN TXT "v=BIMI1; l=; a=;"Publish exactly one v=BIMI1 record per selector name. Zero or more than one valid record at the queried name means no BIMI for that message.
How Receivers Find the Record
The lookup follows the visible From: domain (the Author Domain), not the envelope sender or the DKIM d= domain:
1. Take the selector from the message's BIMI-Selector header (for example "BIMI-Selector: v=BIMI1; s=brand2026"). Without that header the selector is "default". 2. Query <selector>._bimi.<From domain> and discard any TXT record that does not start with v=BIMI1. 3. If nothing is left, query <selector>._bimi.<organizational domain>. A record on example.com therefore also covers mail From news.example.com, unless news.example.com publishes its own record or a declination. 4. If the result is still zero records, or more than one, the message gets no logo.
Use a BIMI-Selector header only when different mail streams need different logos, and include it in the headers your DKIM signature covers: the draft allows receivers to discount a selector header that is not signed.
DMARC Requirements in Detail
BIMI is evaluated only for messages that pass DMARC, and the policy itself has to meet extra conditions. Receivers check them on the From domain and on its organizational domain:
• p= must be quarantine or reject. Mail from a domain at p=none is never eligible, even when it passes DMARC. • pct must be 100 with p=quarantine. The draft accepts any pct with p=reject, but Google requires pct=100 in every case. Treat pct=100, or no pct tag at all (the default is 100), as the rule. • sp= must not be none. The draft tells receivers to skip BIMI when the From domain's or the organizational domain's DMARC record contains sp=none. That disqualifies mail from the apex domain too, not only from subdomains. • Pass means aligned. DMARC passes only when SPF or DKIM passes for a domain aligned with From. Aligned DKIM is the dependable route because it survives forwarding. • Subdomains need enforcement of their own. Mail From news.example.com is judged by the _dmarc record of news.example.com if one exists, otherwise by the sp= (or p=) of example.com.
Getting from p=none to enforcement without losing legitimate mail is usually the longest part of a BIMI project; the staged rollout is in the DMARC guide.
# Eligible
v=DMARC1; p=reject; rua=mailto:dmarc@example.com
v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@example.com
# Not eligible
v=DMARC1; p=none; rua=mailto:dmarc@example.com # monitoring only
v=DMARC1; p=quarantine; pct=50; rua=mailto:dmarc@example.com # partial quarantine
v=DMARC1; p=reject; sp=none; rua=mailto:dmarc@example.com # sp=none blocks BIMILogo Requirements: SVG Tiny PS
BIMI logos use SVG Tiny Portable/Secure (SVG Tiny PS), a restricted profile of SVG Tiny 1.2 published by the BIMI Group. Ordinary SVG exported from a design tool almost never passes as it is. The rules below combine the profile with the limits Google publishes for Gmail:
| Requirement | Rule |
|---|---|
| Profile | The root element has version="1.2" and baseProfile="tiny-ps" |
| Title | A title element with the brand name is required |
| Root attributes | No x= or y= attributes on the root svg element |
| Forbidden content | No scripts, animation, interactive elements or references to external resources |
| Shape | Square, with the logo centred; clients crop it to a circle or rounded square |
| Size (Gmail) | At least 96 by 96 pixels, dimensions in absolute pixels, file 32 KB or smaller |
| Background | A solid background; a transparent one can disappear against the client's avatar colour |
| Transport | Served over HTTPS as image/svg+xml, without redirects, cookies or login |
<svg xmlns="http://www.w3.org/2000/svg" version="1.2" baseProfile="tiny-ps"
width="96" height="96" viewBox="0 0 96 96">
<title>Example Brand</title>
<rect width="96" height="96" fill="#ffffff"/>
<!-- logo paths, centred; no script, no external href -->
</svg>With a VMC or CMC, the logo that counts is the one embedded in the certificate. Changing the SVG on your web server does not change what certificate-validating providers show; a new logo means a new certificate.
Evidence Documents: VMC and CMC
A mark certificate is an X.509 certificate that carries your SVG logo inside it and ties it to your domain and organisation. The certificate authority validates the organisation, the domain and the right to use the mark before issuing it. Receivers that require evidence fetch the PEM file from the a= URL, validate the chain to a mark-certificate root they trust, check the validity dates and that the certificate covers the From domain, and display the logo embedded in it.
The two types differ in the evidence for the mark, not in how receivers process them. Prices, eligibility questions and the buy-or-wait decision are covered in BIMI certificate cost: VMC vs CMC; issuers are listed by the BIMI Group.
| Aspect | Verified Mark Certificate (VMC) | Common Mark Certificate (CMC) |
|---|---|---|
| Evidence for the mark | Registered trademark at a recognised office, or an eligible government mark | Evidence of prior use of the logo, validated by the issuer |
| Organisation and domain validation | Yes | Yes |
| Logo display in Gmail | Yes | Yes |
| Blue verified checkmark in Gmail | Yes | No |
| Lifetime | Renewed periodically; display stops when it expires | Renewed periodically; display stops when it expires |
# The a= URL serves one PEM file: the entity certificate first, then the chain
-----BEGIN CERTIFICATE-----
(entity certificate: your domain, your organisation and the embedded SVG logo)
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
(intermediate CA certificate)
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
(root CA certificate, when your issuer says to include it)
-----END CERTIFICATE-----How Mailbox Providers Validate BIMI
Receivers do not publish their full logic, but the draft and provider documentation describe the same sequence:
1. Authenticate the message. Exactly one From: address, and DMARC passes for its domain. For forwarded mail some receivers also accept a trusted ARC chain. 2. Check the policy. p=quarantine or p=reject on the From domain and its organizational domain, pct=100 for quarantine, no sp=none. 3. Find the record. Selector from BIMI-Selector or "default"; From domain first, organizational domain as fallback. 4. Validate the evidence. Fetch the a= PEM and validate it; or, at a receiver that accepts self-asserted logos, fetch and check the l= SVG. 5. Apply local policy. Sender reputation, volume and the receiver's own rules decide whether the logo is shown. A completely valid setup can still show nothing. 6. Hand the result to the client. The receiver removes any BIMI-Location and BIMI-Indicator headers the sender added and inserts its own, which the mail client uses to draw the logo. Some receivers also record bimi=pass in Authentication-Results.
Provider rules change, and the BIMI Group keeps the current list of participating providers. Two are documented precisely: Gmail displays a logo only with a VMC or CMC, and shows the checkmark only with a VMC; Apple Mail shows a logo only when the receiving mail provider has verified a BIMI evidence document, such as a VMC, and added the required headers. A self-asserted SVG is therefore not enough for either.
Troubleshooting: Record Published, No Logo
Work from the bottom of the stack up. Most "BIMI is not working" reports turn out to be a DMARC or evidence problem rather than a problem with the BIMI record.
| Symptom | Likely cause | Check |
|---|---|---|
| No logo at any provider | DMARC at p=none, pct below 100, or sp=none | DMARC record of the From domain and of the organizational domain |
| No logo for mail from a subdomain | The subdomain's DMARC policy is not enforcing, or the subdomain publishes a declination | _dmarc and default._bimi on the subdomain |
| No logo in Gmail | No a= evidence, or the PEM fails validation | Fetch the PEM; inspect the chain and the dates |
| No logo in Apple Mail with a self-asserted SVG | Apple requires a verified evidence document | Expected; use a certificate-backed record |
| Checkers report no record | Record at the wrong name, or two v=BIMI1 records | dig the exact name default._bimi.<domain> |
| Logo appeared, then stopped | Certificate expired, PEM URL now redirects or returns HTML, or DMARC was relaxed | Repeat the checks below |
| Logo on some messages only | One sending platform fails DMARC alignment | Compare Authentication-Results per platform |
# 1. Exactly one record, at the right name
$ dig +short TXT default._bimi.example.com
"v=BIMI1; l=; a=https://example.com/bimi/vmc.pem"
# 2. DMARC on the From domain (and on the organizational domain if it differs)
$ dig +short TXT _dmarc.example.com
"v=DMARC1; p=reject; rua=mailto:dmarc@example.com"
# 3. Evidence reachable directly over HTTPS: expect 200, no redirect
$ curl -sI https://example.com/bimi/vmc.pem | head -1
HTTP/2 200
# 4. Subject, issuer, validity dates and covered domains of the entity certificate
$ curl -s https://example.com/bimi/vmc.pem | openssl x509 -noout -subject -issuer -dates -ext subjectAltName
# 5. Every certificate in the file, in order
$ curl -s https://example.com/bimi/vmc.pem | openssl crl2pkcs7 -nocrl -certfile /dev/stdin | openssl pkcs7 -print_certs -noout
# 6. The SVG root element: version, baseProfile, no x or y
$ curl -s https://example.com/bimi/logo.svg | grep -o '<svg[^>]*>'When every check passes, the headers of a delivered message are the final proof. Some receivers stamp a line such as: Authentication-Results: mx.example.net; bimi=pass header.d=example.com header.selector=default
Verify and Next Step
The free BIMI Checker reads default._bimi, fetches the SVG and the a= evidence URL, and checks that DMARC is enforced, which covers checks 1 to 3 above in one step. Format the TXT value with the BIMI Record Generator and confirm the policy with the DMARC Checker. If you are starting from scratch, follow the BIMI setup guide in order and come back here when something does not show.
Common Pitfalls to Avoid
- DMARC not at p=quarantine or p=reject
BIMI requires DMARC enforcement: p=quarantine with pct=100, or p=reject, and no sp=none. p=none will not work.
- Invalid SVG format
BIMI requires SVG Tiny 1.2 Portable/Secure format. Regular SVGs, PNGs, or JPEGs will not work.
- Logo not square or centered
Your logo must be square and centered with important content in the center 2/3 for proper display.
- Missing VMC or CMC for Gmail
Gmail only displays certificate-backed BIMI: a VMC or CMC at the a= URL. Apple Mail also requires the receiving provider to verify an evidence document, so a self-asserted SVG is not enough there either.
- HTTPS URL issues
Logo and certificate URLs must be HTTPS with valid SSL. Self-signed certificates will fail.
Related tools & guides
Frequently asked questions
What is BIMI and what does it do?
BIMI (Brand Indicators for Message Identification) lets your verified brand logo appear next to your messages in supporting inboxes instead of a generic avatar. It builds on DMARC: only domains that authenticate and enforce DMARC can display a BIMI logo, so it both improves brand recognition and signals a strong authentication posture.
Does BIMI require an enforced DMARC policy?
Yes. BIMI requires a DMARC policy of p=quarantine or p=reject, typically with pct=100. BIMI will not display with p=none. You must reach DMARC enforcement before BIMI logos appear in any supporting client.
Do I need a VMC or CMC certificate for BIMI?
It depends on the mailbox provider. Gmail uses a certificate-backed path and requires a Verified Mark Certificate (VMC) or Common Mark Certificate (CMC) at the a= URL to display your logo; a VMC also shows the blue verified checkmark. Apple Mail also requires a verified evidence document, so a self-asserted SVG is not shown there. Other providers set their own rules; the BIMI Group keeps the current list of participating providers.
What image format does BIMI require?
BIMI requires the logo in SVG Tiny 1.2 Portable/Secure (SVG Tiny P/S) format — square, with a solid background, no scripts, animations, or external references, and typically under 32KB. PNG, JPEG, or regular SVG files will not work. Host it on a stable HTTPS URL with a valid certificate.
What does a BIMI DNS record look like?
A BIMI record is a TXT record at default._bimi.yourdomain.com. Without a certificate it is v=BIMI1; l=https://yourdomain.com/bimi/logo.svg. For Gmail logo display, add the authority tag: v=BIMI1; l=https://yourdomain.com/bimi/logo.svg; a=https://yourdomain.com/bimi/certificate.pem.