BIMI logo URL returned a completed failure response
ShipReady made one bounded request to the HTTPS logo URL in the selected BIMI record and observed a completed HTTP failure or a connection failure with a receiver-relevant cause.
Why it matters
A published BIMI record can refer to a logo URL that needs operational review. This finding records the scanner's single request result; it does not establish what every recipient or mailbox provider experiences.
How ShipReady detects it
What it inspects
After a qualifying BIMI record supplies an HTTPS l= URL, ShipReady makes one 10-second bounded HTTP request for that URL.
What triggers a finding
The rule triggers for a completed non-200 response, or for a request failure whose causal chain proves connection refusal, TLS certificate verification failure, or DNS nonexistence. Timeouts, scanner-side failures, response refusals such as 429/503, and other inconclusive errors suppress the finding.
What the evidence shows
ShipReady's bounded request to the selected URL received the reported completed failure result.
Limits of this check
ShipReady does not prove that every mailbox provider cannot retrieve the URL, whether a recipient displayed a logo, whether a redirect or later deployment state works, or whether the logo satisfies BIMI requirements.
How to fix it
Inspect the exact published URL
Request the l= URL from an independent environment and review its DNS, TLS certificate, HTTP status, and access controls.
Repair the serving path if needed
Correct the logo host or BIMI record only after identifying why the published URL produced the observed result.
How to verify the change
Recheck the deployed URL
After the repair, request the exact HTTPS l= URL and inspect the response.
Expected: The URL returns the intended logo response in your verification environment.