Suped

What email providers support BIMI without a VMC, and what are key considerations for BIMI implementation?

Published 3 Jun 2025
Updated 25 Oct 2026
13 min read
Summarize with
BIMI without a VMC illustrated with an inbox logo and authentication documents.
Updated on 25 Oct 2026: We clarified certificate-free BIMI support, Gmail's CMC option, and the provider requirements for implementation.
Yahoo Mail and Fastmail support Brand Indicators for Message Identification (BIMI) without a certificate. La Poste also supports self-asserted BIMI, subject to domain approval, and Yahoo supports it for AOL users. Gmail supports BIMI without a Verified Mark Certificate (VMC) when you use a Common Mark Certificate (CMC), but it does not accept certificate-free BIMI. Apple Mail requires a supported BIMI Evidence Document, and both the sender and receiving email provider must meet Apple's requirements. Outlook.com, Hotmail, and Microsoft 365 receiving services do not currently render standard BIMI logos for normal inbound mail.
A certificate-free BIMI pilot has value when the test matches provider requirements. Use it to prove the DNS, SVG hosting, DMARC enforcement, and provider-specific rendering path. Do not use it to forecast Gmail or Apple Mail lift, because those environments require a certificate or supported evidence document. If leadership wants a first measurement before paying for a VMC, segment the audience by mailbox provider and treat Yahoo Mail, AOL, Fastmail, and La Poste as the test group.
The bigger blocker is usually not the BIMI record itself. It is whether the domain has real DMARC monitoring, an enforced policy, complete sender coverage, and a logo file that receivers accept. Suped's DMARC reporting product helps identify legitimate sending sources that fail authentication before you enforce DMARC, and monitor those sources after BIMI goes live.

Provider support without a VMC

The provider split is the first thing to make clear internally. BIMI support and certificate-free BIMI support are different questions. A mailbox provider can support BIMI but still refuse to display a logo unless the BIMI record points to a certificate or another evidence document. That is why a self-asserted BIMI record works in a narrow set of places and fails quietly in others.

Provider or client

Certificate-free display

Implementation note

yahoo.com logoYahoo Mail
Yes, subject to eligibility
Bulk mail with sufficient sender reputation and engagement
AOL
Yes, in Yahoo-supported applications
Apply Yahoo requirements and measure AOL separately
fastmail.com logoFastmail
Yes
SVG logo file must be smaller than 16 KB
La Poste
Yes, after approval
Contact the La Poste postmaster for self-asserted BIMI approval
google.com logoGmail
No
A CMC works without a VMC; the Gmail checkmark requires a VMC
apple.com logoApple Mail
No
Needs accepted evidence and a compatible receiving provider
microsoft.com logoOutlook.com / Microsoft 365
No
No standard BIMI receiving support in Outlook.com or Microsoft 365
BIMI support with and without certificates
The BIMI guide covers the baseline requirements and notes that every participating mailbox provider applies its own display criteria. Provider behavior changes, so validate the actual inboxes in your audience instead of copying a support list into a business case. The BIMI provider support list covers additional participants; inclusion does not establish certificate-free display eligibility.
Yahoo's BIMI requirements limit display to bulk mail with sufficient sender reputation and engagement. A single personal test message is not a reliable display test. La Poste's BIMI policy requires senders without a VMC to contact its postmaster for approval before expecting a logo.
Apple Mail is an email client, so record the receiving mailbox provider separately from the app used to read the message. Apple's BIMI support documentation lists support in iOS 16, iPadOS 16, macOS Ventura 13 or later, and iCloud.com. Both sides must meet its requirements; do not assume that a CMC accepted by Gmail is accepted by Apple.
Illustrated Yahoo Mail inbox showing BIMI logos beside sender names.
Illustrated Yahoo Mail inbox showing BIMI logos beside sender names.
What a certificate-free test establishes
Successful self-asserted BIMI display confirms that your DNS and logo path can work. It does not prove that Gmail, Apple Mail, or Microsoft recipients will see the same thing.
  1. Scope: Report Yahoo Mail, AOL, Fastmail, and La Poste results separately. Record Apple Mail usage alongside the receiving provider.
  2. Metric: Prefer clicks, replies, conversions, and complaint rate over open-rate movement.
  3. Caveat: A provider can suppress display because of local policy, reputation, or low volume.

