What the lookup returns
- HTTP metrics. Observe latency, number of redirects, final URL and reported MIME type to catch fragile hosting or missing HTTPS hardening.
- SVG metadata. Title, viewBox, width/height attributes and additional tags help document the asset and confirm the Tiny-PS profile.
- Diagnostics. Errors stop the logo from rendering. Warnings highlight risky constructs (external references, scripts, oversized files) that mailbox providers may reject.
Recommended workflow
- Copy the
l=URL from your BIMI TXT record and launch the lookup. - Export the JSON response to keep an audit trail with your change request.
- Fix blocking errors first (invalid HTTPS endpoint, missing Tiny-PS requirements, parsing failures).
- Address warnings: simplify redirect chains, reduce the file size, document the final CDN location.
- Re-run the lookup until the status is clean, then publish or update your BIMI record.
Good practices when hosting BIMI logos
- Serve the SVG over HTTPS with a predictable CDN or origin that supports caching and redirects sparingly.
- Keep the file below 32 kB, remove unused metadata and make sure the viewBox matches the intended display.
- Avoid scripts, fonts, foreignObject and external references: they violate Tiny-PS and are blocked by mailbox providers.
- Monitor latency over time; sudden spikes usually signal CDN incidents or expired TLS chains that will prevent the logo from loading.