BIMI logo

This check fetches the SVG the BIMI record's l= tag points at and grades the two things that make a logo silently not appear in Gmail when the record and the certificate are both fine. Nothing about it is visible from DNS, and the failure mode is a record that parses, a logo URL that loads, and no logo in anyone's inbox.

The first is the SVG Tiny Portable/Secure profile. Gmail requires the root <svg> to declare version="1.2" and baseProfile="tiny-ps", a <title> element naming the brand, no x or y on the root, a square aspect ratio, and nothing that scripts, animates, embeds an image or refers outside the document. Each problem found is named.

The second is the mark certificate. A Verified Mark or Common Mark Certificate embeds the exact logo it was issued for, with a hash of it, and the file served at l= has to be that same file. Editing or re-exporting the SVG after the certificate was issued — even a change no one can see — breaks the match. Where the record has an a= tag, the logo's hash is compared with the certificate's. Without one, only the profile is graded.

The logo itself is not stored, only its size and hashes.

If the logo does not match the certificate, serve the logo embedded in the certificate — your issuer can supply it — or have the certificate reissued for the new logo. A mark certificate cannot follow a changed file.

For profile problems, convert the logo with a tool that produces SVG Tiny P/S rather than editing an ordinary export by hand, then validate it. Set version="1.2" and baseProfile="tiny-ps" on the root, add a <title>, remove x and y from the root, and make the viewBox square.

Change the logo and the certificate together. A logo fixed after the certificate was issued fails the match instead.