BIMI logo lookup

Check HTTP delivery, weight and Tiny-PS compliance in seconds

Paste the URL exposed in your BIMI record to validate the SVG asset without leaving the browser. CaptainDNS proxies the download, measures latency, records redirects and runs the Tiny-PS checks used by the backend resolver.

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.
  1. Copy the l= URL from your BIMI TXT record and launch the lookup.
  2. Export the JSON response to keep an audit trail with your change request.
  3. Fix blocking errors first (invalid HTTPS endpoint, missing Tiny-PS requirements, parsing failures).
  4. Address warnings: simplify redirect chains, reduce the file size, document the final CDN location.
  5. 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.