VMC, CMC, and self-asserted BIMI

The simplest way to think about BIMI is that the DNS record tells receivers where the logo or certificate-backed evidence lives. The receiver then decides whether to display it. The receiving provider has the final say, not the sender, DNS host, or email service platform.
Self-asserted BIMI
This is the certificate-free path. You publish a BIMI TXT record that points directly to an SVG Tiny PS logo and omit the a= evidence tag or leave its value empty.
  1. Works: Useful for Yahoo Mail and AOL, Fastmail, and approved La Poste domains.
  2. Limits: No Gmail display, no Apple Mail display, no verified mark, and limited business-case coverage.
Certificate-backed BIMI
This path points the BIMI record to a PEM file containing a VMC or CMC. The certificate connects the logo, legal organization, and domain.
  1. Works: Gmail accepts a VMC or CMC. Apple Mail requires a supported evidence document and a compatible receiving provider.
  2. Limits: Plan for organization validation and logo eligibility, plus certificate renewal and hosting.
A Verified Mark Certificate (VMC) is the usual path for a registered trademarked logo. A Common Mark Certificate (CMC) accommodates eligible unregistered logos or modified registered marks. Google's BIMI setup documentation confirms that Gmail accepts either certificate for logo display, but its verification checkmark requires a VMC. If your main question is specifically Gmail, review Gmail VMC requirements before you build the rollout plan.
A CMC still requires validation. For the prior-use route, the Mark Certificate requirements require evidence that the logo is currently displayed on a domain you control and was displayed on that same domain at least 12 months before verification. Check eligibility before budgeting for a CMC.
If the budget conversation is stuck, publish the self-asserted record only after DMARC is fully ready. That lets you measure the certificate-free providers and prove that the operational base is clean. Then decide whether a CMC or VMC belongs in the next phase. Self-asserted BIMI avoids certificate fees, but logo preparation and hosting still require resources. Compare certificate quotes for domain coverage and renewal costs before choosing a CMC or VMC.

DNS records and enforcement requirements

BIMI depends on DMARC enforcement. A domain at p=none is not ready. A domain at p=quarantine or p=reject is the baseline at the organizational domain and applicable subdomains. The visible From domain must pass DMARC, which means SPF or DKIM has to pass with alignment that DMARC accepts for that domain. Configure both SPF and DKIM for legitimate senders; DKIM is especially useful when forwarding breaks SPF. BIMI does not require strict adkim=s or aspf=s modes; the relaxed defaults are valid when DMARC passes. RFC 9989 moved the old pct tag to historic status, although provider documentation still refers to pct=100. For BIMI, enforce the policy for all applicable mail. Where a legacy record still includes pct, it must not request less than 100 percent. Omitting the legacy tag uses its RFC 7489 default of 100 percent. See the BIMI implementation requirements.
BIMI readiness by DMARC policy
Both enforced policies qualify when DMARC passes and applicable subdomains are also at enforcement, without testing mode.
Not ready
p=none
Authentication can be monitored, but BIMI display should not be expected.
Enforcement eligible
p=quarantine
A valid BIMI policy for ongoing use when legitimate mail authenticates.
Stricter failure handling
p=reject
Requests rejection of DMARC failures; logo display still depends on provider criteria.
DMARC record that can support BIMIDNS
Host: _dmarc.example.com Type: TXT Value: v=DMARC1; p=quarantine; sp=quarantine; rua=mailto:dmarc@example.com;
RFC 9989 uses t=y for policy testing. It asks receivers to apply a policy one level below the published value to failing mail, so p=quarantine; t=y is treated like p=none and p=reject; t=y is treated like p=quarantine. Remove testing mode before a live BIMI measurement. These testing semantics are defined in RFC 9989; they do not establish BIMI eligibility for testing policies.
Before publishing BIMI, validate the DMARC record with a DMARC checker and confirm the real mail stream still passes after enforcement. Suped's DMARC reports and issue workflows help identify the sender that needs attention before you change its DNS or sending configuration.
?

What's your domain score?

Deep-scan SPF, DKIM & DMARC records for email deliverability and security issues.

