Set Up a BIMI Record: Get Your Logo in Gmail & Yahoo Inbox

You've probably noticed some emails showing a little logo next to the sender name in Gmail or Yahoo Mail, while yours just shows a plain gray circle with an initial. That's not random — it's a DNS record called BIMI, and once your domain has proper DMARC enforcement in place, it's a fairly quick add. Here's how to set it up on a domain hosted with SkyServer, what trips people up, and why some accounts still don't show the logo even after everything looks right.

What BIMI Actually Does

BIMI stands for Brand Indicators for Message Identification. It's a DNS TXT record that points to your logo (as an SVG file) and, for some inbox providers, a certificate that proves you own the trademark on that logo. When it's set up correctly and your mail passes DMARC checks, Gmail and Yahoo will show your logo as the avatar next to your messages instead of a generic letter circle.

It doesn't improve deliverability by itself and it isn't an authentication mechanism — SPF, DKIM, and DMARC still do that job. BIMI is purely a visual trust signal that sits on top of an already-healthy DMARC setup. If your DMARC isn't enforcing yet, fix that first; BIMI won't work around it.

Symptom: You Added a BIMI Record and Nothing Changed

This is the most common support ticket we see on this topic. The customer adds a default._bimi TXT record, waits a day, sends a test email to a Gmail address, and the logo still doesn't appear. Nine times out of ten it comes down to one of these:

• DMARC policy is set to p=none instead of p=quarantine or p=reject
• The logo file isn't a valid, compliant SVG (wrong profile, transparency, or file size)
• Gmail requires a Verified Mark Certificate (VMC) for the checkmark; Yahoo will show a plain SVG-based logo without one
• The BIMI record has a typo in the selector or is on the wrong subdomain
• The mailbox provider is just slow to pick it up — this can genuinely take a few days

Cause: Why the Prerequisites Matter

Inbox providers only trust a logo claim if they can already trust the sender. That trust comes from DMARC being at enforcement, meaning your domain publishes a policy that actually rejects or quarantines mail that fails SPF/DKIM alignment — not just monitors it. If you're still sitting at p=none because you're worried about breaking legitimate mail flows, that's a reasonable caution, but it also means BIMI is off the table until you move past it.

On the certificate side: Gmail added a requirement a while back that logos come with a Verified Mark Certificate from an authorized certificate authority (DigiCert and Entrust both issue these) if you want the blue checkmark next to the logo. Without a VMC, Gmail generally won't display the image at all for most senders, even though the BIMI spec technically allows a self-asserted logo. Yahoo is more lenient and will often show the plain SVG without a VMC. This is the single biggest reason people set everything up and see it work in Yahoo but not Gmail.

Fix: Step-by-Step Setup

1. Confirm DMARC Is at Enforcement

Check your existing DMARC record in the cPanel > Zone Editor, or via a quick lookup:

dig TXT _dmarc.yourdomain.com +short

You want to see something like:

v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@yourdomain.com; pct=100

p=none will not qualify for BIMI on Gmail or Yahoo. If you're still on p=none, work through alignment issues first (see our DMARC enforcement guide) and only move to BIMI once you've run at enforcement for a couple of weeks without a spike in rejected legitimate mail.

2. Prepare a Compliant SVG Logo

Your logo file needs to follow the SVG Tiny Portable/Secure (SVG P/S) profile, not a regular SVG export from Illustrator or Figma. Requirements that trip people up most:

• Square canvas, ideally 1:1 aspect ratio, logo centered
• No scripts, no external references, no raster images embedded — pure vector paths only
• A solid background color (transparent backgrounds get rejected or rendered oddly)
• File size under roughly 32KB

There are free BIMI SVG conversion tools online that will validate the file against the P/S profile before you publish it. Don't skip validation — a logo that looks fine in a browser can still fail the strict profile check that mailbox providers run.

Host the SVG somewhere with a stable HTTPS URL that won't move — a subfolder on your main site, e.g. https://yourdomain.com/assets/logo.svg, works fine on standard cPanel hosting.

3. Publish the BIMI TXT Record

In cPanel, go to Domains > Zone Editor, select the domain, and add a TXT record:

The l= tag points to your SVG. The a= tag, only needed if you've purchased a VMC, points to the certificate chain file. If you don't have a VMC yet, just omit the a= tag entirely — don't leave it pointing at a blank file.

4. Verify the Record Resolves Correctly

dig TXT default._bimi.yourdomain.com +short

You should get your BIMI string back, quoted, with no line breaks. If you see nothing, double-check you added it under the right domain in Zone Editor (addon domains and subdomains have their own zones) and that you didn't accidentally add it as a CNAME or under the wrong host label.

5. Get a VMC If You Want the Gmail Checkmark

If your logo is a registered trademark, you can purchase a Verified Mark Certificate from DigiCert or Entrust. This is a paid, manual process that involves proving trademark ownership, and it typically takes a few business days to issue. Without it, expect Yahoo to display your logo and Gmail to mostly ignore it for now — Gmail's policy on this has shifted before and may shift again, so don't take today's exact behavior as permanent.

Prevention: Keep It Working

• Never let your DMARC policy slide back to p=none once BIMI is live — that silently breaks logo display along with your authentication posture.
• Keep the logo file at a stable URL. If you redesign your site and the assets folder moves, the BIMI record breaks with no error message anywhere — it just quietly stops showing.
• Renew your VMC before it expires if you bought one; there's no grace period notification from Gmail, the checkmark just disappears.
• If you send from multiple subdomains (e.g. marketing.yourdomain.com), each one needs its own default._bimi record and ideally its own DMARC alignment check.

Frequently Asked Questions

Do I need a VMC to use BIMI at all?

No. A VMC is only required for Gmail's blue checkmark treatment on the logo. Yahoo and some other providers will display a plain BIMI logo without any certificate. It's a nice-to-have for Gmail specifically, not a hard requirement of the BIMI standard itself.

Why does my logo show in Yahoo but not Gmail?

This is almost always the missing VMC. Gmail's current policy generally withholds the logo display for senders without a Verified Mark Certificate, even if the BIMI record and SVG are otherwise perfect.

Can I set up BIMI if my DMARC policy is p=none?

Not reliably. Major providers require DMARC at p=quarantine or p=reject with a reasonably high pct value before they'll trust the BIMI logo claim. Get DMARC to enforcement first, run it clean for a couple of weeks, then add BIMI.

How long does it take after publishing the record to see the logo?

DNS propagation itself is usually fast, but mailbox providers cache and re-check BIMI records on their own schedule, which can take anywhere from a few hours to several days. If it's been over a week and everything above checks out, validate your SVG file again — a subtly non-compliant file is the most common silent failure.

Does BIMI cost anything to set up?

The DNS record and SVG logo are free. The only cost is the optional Verified Mark Certificate from an authorized CA, which is a paid annual certificate similar in spirit to a regular SSL cert but for trademark verification instead of domain ownership.