BIMI Checker: the question this tool answers
Check the default BIMI DNS location and explain whether a logo location and authority evidence are published. The live result starts with default._bimi TXT, then uses l tag and a tag to confirm or challenge the first interpretation. A healthy result here is intentionally scoped to business-email DNS and mail authentication; it does not claim that unrelated parts of the domain are healthy.
- default._bimi TXT
- l tag
- a tag
- record syntax
How to read the default._bimi TXT, l tag and a tag evidence
Start with the value that directly controls the failing service, then use the other signals to confirm or challenge that interpretation. A single record or response can look correct while another hostname, IP family, redirect or mail-authentication path still fails. The tool therefore keeps the raw observed value visible and explains how the signals relate.
- Default._bimi TXT — Verify default._bimi TXT from the public Internet and compare it with the value the responsible provider says should be live.
- L tag — Verify l tag from the public Internet and compare it with the value the responsible provider says should be live.
- A tag — Verify a tag from the public Internet and compare it with the value the responsible provider says should be live.
- Record syntax — Verify record syntax from the public Internet and compare it with the value the responsible provider says should be live.
Common bimi checker failure patterns
The most useful warnings are mismatches rather than isolated missing fields. Default._bimi TXT can be absent or stale; l tag can point somewhere different from the expected provider; and a tag can reveal a second path that behaves differently. If public sources disagree, first decide whether the difference comes from authoritative data, caching, a separate hostname, IPv6, or another protocol layer before editing configuration.
What to change — and what not to change
Change the smallest setting that the evidence proves is wrong. Compare the observed default._bimi TXT with the current value supplied by the responsible provider, save the existing value, make one correction, and retest. Do not replace nameservers, delete unrelated MX/TXT records, disable TLS controls or remove IPv6 simply because BIMI Checker shows a warning in another layer. Broad changes can turn one isolated problem into several independent outages.
How HostWithShery runs BIMI Checker
The submitted public input is normalized and validated before any server-side request is made. HostWithShery then obtains default._bimi TXT and l tag using the appropriate public DNS, HTTP, TLS or mail protocol and adds a tag plus record syntax where it materially changes the interpretation. URL-based checks are restricted to public destinations, and redirect targets are revalidated instead of being trusted automatically.
How to interpret conflicting bimi checker signals
When default._bimi TXT looks correct but l tag or a tag disagrees, do not treat the whole domain as broken. Isolate the public path that differs, identify whether it belongs to business-email DNS and mail authentication, and verify that path against the authoritative provider value before making a change. HostWithShery keeps these signals separate so a healthy value in one layer cannot mask a failure in another.
When a bimi checker result is inconclusive
This is a public-configuration diagnostic. Network filtering, private control-panel settings, split-horizon DNS, provider-internal state and transient routing conditions can limit what can be confirmed from outside the account. Public diagnostics cannot see private control-panel state, unpublished origin addresses, provider account status or split-horizon/internal DNS. If the remote service times out, blocks automated requests or hides a signal, the result stays inconclusive instead of inventing a provider or configuration. That distinction matters when the next step is a potentially disruptive DNS, SSL or mail change.
How to verify the repair
The public MX/authentication records should match the intended mail provider, required hostnames should resolve, and the relevant SPF/DKIM/DMARC check should no longer show the original failure. Repeat BIMI Checker after the change and compare the same default._bimi TXT, l tag and a tag evidence that exposed the problem. A provider dashboard saying “saved” is not enough when the public Internet still returns the old value.
What to check next if BIMI Checker is healthy
If default._bimi TXT, l tag and a tag now agree but the user-facing problem remains, move to the adjacent layer instead of editing the same setting repeatedly. Use the related diagnostics on this page to test the next plausible cause, and keep the previous result as evidence when escalating to a hosting, DNS or email provider.
Technical references
These primary standards and provider documents are used to verify the behavior described on this page. Provider dashboards can change, so use the current official value for tenant-specific DNS records rather than copying an example from another account.