bonus.bimi.logo_unreachable
BIMI Logo Not Reachable
What we check
We fetch the l= logo URL from the BIMI record over HTTPS. Supporting clients must retrieve this logo to display it; if the URL doesn't return a successful response, the logo can never appear.
What this finding means
The BIMI record names a logo URL, but we couldn't fetch it — the HTTPS request failed, timed out, returned an error status, or the host is unreachable. A logo that can't be retrieved is a logo that never shows, no matter how correct the rest of your BIMI and DMARC setup is.
Common causes: the file was moved or deleted, the HTTPS certificate is invalid, the URL is HTTP rather than HTTPS, or the hosting is down or blocking automated fetches.
Why it matters
- The logo never displays. Clients fetch the SVG live; a failed fetch means no logo at any provider, so your BIMI investment delivers nothing.
- Silent from your side. The DNS record looks fine — the failure is one layer down, at the URL it points to, which is easy to overlook.
How to fix
Confirm the URL loads over HTTPS with a valid certificate and a success status:
curl -sI https://example.com/logo.svg # expect: HTTP/2 200, Content-Type: image/svg+xmlFix what's broken: restore a moved or deleted file, repair the HTTPS certificate, switch an
http://URL tohttps://, and make sure the host doesn't block automated clients.Use a stable URL. Host the logo somewhere durable so the link doesn't break on the next site change.
How it's graded
An unreachable BIMI logo 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 404
Logo fetch failed — clients cannot retrieve the logo