Skip to content
Open your domains

Your brand logo in supporting inboxes.

BIMI lets receiving email services find your domain’s brand logo. FranklyMail can host your logo and public mark certificate, generate the DNS record and check your setup. Each receiving service decides whether a logo appears.

Before you start

You need control of your domain’s DNS, an SVG Tiny PS logo, and an enforced DMARC policy covering all your mail. Gmail also requires a Verified Mark Certificate (VMC) or Common Mark Certificate (CMC) from an external issuer. Certificates may cost extra; FranklyMail does not issue them. A VMC can qualify for Gmail’s verified checkmark; a CMC does not give that checkmark.

Your DMARC policy must use quarantine or reject, with pct=100 if that tag is present, and without testing mode. The organizational domain and applicable subdomain policies must be enforced. Check all legitimate sending services before changing DMARC. We do not change this policy for you.

Set up your domain

  1. Open Domains, choose your domain and find Brand appearance (BIMI). Verify domain ownership with DKIM first if prompted.
  2. Upload your logo as an SVG Tiny PS file, up to 32 KB, or select Convert a PNG, JPG or WebP logo for an image up to 5 MB. Conversion runs in your browser and produces a square SVG on a white background. Review the preview, confirm it represents your logo, then use or download the result. Fine details and colors may change. Use the converted SVG for your certificate application; never convert an already-certified logo. Use version 1.2, baseProfile tiny-ps, a title with your organization’s name, and square absolute dimensions of at least 96 pixels. Convert text to outlines. Our conservative validator accepts static shapes and gradients; it rejects CSS styles, embedded images, scripts, animations and external references. Use presentation attributes for colors and strokes.
  3. For Gmail, obtain a VMC or CMC covering this domain and your logo. Upload the public PEM certificate chain from your issuer, up to 64 KB. Never upload a private key. Saving publishes the files at stable HTTPS URLs, served directly from Backblaze B2. Each file keeps its URL until replaced or removed.
  4. Add the generated TXT record at default._bimi with your DNS provider. If a BIMI record already exists at that name, replace it instead of adding a second. We do not add it automatically through Domain Connect.
  5. Select Check BIMI setup. Fix the issues shown and check again after DNS has propagated. Send a test email and inspect its authentication results to confirm that the message itself passes aligned DMARC.

What passing checks means

The checker reads public DNS, compares the published BIMI record with your saved settings, inspects SPF and DKIM records, and checks DMARC enforcement. For uploaded certificates, it checks the file format, mark-certificate purpose, domain coverage, validity dates and signatures between supplied chain entries.

It does not establish certificate issuer trust, check revocation, compare the certificate’s embedded logo with your SVG, or authenticate a sent message. Your certificate issuer and receiving email service perform those checks. DNS and file checks alone cannot guarantee inbox placement or logo display. This feature does not change your personal avatar or email signature.

Replace or remove your logo

Upload a replacement and save. A replacement file gets a new HTTPS URL. Update the BIMI TXT record within seven days, before the previous file is removed. Receivers may cache old files. A different logo may need a new certificate. Renew expiring certificates through your issuer and upload the new chain here.

To stop using BIMI, remove its TXT record first, then remove the brand files from the domain page. Public files are queued for removal within an hour. Removing a certificate changes the generated TXT value, so update DNS too. BIMI is optional: removing it does not disable mail delivery.

Provider requirements can change. See Google’s BIMI requirements and the BIMI Group implementation guide.