Tool guideEmail Tools

BIMI Checker – Complete Guide to BIMI Records, SVG Logos and VMC/CMC Certificates

What Brand Indicators for Message Identification need, how the NetTools.tech BIMI Checker validates the record, DMARC, logo and mark certificate, and how to fix each problem.

By NetTools.tech · · 6 min read

Your DMARC policy is at reject, the logo is uploaded and the TXT record is published — and still no logo appears next to your messages in Gmail. BIMI has several independent requirements, and one failing part is enough to hide the logo: a quarantine policy at pct=50, an SVG exported with x and y attributes, an expired certificate, or a logo file that differs by a single byte from the one inside the certificate.

The BIMI Checker checks every part in one run — the BIMI record, DMARC enforcement, SVG Tiny PS compliance, the VMC or CMC certificate with its trust chain and revocation status, and whether the certificate's embedded logo matches the published one — and explains what to fix.

What is BIMI?

In simple terms

Brand Indicators for Message Identification (BIMI) lets a domain owner publish a logo that participating mailbox providers show next to authenticated messages. It rewards strong email authentication: only domains that enforce DMARC qualify.

Technical background

The domain publishes a TXT record at default._bimi.example.com with v=BIMI1, a logo URL (l=) and optionally an authority evidence URL (a=) pointing to a PEM file with a mark certificate. The logo must use the SVG Tiny PS profile. The certificate — a Verified Mark Certificate (VMC) or Common Mark Certificate (CMC) — is an X.509 certificate with a BIMI extended key usage that embeds the verified logo in an RFC 9399 logotype extension.

Why use a BIMI checker?

Mailbox providers rarely explain why a logo is not shown. A checker turns the hidden requirements into explicit pass/fail results with evidence, so you can fix the record, the policy, the SVG or the certificate before a campaign — and confirm that a renewal or logo update did not break anything.

Who should use it?

Email administrators setting up BIMI, marketing teams preparing a brand launch, agencies managing several senders, and anyone renewing a VMC or CMC. It is also useful before buying a certificate: the DMARC and SVG checks show whether the domain is ready.

How the BIMI checker works

The NetTools server reads the BIMI TXT record at <selector>._bimi.<domain> (falling back to the parent domain, as BIMI allows) and the DMARC records of the domain and its organizational domain. It downloads the logo and the certificate through an SSRF-protected fetcher, validates the SVG as data without rendering it, and parses the certificate with OpenSSL. It verifies every signature in the chain, checks that the chain ends at a Mark root CA confirmed from the CA's official repository, checks the signed revocation list, and compares the logo embedded in the certificate with the published SVG. Related checks: DMARC Lookup and the Email Deliverability Checker.

How to use the NetTools.tech BIMI Checker

  1. Open the BIMI Checker and enter your domain — an email address or URL works too.
  2. If you use a selector other than default, set it under Advanced settings.
  3. To validate a record before publishing it, paste it into Test a BIMI record instead of DNS.
  4. Click Check BIMI and follow the progress list.
  5. Read the four status cards, then open the sections for details and the findings for fixes. Export the result as PDF, CSV or JSON, or print it.

Understanding the results

The overall status is VALID (all parts pass), WARNING (works, but something needs attention — for example a self-asserted record without a certificate), INVALID (a required part fails), NOT CONFIGURED (no record), DECLINED (empty l=) or UNABLE TO VERIFY (DNS or a server did not answer — not a verdict).

The certificate section verifies each step separately: the URL answers, the file is PEM, the PEM is X.509, the certificate is a mark certificate (VMC or CMC, determined from its mark-type attribute and policy), and the chain is trusted, valid and not revoked. Revocation is reported as unknown — never as revoked — when the revocation list cannot be checked. The embedded logo section shows both logos side by side as images and the hash check.

Example: a logo that does not match the certificate

A brand refreshed its logo colours and replaced logo.svg on its web server. The checker reports INVALID with a CRITICAL finding: the published SVG differs from the logo embedded in the VMC. The certificate is still valid and trusted, but receivers only show the logo the CA verified. The fix is to republish the original SVG — or, for the new design, obtain a new certificate with the new logo and publish both together.

