bonus.bimi.logo_not_svg
BIMI Logo Not Valid SVG
What we check
We fetch the l= logo URL and check its content type and content against the SVG requirement. BIMI mandates an SVG image in the SVG Tiny PS (Portable/Secure) profile; supporting clients reject other formats.
What this finding means
The BIMI logo URL is reachable, but what it returns isn't a valid SVG. The record and the hosting are fine — the image itself is the wrong format. A PNG, JPEG, a full-feature SVG that isn't the Tiny PS profile, or an HTML error page served with a 200 status all land here.
BIMI is strict about this on purpose: the SVG Tiny PS profile is a locked-down subset (no scripts, no external references, defined dimensions) so that a logo can be rendered safely inside a mail client.
Why it matters
- The logo won't display. Clients that support BIMI reject non-conforming images, so a wrong-format logo shows nothing even though everything else is in place.
- Easy to get wrong. Design tools export "SVG" that isn't Tiny PS, or a raster logo gets renamed
.svg. It looks like an SVG until a BIMI-strict client parses it.
How to fix
Produce an SVG Tiny PS version of your logo (a normal SVG export won't do). Several BIMI logo converters and validators exist for exactly this profile.
Serve it with the right content type —
image/svg+xml— at yourl=URL:default._bimi.example.com. IN TXT "v=BIMI1; l=https://example.com/logo.svg; a=https://example.com/vmc.pem"Validate before publishing. Confirm the file conforms to SVG Tiny PS (correct root attributes, no scripts, no external references) and re-scan.
How it's graded
A BIMI logo that isn't a valid SVG costs 5 points in the optional Bonus category. See Grading Methodology for the full scoring model.
Evidence example
BIMI record: "v=BIMI1; l=https://example.com/logo.svg; a=..."
$ curl -sI https://example.com/logo.svg
HTTP/2 200
Content-Type: image/png ← reachable, but not an SVG (must be SVG Tiny PS)