Email Authentication Glossary
Alignment & authentication
BIMImedium

Valid Record, but DMARC Isn't Ready

“Valid record, but DMARC isn't ready” means the BIMI record parses, but the evaluated domain does not meet BIMI's DMARC enforcement boundary. The BIMI draft requires quarantine or reject on both relev

The exact error

Valid record, but DMARC isn't ready

What Does “Valid Record, but DMARC Isn't Ready” Mean?

“Valid record, but DMARC isn't ready” means the BIMI record parses, but the evaluated domain does not meet BIMI's DMARC enforcement boundary. The BIMI draft requires quarantine or reject on both relevant domains; quarantine must apply at an effective 100 percent, meaning an explicit pct must equal 100 while omission uses DMARC's default of 100. Brand Indicators for Message Identification draft 14 documents the controlling requirement or boundary.

BIMI processing must not proceed while the DMARC boundary is unmet. A receiver may use additional authentication to substitute for message-level DMARC pass, but that does not waive p=none, sp=none, or quarantine-percentage restrictions.

Why Does Valid Record, but DMARC Isn't Ready Appear?

Valid record, but DMARC isn't ready appears when the author or organizational-domain policy is p=none, a relevant subdomain policy is sp=none, or a quarantine policy applies to less than the full percentage. The exact diagnostic should be read at the scope of domain authentication eligibility rather than as proof that every BIMI layer failed.

How Do You Fix Valid Record, but DMARC Isn't Ready?

To fix Valid record, but DMARC isn't ready, move the applicable DMARC policies to an enforced setting only after confirming legitimate mail passes aligned SPF or DKIM.

Changing DMARC can affect mail delivery and does not validate the BIMI record or assets.

What Should You Verify After Fixing Valid Record, but DMARC Isn't Ready?

After fixing Valid record, but DMARC isn't ready, send an authenticated test message and verify DMARC pass plus the author and organizational-domain policy values. 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 domain authentication eligibility.
  • The direct correction is to move the applicable DMARC policies to an enforced setting only after confirming legitimate mail passes aligned SPF or DKIM.
  • Changing DMARC can affect mail delivery and does not validate the BIMI record or assets.
Check your BIMI record

See exactly which checks your domain passes and fails.

Email Authentication Glossary