Common use cases

  • Verifying a new BIMI setup end to end before announcing it.
  • Checking after a DMARC change that the policy still meets the BIMI requirement.
  • Monitoring certificate expiry and revocation ahead of renewal.
  • Converting a design-tool SVG to SVG Tiny PS and confirming the result.
  • Checking subdomains that inherit the organizational domain's record and policy.

Troubleshooting

"DMARC policy is none" or "percentage below 100 %"

Move to p=quarantine without a pct tag (or pct=100), or to p=reject, after your DMARC reports show that legitimate mail passes.

"Logo does not comply with SVG Tiny PS"

Set version="1.2" baseProfile="tiny-ps" on the root, add a <title>, remove x/y from <svg>, and remove scripts, <image>, links, animation, filters and <style>.

"Certificate is not trusted"

The chain does not end at a Mark root CA. Publish the PEM bundle exactly as issued by your Mark Verifying Authority, with the intermediate certificate after the leaf.

Download the SVG from your CA's portal and publish it unchanged at the l= URL.

UNABLE TO VERIFY

DNS or the logo or certificate server did not answer in time. Check that the URLs are reachable over HTTPS and run the check again.

Common mistakes

  • Publishing pct=50 with p=quarantine, or sp=none.
  • Exporting the logo from a design tool without converting it to SVG Tiny PS.
  • Serving the logo or certificate over HTTP, or through redirects that leave HTTPS.
  • Editing the published SVG after the certificate was issued.
  • Publishing two BIMI TXT records at the same name.

Limitations

The checker examines the published configuration; it cannot see whether individual messages pass DMARC or whether a mailbox provider's own reputation rules apply. The organizational domain is approximated by walking up parent domains. Only Mark root CAs whose fingerprints were confirmed from the CA's official repository are trusted (DigiCert, GlobalSign and SSL.com); certificates from other roots are reported as not recognised. Revocation is checked through the certificate's CRL; OCSP is not used.

Security & privacy

Only public addresses are contacted: every redirect is re-checked, downloads are size-limited (128 KB logo, 256 KB certificate, 4 MB CRL) and time-limited. The SVG is parsed as data — DTDs and entities are refused, nothing is executed — and previews are displayed as images, which browsers render without scripts or external requests. Results are kept in memory for 15 minutes and are not stored.

Summary

BIMI only works when the record, DMARC enforcement, an SVG Tiny PS logo and — for the major mailbox providers — a trusted VMC or CMC with the identical embedded logo all line up. The NetTools.tech BIMI Checker verifies each of them with real data, explains every failure and tells you exactly what to change.

Frequently asked questions

What do I need for BIMI?

A DMARC policy at enforcement on your domain and organizational domain (p=quarantine at 100 % or p=reject), an SVG Tiny PS logo published over HTTPS, a BIMI TXT record pointing to it, and for Gmail and Apple Mail a Verified Mark Certificate or Common Mark Certificate.

What is the difference between a VMC and a CMC?

A VMC verifies a registered trademark or government mark. A CMC verifies a logo protected by prior use or a modified registered mark. Mailbox providers treat them differently; Gmail accepts both and describes its verified checkmark for VMCs.

Why does p=none not work with BIMI?

p=none only monitors: mail that fails DMARC is still delivered, so anyone could send mail that shows your logo. BIMI therefore requires quarantine applied to 100 % of mail, or reject.

My logo is a valid SVG. Why does the checker reject it?

BIMI requires the SVG Tiny Portable/Secure profile: version 1.2, baseProfile tiny-ps, a title, and no scripts, images, links, animation, filters, CSS style elements or external references. Most design tools export ordinary SVG, which needs converting.

What does an empty l= mean?

v=BIMI1; l=; is a deliberate declination: the domain asks receivers not to show any logo. A missing record simply means BIMI is not configured.

Does a valid result guarantee that Gmail shows my logo?

No. The checker validates the published configuration. Each message must also pass DMARC, and mailbox providers apply their own sender reputation and volume requirements.

Why must the published SVG match the certificate?

A mark certificate embeds the exact logo the CA verified. Receivers compare it with the SVG at the l= URL and only show the logo when they are the same file, so edit neither after issuance.