No qualifying BIMI record observed after enforcing DMARC
ShipReady found an enforcing DMARC policy but no TXT record beginning with v=BIMI1 at default._bimi for the organisational domain.
Why it matters
BIMI is an optional brand-identification mechanism. This finding helps an owner decide whether adding it is worthwhile after email authentication is already configured; it is not a security failure.
How ShipReady detects it
What it inspects
ShipReady uses the selected DMARC policy and queries the TXT records at default._bimi for the organisational domain.
What triggers a finding
The rule triggers only when the selected DMARC policy is quarantine or reject, the BIMI lookup completes, and no TXT value begins with v=BIMI1. Missing or non-enforcing DMARC and an unanswered DNS lookup suppress the finding.
What the evidence shows
No qualifying BIMI TXT record was observed at the supported default location after ShipReady observed an enforcing DMARC policy.
Limits of this check
ShipReady does not validate a complete BIMI deployment, inspect a logo, determine certificate requirements, send email, or establish whether any mailbox provider will display a logo.
How to fix it
Decide whether BIMI is useful for the domain
Treat BIMI as an optional brand and trust feature, rather than a replacement for DMARC, SPF, or DKIM.
Follow the BIMI requirements that apply
If you choose to deploy BIMI, use the applicable provider and BIMI guidance to prepare the logo, record, and any certificate requirements.
How to verify the change
Verify the published BIMI record
Query default._bimi for the organisational domain after DNS propagation and inspect the intended record.
Expected: A qualifying BIMI TXT record is present when BIMI is deliberately deployed.