Publishing a BIMI DNS record requires three parts that are easy to blur together: graphic and certificate files hosted at public HTTPS endpoints, the DNS TXT assertion pointing to them for the domain in the From header, and verifiable evidence that each part works. The DNS record is how a receiving mail server discovers your assets; whether that provider displays your logo in the inbox is an entirely separate determination. This procedure keeps those parts distinct and records technical validity, provider acceptance, and observed display as three separate results.
It is written for a domain administrator coordinating DNS, hosting, and certificate owners, assuming sending identities and DMARC enforcement have already been assessed. Do not speed up a DMARC policy change for the sake of a logo. For broader background on BIMI, see BIMI: showing your logo in the inbox.
What does each receiver require for BIMI?
Provider documentation checked: 15 September 2026. Recheck provider guidance before initiating deployment.
Gmail requires a Verified Mark Certificate (VMC) or Common Mark Certificate (CMC) and a PEM reference; a VMC is what supports its verification checkmark. Google’s published DMARC conditions still specify quarantine or reject with pct=100, while RFC 9989 makes pct historic. Treat the gap as a compatibility question and check Google’s current documentation; it does not show whether Google has adopted RFC 9989. This procedure does not change any DMARC record. See Google’s BIMI setup requirements and RFC 9989 on the removal of pct. For a full breakdown of the RFC 9989 update, see DMARCbis (RFC 9989): what the latest standard changes.
Yahoo requires a record that references an SVG, DMARC quarantine or reject, bulk mail, and sufficient reputation and engagement for the sending address; personal mail is excluded. A VMC is currently optional, but supplying one informs eligibility. Yahoo publishes no numeric reputation threshold and no explicit CMC rule here (Yahoo’s BIMI conditions).
Apple Mail needs a receiving provider that is listed for BIMI and verified by Apple. That provider must check message and domain compliance, verify trusted evidence, and add verification headers, so an arbitrary account opened in Apple Mail is not enough, and Apple’s guidance does not promise universal CMC acceptance (Apple’s receiving-provider requirements).
Pin down the release identity
Before anything changes, write down the actual From address, the target providers, the approved logo version, the certificate owner, the intended resource URLs, the previous BIMI value and its TTL, and the administrator responsible for reversing the change.
For an email containing one From address and no BIMI-Selector header, the lookup name is default._bimi.<From-domain>. The name does not derive from your DKIM selector or asset web host. The current BIMI Internet-Draft’s discovery rules describe a fallback to the same selector at the organizational domain when no BIMI record remains at the author domain after version filtering; if more than one BIMI record remains, discovery stops. This procedure deploys an explicit default record at the author domain.
Freeze the files before you publish
For Gmail compatibility, author vector artwork strictly to the SVG Tiny PS profile with baseProfile="tiny-ps" and version="1.2". Canvas dimensions must specify absolute width and height of at least 96 pixels. Exclude all scripts, animations, external URLs, and root x or y attributes. Centering within a square canvas, using a solid background, a file size of 32 KB or less, and including a desc element are compatibility recommendations. A standard browser preview cannot validate profile rules, so a logo that renders in a browser has not been checked (Google’s BIMI setup requirements).
Obtain real issuance from a certificate authority (CA) that assesses your domain coverage and eligibility. For Gmail, append the issued chain as instructed, which is normally entity, intermediates, then root, and retain the approved bytes (Google’s BIMI setup requirements).
Host the files at stable, publicly accessible HTTPS URLs. Fetch the complete bodies without logging in, preserve the response headers, and compare bytes with your controlled copies; a successful status code or a plausible filename is not enough. Google’s BIMI file troubleshooting covers public access, packaging, and exact URL checks.
Two distinct certificates are in play here, doing different jobs: the web server TLS certificate secures HTTPS transport, while the BIMI mark certificate certifies the brand mark. For the mark certificate, verify validity dates, issuer trust, revocation status, Certificate Transparency evidence, BIMI extended key usage, certificate chain, embedded SVG, and Subject Alternative Name (SAN), following the draft’s certificate issuance and profile checks. Verify SAN coverage for the author domain or complete selector hostname; the logo host alone does not establish coverage. The certificate validation draft addresses VMCs, and Google directs CMC users to that guidance in Google’s BIMI setup requirements.
The hosted SVG must remain identical to the mark embedded in the certificate. Any mismatch can fail embedded-logo verification, so if artwork is modified, take it back to the CA for new assessment.
A synthetic example that ends in a hold
This invented newsletter example uses reserved domains. No artwork, certificate, DNS deployment, retrieval or message test exists. The planned sender is news@letters.example.net, with no selector header and no local-part selector. The existing assessed policy at _dmarc.example.net is v=DMARC1; p=quarantine; sp=quarantine; pct=100, with no author-domain override. (That policy reflects Google’s published legacy requirement, not modern DMARC syntax advice.)
The intended SVG is Tiny PS, 160 by 160 absolute pixels, with viewBox="0 0 160 160" and all prohibited elements stripped; the approved artwork file does not exist yet. The intended Gmail certificate is a CMC, but eligibility, issuance, chain, SAN, expiry, revocation, transparency, and embedded-mark evidence are all missing.
The planned TXT owner is default._bimi.letters.example.net, TTL 3600 seconds, with this single logical value:
v=BIMI1; l=https://letters.example.net/bimi/mark-v1.svg; a=https://letters.example.net/bimi/mark-v1.pem
Here l locates the logo and a the certificate evidence, and both are populated. Google also documents a record with an empty l= tag beside the a= PEM URL; do not assume every receiver accepts that path. See Google’s BIMI DNS instructions and the draft’s BIMI assertion syntax.
Decision: hold before publication. Planned strings cannot stand in for approved artwork and an issued certificate. The brand owner must supply the artwork, the certificate owner must obtain issuance and validation evidence, and the hosting owner must provide public retrieval evidence. Technical deployment, provider acceptance, and inbox display all remain unverified.
Publish the record and collect the verification evidence
Once your prerequisites are verified, save the previous state and publish one BIMI assertion. Check whether the DNS panel automatically appends the zone name. Query the complete owner name at authoritative DNS and independent recursive resolvers, and compare the returned value with the approved value; one resolver cannot establish that every cache has updated (Google’s BIMI DNS instructions).
This evidence record applies before and after publication:
| Evidence | What it establishes | If missing or failed |
|---|---|---|
| Exact TXT name, value and TTL | The queried DNS state matches the release | Hold or reverse the BIMI change. |
| Full GET responses from both URLs in the BIMI record | Public retrieval returns the intended files | Resolve access or byte differences before proceeding. |
| Certificate identity, status, chain and matching mark | The selected certificate checks have supporting evidence | Obtain CA/provider-appropriate validation. |
| Recipient-generated authentication results | Whether the tested message passed DMARC with an aligned mechanism | Investigate authentication separately. |
| Receiver evidence, client, message and observation time | Provider acceptance, where evidenced, and whether a logo was seen | Record unknown acceptance or unobserved display explicitly. |
Fetch the exact URLs that DNS returned once more and repeat file and certificate checks. Printing certificate text with OpenSSL only inspects it; it does not establish trusted BIMI roots, revocation, transparency, or provider acceptance.
The last two rows need an authorized real message. A DMARC pass needs a passing mechanism aligned to From; it cannot prove business authorization, delivery of other messages, or inbox placement. Record technical validity, provider acceptance, and observed display as three separate results. See DMARC authentication and alignment and the draft’s BIMI receiver results.
Reverse failures and hand over maintenance
In this example, no prior BIMI record exists at either the author or the organizational domain. If your new record fails checks after going live, remove the new assertion, verify authoritative DNS and record the caches as pending. For a replacement, restore the saved valid assertion and resources. In either case, keep DMARC unchanged: the rollback concerns only the BIMI assertion and its hosted resources.
Hand over the record, TTL, file versions, certificate expiry, renewal owner, and any unresolved provider observations. Stage valid replacement resources before changing references, and keep valid previous files during the transition, because receiver certificate caching has no universal duration in the certificate fetch draft; DNS TTL is not a display deadline.
Related reading: Check BIMI readiness for missing prerequisites, Prepare a DNS change for change control, and Diagnose a missing BIMI logo when technical checks pass but display remains absent.
Frequently asked questions
What is the lookup name for a BIMI record?
For a message with one From address and no applicable BIMI-Selector header, the lookup name is default._bimi.. Neither the DKIM selector nor the asset hostname determines this name. The draft’s discovery rules describe a fallback to the same selector at the organizational domain when no BIMI record remains at the author domain after version filtering; if more than one record remains, discovery stops.
Does Gmail accept a plain SVG without a certificate?
No. Gmail requires a Verified Mark Certificate (VMC) or Common Mark Certificate (CMC) and a PEM reference; a VMC is what supports its verification checkmark.
Is a logo that renders in a browser already validated?
No. A browser preview cannot validate the SVG Tiny PS profile, so a logo that renders in a browser has not been checked.
Does one resolver returning the new value prove the record is live everywhere?
No. One resolver cannot establish that every cache has updated. Query the complete owner name at authoritative DNS and at independent recursive resolvers, and compare the returned value with the approved value.
Does a BIMI rollback change the DMARC record?
No. Whether you remove or replace the BIMI assertion, DMARC stays unchanged: the rollback concerns only the BIMI assertion and its resources.


