No Version in Record

What Does “No Version in Record” Mean?

“No version in record” means the checker found that the BIMI record is missing its v= version tag. The BIMI draft requires v=BIMI1 to be first and says records without the current version are discarded. Brand Indicators for Message Identification draft 14 documents the controlling requirement or boundary.

The candidate is ignored during assertion-record discovery. The syntax result is deterministic, while final display remains receiver policy.

Why Does No Version in Record Appear?

No version in record appears when the version tag is absent; separately, the protocol also discards candidates whose version has the wrong value or is not the first tag. The exact diagnostic should be read at the scope of BIMI Assertion Record rather than as proof that every BIMI layer failed.

How Do You Fix No Version in Record?

To fix No version in record, place v=BIMI1 as the first tag and preserve valid separators and required fields.

Correcting the version does not repair other tag, DNS, DMARC, asset, or evidence failures.

What Should You Verify After Fixing No Version in Record?

After fixing No version in record, query the exact selector name and confirm that only the intended versioned record remains. Verification should use the exact public selector, URL, record, or file evaluated by the receiver.

The correction clears only this condition; it does not guarantee that a receiver will display an indicator.

Key Takeaways

• The affected object is BIMI Assertion Record.
• The direct correction is to place v=BIMI1 as the first tag and preserve valid separators and required fields.
• Correcting the version does not repair other tag, DNS, DMARC, asset, or evidence failures.