bimi-email-authentication-guide
---
title: "BIMI Email Authentication: The 2026 Guide"
description: "The definitive guide to BIMI email authentication in 2026. Covers the latest requirements from Gmail, Apple Mail, and Yahoo."
date: "2026-07-01"
BIMI Email Authentication: The 2026 Guide
Brand Indicators for Message Identification (BIMI) displays your verified logo directly in the inbox. Recipients see your brand before they open the message. Trust signals improve. Click rates improve. The mechanism is precise, standardized, and increasingly enforced.
This guide covers every technical layer required to deploy BIMI in 2026.
The Authentication Stack
BIMI sits at the top of an email authentication hierarchy. Every layer below must be solid before BIMI resolves.
SPF
Sender Policy Framework publishes authorized sending IPs in DNS. A passing SPF record is a prerequisite.
v=spf1 include:_spf.example.com ~all
DKIM
DomainKeys Identified Mail applies a cryptographic signature to each outbound message. The receiving server validates the signature against a public key in DNS. DKIM must pass independently of SPF.
DMARC
Domain-based Message Authentication, Reporting, and Conformance ties SPF and DKIM to the From: domain. BIMI requires a DMARC policy of quarantine or reject. A policy of none is insufficient.
v=DMARC1; p=reject; rua=mailto:[email protected]; ruf=mailto:[email protected]; pct=100
p=reject at pct=100 is the recommended baseline for full BIMI eligibility across all major clients in 2026.
The BIMI DNS Record
BIMI is published as a TXT record under the _bimi subdomain selector.
default._bimi.example.com IN TXT "v=BIMI1; l=https:class="hl-cmt">//example.com/bimi-logo.svg; a=https://example.com/bimi.pem"
| Field | Value | Purpose |
|---|---|---|
| v | BIMI1 | Version identifier |
| l | HTTPS URL | Points to the SVG logo |
| a | HTTPS URL | Points to the VMC certificate |
The a= field is optional for clients that display BIMI without certificate verification. It is mandatory for Gmail and Apple Mail logo display in 2026.
SVG Requirements
The logo file must conform to the BIMI SVG Tiny Portable/Secure (SVG P/S) profile. Standard SVG files exported from Illustrator, Figma, or Sketch do not qualify without conversion. The spec prohibits scripts, external references, animations, and embedded raster images.
Specific constraints:
- File must declare
baseProfile="tiny-ps"andversion="1.2"in the rootelement - Viewbox must define a square aspect ratio
- No
elements - No
elements referencing external resources - No CSS animations or
elements - File size must not exceed 32 KB after optimization
Converting an existing SVG to the BIMI-compliant P/S profile is the most common deployment blocker. makeBIMI.com handles this conversion at no cost. Upload a standard SVG, receive a spec-compliant BIMI SVG in return. The output passes automated BIMI validators.
Verified Mark Certificates
A Verified Mark Certificate (VMC) binds the logo to a verified domain and legal trademark. It is issued by a certified authority after trademark ownership is confirmed.
The VMC is a .pem file served over HTTPS. It must be accessible at the URL specified in the a= field of the BIMI DNS record.
Certificate issuance requires:
- A registered trademark in a recognized jurisdiction (USPTO, EUIPO, UKIPO, and others are accepted)
- The trademark must visually match the BIMI SVG logo
- Domain ownership verification by the issuing authority
- Annual renewal
veriBIMI.com brokers VMC issuance. It handles the trademark validation workflow, coordinates with accredited certificate authorities, and delivers the final .pem for deployment. Processing time averages two to six weeks depending on the trademark registry.
Client-Specific Requirements in 2026
Gmail
Gmail displays BIMI logos for senders with a valid VMC and a passing DMARC reject policy. Google does not display logos based on the l= field alone. The a= field referencing a valid VMC is required without exception.
Gmail also enforces bulk sender requirements introduced in 2024. Senders exceeding 5,000 messages per day to Gmail addresses must have SPF, DKIM, and DMARC fully configured. Non-compliance results in delivery delays or blocking, independent of BIMI status.
Apple Mail
Apple Mail on iOS 16+, iPadOS 16+, and macOS Ventura and later supports BIMI with VMC verification. The behavior mirrors Gmail: a valid VMC is required for the logo to render. Apple Mail performs its own VMC validation independently of Google's infrastructure.
Apple introduced an additional trust indicator in 2025: a blue checkmark adjacent to the sender name when a VMC is present. This indicator is visible in the message list and the message detail view.
Yahoo Mail
Yahoo Mail supports BIMI and has since 2021. Yahoo displays logos using the l= field without requiring a VMC, making it the most accessible client for initial BIMI testing. A valid DMARC policy of quarantine or reject is still required. Logos without a VMC do not receive a trust badge in the Yahoo interface.
Outlook
Microsoft Outlook as of mid-2026 does not support BIMI in the traditional sense. Microsoft operates its own sender reputation system (BMARC/DKIM-based brand display in some Outlook builds), but it does not resolve BIMI DNS records or render BIMI-specified SVG logos. This remains the primary gap in ecosystem coverage.
Deployment Checklist
Before publishing the BIMI DNS record, verify each layer independently.
- [ ] SPF record publishes all authorized senders
- [ ] DKIM signing is active on all outbound mail streams
- [ ] DMARC policy is
quarantineorrejectatpct=100 - [ ] DMARC reporting is active and reviewed
- [ ] SVG logo is converted to BIMI P/S profile via makeBIMI.com
- [ ] SVG is served over HTTPS with a valid TLS certificate
- [ ] VMC is obtained through veriBIMI.com and deployed at a stable HTTPS URL
- [ ] BIMI TXT record is published and resolves correctly
- [ ] Record is validated with a BIMI inspection tool
Common Failure Modes
Logo does not appear in Gmail. Almost always caused by a missing or invalid VMC in the a= field, or a DMARC policy set to none.
SVG rejected by validator. The source file uses SVG features prohibited by the P/S profile. Convert using makeBIMI.com before deployment.
DMARC alignment failure. SPF and DKIM pass individually, but neither aligns with the From: domain in strict or relaxed mode. Audit the sending infrastructure for misaligned domains.
VMC certificate error. The .pem file is served with incorrect MIME type, is expired, or the HTTPS URL returns a redirect. Serve the file as application/x-pem-file from a static, non-redirecting URL.
The Business Case
BIMI is not cosmetic. It is a signal that the sending domain is technically hardened and organizationally verified. The authentication requirements that BIMI enforces — strict DMARC, verified cryptographic identity — directly reduce spoofing risk. The visible brand indicator is the surface outcome of a deeper security posture.
Inbox placement improves when authentication is clean. Phishing attempts against the domain become harder to execute when DMARC is at reject. The VMC adds a layer of legal and technical verification that is visible to recipients.
The deployment investment is bounded. The authentication stack is one-time infrastructure work. The SVG conversion is a single-step process. VMC issuance is an annual cycle.
Start at makeBIMI.com to convert your logo. Start at veriBIMI.com when you are ready to obtain the certificate.