Check the whole domain, not only the BIMI hostname. A domain health checker is useful here because BIMI readiness includes DMARC, SPF, DKIM, DNS visibility, and mail-source hygiene. A clean BIMI TXT record will not rescue a sender that fails DMARC for normal campaign traffic.
The logo file also needs its own review. Use SVG Tiny PS and center the mark in a square canvas with a solid background. Gmail recommends a file no larger than 32 KB and requires absolute dimensions of at least 96 by 96 pixels. Include baseProfile="tiny-ps" and version="1.2" attributes and a title element describing the organization. Remove scripts, animation, external resources, and embedded raster images. Wordmarks are allowed when they meet the SVG and certificate requirements. Host the file on a public HTTPS URL that returns the SVG directly with an image/svg+xml content type. BIMI is configured for a domain you own and control; it does not work as a sender-logo shortcut for mail sent from free consumer domains. See Gmail's SVG requirements for its format and sizing rules.
Fastmail's BIMI requirements specify an SVG file smaller than 16 KB. Use that tighter limit for a shared logo intended for Fastmail as well as other providers.
BIMI record examplesDNS
Self-asserted BIMI: Host: default._bimi.example.com Type: TXT Value: v=BIMI1; l=https://brand.example.com/bimi.svg; a=; Certificate-backed BIMI: Host: default._bimi.example.com Type: TXT Value: v=BIMI1; l=https://brand.example.com/bimi.svg; a=https://brand.example.com/vmc.pem;
In the certificate-backed example, use your CMC PEM URL instead when deploying a CMC. Keeping both the SVG URL in l= and the PEM URL in a= supports receivers that fetch the standalone logo as well as those that validate the certificate. The hosted SVG must match the certified logo, and the PEM must include the required certificate chain.

Subdomains and BIMI inheritance

For subdomains, the practical answer is usually yes, a BIMI record at the organizational domain can apply to subdomains that do not publish their own BIMI record. Still test every visible From domain because receiver behavior, DMARC subdomain policy, and certificate coverage can change the outcome.
BIMI subdomain lookup showing fallback to the organizational domain before logo display.
BIMI subdomain lookup showing fallback to the organizational domain before logo display.
The important rule is that BIMI follows the authenticated visible From domain, not a tracking domain or bounce domain. If you send as news.example.com, the receiver evaluates that domain's authentication result and then looks for the BIMI assertion path. If there is no subdomain-specific BIMI record, the organizational-domain BIMI record can be used. If you publish a specific record at default._bimi.news.example.com, that record controls the news.example.com stream. This fallback is described in the BIMI sender FAQ.
  1. One logo: Publish at the organizational domain when all subdomains should use the same mark.
  2. Different logo: Publish a separate subdomain BIMI record when that sending stream needs a different mark.
  3. DMARC policy: Use enforced policy for the organizational domain and any explicit subdomain policy. If sp= is absent, the organizational policy applies; an explicit sp=none does not meet BIMI requirements.
  4. Certificate scope: Confirm the certificate and evidence path cover the domains you plan to send from.
Suped's hosted DMARC workflow helps manage policy changes while the team checks subdomain coverage. Review authentication reports for every active sending domain before changing its effective policy.
Hosted DMARC configuration dialog showing policy controls, CNAME setup, and expanded advanced options

Why a valid BIMI logo is not showing

A valid DNS response is only one part of display eligibility. The receiving provider also has to retrieve the files, confirm the message passed DMARC, accept any required evidence document, and decide that the sender meets its local reputation rules. Diagnose each layer separately instead of repeatedly changing the TXT record.
  1. Check discovery: Confirm the selector and visible From domain lead to one valid BIMI TXT record. Allow for the DNS TTL and provider caching; there is no universal 48-hour display deadline.
  2. Check retrieval: Open the SVG or PEM URL without authentication, redirects that fail, geographic restrictions, hotlink protection, or blocked user agents.
  3. Check responses: Use HTTPS, a trusted TLS chain, the correct content type, and a direct successful response for each hosted file.
  4. Check authentication: Inspect a delivered message and confirm that DMARC passed for the visible From domain under an enforced policy.
  5. Check eligibility: Confirm any required certificate is valid and accepted by the provider. Check Yahoo bulk-mail eligibility or La Poste approval as applicable, plus sender reputation.
