BIMI logo does not look like an SVG
The BIMI record for `your domain` points to your logo URL, which fetched successfully but its content does not look like an SVG image — BIMI requires the logo be an SVG Tiny P/S file.
Why it matters
The BIMI record for `your domain` points to your logo URL, which fetched successfully but its content does not look like an SVG image — BIMI requires the logo be an SVG Tiny P/S file. Mailbox providers that fetch this URL and cannot parse it as the required SVG profile will simply not display a logo. This checks for a plausible SVG only (an <svg> tag or an SVG content-type), not full compliance with the Tiny P/S profile BIMI requires, which needs a dedicated validator.
How ShipReady detects it
Email-authentication DNS records (DMARC / SPF). Almost every AI-built SaaS sends transactional email — password resets, magic links, receipts — through Resend, SendGrid or Postmark. Setting that up gets the mail delivered; it does not stop anyone else sending mail that claims to come from the same domain. Without a DMARC policy, a receiving server has no instruction to reject a forgery, so an attacker can send "reset your password" from the product's own domain and the message will land in the inbox looking authentic. This check is almost entirely DNS rather than HTTP — one exception is MTA-STS, whose policy is only half-published in DNS; the other half is a file fetched over HTTPS (see _check_mta_sts). Nearly everything else here is the most deterministic kind of check the scanner has: a record either exists or it does not, so there is no heuristic and no false-positive surface. The one place judgement is required is deciding WHICH domain to ask about — see _organizational_domain.
Detection is deterministic. ShipReady reports this only when it observes the condition directly, and prefers to miss a real problem over inventing one. Rule version 1.10.0.
How to fix it
This is the prompt ShipReady puts in your report — written to be pasted straight into Cursor, Claude Code, or whichever assistant built the app.
The BIMI record at default._bimi.your domain points to your logo URL, which loads but doesn't look like an SVG image. BIMI requires the logo be an SVG Tiny P/S file specifically — not a PNG, JPEG, or a regular SVG using features outside that restricted profile. Export your logo as SVG Tiny P/S (most brand/logo generators aimed at BIMI produce this automatically — verify with a BIMI logo validator such as bimigroup.org's), serve it at your logo URL with an image/svg+xml content-type, and confirm the file starts with an <svg> element.
Frequently asked questions
- What does "BIMI logo does not look like an SVG" mean?
- The BIMI record for `your domain` points to your logo URL, which fetched successfully but its content does not look like an SVG image — BIMI requires the logo be an SVG Tiny P/S file.
- How serious is it?
- ShipReady rates this low. Worth fixing. Small individually, and they accumulate.
- How do I fix it?
- Paste the fix prompt on this page into Cursor, Claude Code or your AI editor. It is the same prompt ShipReady puts in your report.
- Can I check my own site?
- Yes — ShipReady scans up to ten pages of any public site for free and reports this alongside every other check. The free report lists every issue it finds and shows full evidence and a fix prompt for the critical and high-severity ones; medium and low findings are counted and unlock on Pro.
Related checks
Run this check on your site
ShipReady checks this and 193 other things across up to ten pages of your site, with an AI-ready fix for each. Free, no signup.