BIMI Logo Not Showing: Every Rejection Reason and Fix

BIMI Display Requirements

For a BIMI logo to display, everything must be in place:

1. DMARC policy at p=quarantine or p=reject (not p=none)
2. BIMI DNS record published correctly
3. SVG logo in Tiny PS format, accessible via HTTPS
4. VMC certificate (required by Gmail, optional elsewhere)
5. Mailbox provider that supports BIMI

If any piece is missing, no logo.

Checking Your BIMI Setup

Step 1: Verify DMARC Policy

dig TXT _dmarc.yourdomain.com +short

Look for p=quarantine or p=reject. If you see p=none, BIMI won't work.

Step 2: Check BIMI DNS Record

dig TXT default._bimi.yourdomain.com +short

You should see something like:

"v=BIMI1; l=https://yourdomain.com/logo.svg; a=https://yourdomain.com/vmc.pem"

Step 3: Test Logo URL

curl -I https://yourdomain.com/logo.svg

Check for:

• HTTP 200 response
• Content-Type: image/svg+xml
• HTTPS (not HTTP)

Step 4: Validate with BIMI Inspector

Use bimigroup.org/bimi-generator/ to test your setup.

Common Failures and Fixes

Problem 1: DMARC Not at Enforcement

Symptom: Everything looks correct but logo doesn't show.

Cause: DMARC is at p=none (monitoring only).

Fix: Advance DMARC to at least p=quarantine:

v=DMARC1; p=quarantine; rua=mailto:[email protected]

Practitioner note: Don't rush to quarantine just for BIMI. If you haven't properly audited your senders, you'll break legitimate email. Follow the DMARC advancement process first.

Problem 2: Missing or Invalid VMC (Gmail)

Symptom: Logo shows in Apple Mail but not Gmail.

Cause: Gmail requires a Verified Mark Certificate (VMC). Other providers are more lenient.

Fix:

1. Purchase a VMC from DigiCert or Entrust (~$1,500/year)
2. VMC requires a registered trademark (USPTO, EUIPO, etc.)
3. Add the VMC URL to your BIMI record: a=https://yourdomain.com/vmc.pem

If you don't have a registered trademark, you can't get a VMC, and Gmail won't show your logo.

Problem 3: SVG Format Not Tiny PS

Symptom: Logo URL loads fine in browser but BIMI rejects it.

Cause: BIMI requires SVG Tiny Portable/Secure, not standard SVG.

What's not allowed in Tiny PS:

• External references
• Scripts
• Animations
• Filters
• Masks
• Clipping paths (complex)
• Embedded images (some restrictions)
• Many CSS properties

Fix:

1. Use a BIMI SVG generator/converter:
   • BIMI Group SVG Converter
   • DigiCert's BIMI tools
2. Manual cleanup:
   • Remove all <script> elements
   • Remove <animate> elements
   • Remove external references
   • Ensure single <svg> root with viewBox
   • Keep file under 32KB

Example Tiny PS structure:

<?xml version="1.0" encoding="UTF-8"?>
<svg version="1.2" baseProfile="tiny-ps" xmlns="http://www.w3.org/2000/svg"
     viewBox="0 0 100 100" width="100" height="100">
  <title>Company Logo</title>
  <circle cx="50" cy="50" r="40" fill="#0066CC"/>
</svg>

Problem 4: DNS Record Syntax Errors

Symptom: DNS query returns no record or malformed data.

Common mistakes:

Error	Correct Format
Missing v=BIMI1	v=BIMI1; l=https://...
Wrong hostname	default._bimi.domain.com not _bimi.domain.com
HTTP instead of HTTPS	l=https://... (must be HTTPS)
Missing semicolons	Separate tags with ;
Quotes inside value	Escape or avoid special characters

Correct record:

Host: default._bimi
Type: TXT
Value: v=BIMI1; l=https://yourdomain.com/bimi/logo.svg; a=https://yourdomain.com/bimi/vmc.pem

Problem 5: Logo URL Not Accessible

Symptom: BIMI validator reports "cannot fetch logo."

Possible causes:

• Server returns 404 or 403
• Firewall blocks external requests
• Content-Type header is wrong
• Mixed content (HTTPS record pointing to HTTP resource)
• Geo-blocking

Fix:

1. Test URL from external location:

curl -I https://yourdomain.com/logo.svg

2. Ensure HTTPS with valid certificate
3. Set proper Content-Type: image/svg+xml
4. Allow access from all IPs (no geo-blocking)

Problem 6: VMC Expired or Revoked

Symptom: Was working, suddenly stopped.

Cause: VMC certificates have expiration dates (usually 1 year).

Fix:

1. Check VMC expiration date
2. Renew with DigiCert or Entrust before expiration
3. Update the certificate file at your a= URL

Problem 7: Trademark Issues

Symptom: VMC application rejected.

Cause: Your trademark doesn't match requirements.

Requirements for VMC:

• Active registered trademark
• Trademark must be for a logo mark (design mark)
• Word marks alone may not qualify
• Trademark must be registered (not just applied for)

Accepted trademark offices:

• USPTO (United States)
• EUIPO (European Union)
• CIPO (Canada)
• UK IPO (United Kingdom)
• And others — check with VMC provider

Problem 8: Provider Doesn't Support BIMI

Symptom: Everything configured correctly but logo doesn't show.

Cause: Not all email clients support BIMI.

BIMI Support (2026):

Provider	Supports BIMI	Requires VMC
Gmail	Yes	Yes
Apple Mail	Yes	No
Yahoo Mail	Yes	No
Fastmail	Yes	No
Outlook	Limited pilot	Yes
Proton Mail	No	N/A

If the recipient's provider doesn't support BIMI, no amount of configuration will help.

Problem 9: Recent Authentication Failures

Symptom: BIMI was working, then stopped.

Cause: Some providers (especially Gmail) may suppress BIMI if they detect authentication failures from your domain.

Fix:

1. Check DMARC reports for failures
2. Verify all senders are properly authenticated
3. Monitor for any spoofing attempts
4. Wait for provider to re-trust your domain

Practitioner note: I've seen Gmail suppress BIMI for domains that had a spike in DMARC failures — even when those failures were from spoofed messages, not legitimate sends. Keep your authentication tight.

BIMI Checklist

• DMARC at p=quarantine or p=reject
• BIMI DNS record at default._bimi.yourdomain.com
• SVG in Tiny PS format
• Logo accessible via HTTPS
• Content-Type: image/svg+xml
• VMC certificate (for Gmail)
• VMC URL in BIMI record (a= tag)
• Logo under 32KB
• Square aspect ratio
• Validated with BIMI Inspector

Testing Workflow

1. Validate DNS: dig TXT default._bimi.yourdomain.com
2. Test logo URL: curl -I https://yourdomain.com/logo.svg
3. Run BIMI Inspector: bimigroup.org tools
4. Send test email: Check headers for BIMI processing
5. Wait 24-48 hours: Allow caching to update
6. Test in supported client: Gmail (with VMC), Apple Mail

If you've checked everything and BIMI still isn't displaying, schedule a consultation — I'll diagnose the specific issue in your setup.

Sources

• BIMI Group: Implementation Guide
• Google: BIMI requirements
• RFC 9495: Brand Indicators for Message Identification (BIMI)
• DigiCert VMC
• Entrust VMC

---

v1.0 · March 2026