Send a new message after changes, then test in a fresh web session as well as the relevant mobile client because cached logos and interface differences can hide a successful change. Keep DNS validity and visual display as separate results: a record can pass technical validation while the provider still withholds the logo under its own policy.

How to test self-asserted BIMI

A certificate-free pilot needs a measurement plan before DNS changes. Otherwise the result becomes a vague claim that BIMI helped or did not help. Build the test around mailbox-provider segments, not one blended audience average.
  1. Baseline: Measure normal engagement by receiving mailbox provider. Record Apple Mail as a client separately, because it can read mail from different providers.
  2. Readiness: Confirm enforced DMARC, stable pass rates, known senders, and no hidden failing stream.
  3. Publish: Add the BIMI TXT record and host the SVG over HTTPS on a reliable public path.
  4. Validate: Inspect fresh messages in each target provider and client. For Yahoo and AOL, test an eligible bulk stream; for La Poste, complete the approval process.
  5. Report: Compare provider-specific clicks, replies, conversions, complaints, and unsubscribes.
Open rates are a weak signal because client privacy behavior and image handling distort them. BIMI logos can still influence recognition, but anchor the business case in downstream behavior. Compare matched audiences under similar sending conditions and record whether the logo actually appeared. An inconclusive result does not establish an engagement benefit or failure; a lift at certificate-free providers does not establish the same lift in Gmail or Apple Mail.
For ROI, separate the visible-logo value from the authentication value. Track incremental clicks, conversions, replies, complaint reduction, abuse tickets, and time saved on authentication investigations. Then subtract certificate, logo-preparation, DNS, monitoring, and internal labor costs before presenting the business case.
Where Suped fits
Suped is our DMARC reporting and email authentication product. Use its reports to check sender coverage before enforcement, then monitor DMARC failures during the BIMI pilot. Blocklist (blacklist) monitoring supports separate reputation investigations; a clean result does not establish BIMI display eligibility.
  1. Before BIMI: Find authentication gaps before enforcement or provider testing.
  2. During pilot: Watch pass rates by source so a new sender does not break display.
  3. After launch: Use alerts and issue workflows to keep BIMI prerequisites intact.
Separate Apple-specific brand work from BIMI. Branded Mail in Apple Business is a separate approval program for showing a logo in Apple's ecosystem. It does not make Gmail render BIMI without a VMC or CMC, and it does not change Microsoft receiving support. For Microsoft-specific expectations, check Outlook BIMI support before including Outlook audiences in the ROI model.

Frequently asked questions

Yes. Yahoo Mail and AOL, Fastmail, and approved La Poste domains support certificate-free BIMI. Gmail also supports BIMI without a VMC if you use a CMC, but it does not accept self-asserted BIMI. Apple Mail requires accepted evidence and a compatible receiving provider.

Yes, with a CMC. Gmail requires a VMC or CMC for logo display and does not accept self-asserted BIMI. Only the VMC route qualifies for the Gmail verification checkmark.

Receivers can fall back to the organizational-domain BIMI record when the sending subdomain has no specific record. A subdomain record takes precedence. Test each visible From domain and confirm enforcement at the organizational domain and applicable subdomain policies.

BIMI itself is not a placement shortcut. The authentication work required for BIMI helps domain protection, and the visible logo can improve recognition where providers display it.

Check the visible From domain, selector, DMARC result, SVG or PEM retrieval, TLS chain, content type, certificate validity, and provider eligibility. Yahoo requires eligible bulk mail; La Poste requires approval for self-asserted BIMI. Allow for DNS TTLs and provider caching, then send a new test message. There is no universal display deadline.

Measure by receiving mailbox provider and record the email client separately. Use clicks, replies, conversions, complaints, unsubscribes, abuse reports, and authentication issue workload. Do not rely on blended open-rate changes across all providers.
DMARC monitoring

Start monitoring your DMARC reports today

Suped DMARC platform dashboard
What you'll get with Suped
Real-time DMARC report monitoring and analysis
Automated alerts for authentication failures
Clear recommendations to improve email deliverability
Protection against phishing and domain spoofing