Email.com docsOpen the app

Guides

Domain readiness: the contract for warmup, blacklist and checklists

The DMARC product decides whether a sending domain is authenticated well enough for volume. Other products never re-check DNS themselves: they consume two events and, when they need the current state, read it through the API. This page is the contract they build against (dmarc PLAN section 3.6). The rail-level gate is separate and stays the platform's: domain.verified.v1 (consumed by the send pipeline, which holds a message until its identity is verified). Readiness never blocks a send by itself.

What ready means

A domain is ready when all three gates pass on one check:

Ready does not require an enforcing policy (p=none is ready), BIMI, MTA-STS, TLS-RPT or wired aggregate reports: those are recommendations the panel shows next to the gates.

The four readiness values are not_checked (no check yet), pending (checked, not all gates pass, never ready before), ready and degraded (was ready, lost a gate).

The two events

Both are catalog events written by the dmarc outbox (producer.service is dmarc-worker) with the subject { "kind": "domain", "id": "dom_..." }; a consumer subscribed through the platform's consumes rule receives each one on its own queue. They carry ids, the domain name, codes and booleans only, never a DNS record value, a report row or an IP address.

EventEmitted whendata fields
domain.auth.ready.v1a check moves the domain into ready (from pending, degraded or not_checked)domain_id, domain, spf_ok, dkim_ok, dmarc_ok (all true), dmarc_policy, mandates_compliant, reports_wired, checked_at
dmarc.auth.degraded.v1a ready domain loses a gate, and again whenever the reason set of a degraded domain changesdomain_id, domain, reasons (one to many codes), previous_readiness, checked_at

Rules a consumer can rely on:

Reason codes

CodeMeaning
spf.missingNo SPF record is published.
spf.over_lookup_limitThe SPF record needs more than 10 DNS lookups.
spf.include_missingThe SPF record does not include the platform's sending servers.
spf.invalidSeveral SPF records, +all, a loop or an unknown term.
dkim.active_selector_missingThe active selector's key is missing or shorter than 1,024 bits.
dkim.key_revokedThe active selector's key is revoked (empty p=).
dkim.not_alignedThe DKIM signature domain does not align with the From domain.
dmarc.missingNo DMARC record at _dmarc.<domain>.
dmarc.invalidSeveral DMARC records, a record that does not parse, or one without a policy.
dmarc.weakenedThe published policy is weaker than the last step the tenant's plan verified.
dmarc.rua_removedThe DMARC record names no valid mailto: address for aggregate reports.
dns.lookup_budget_exceededThe domain needed more lookups than one check allows; some gates were not reached.

Reading the current state

A consumer that needs the state now (a checklist before a bulk send, a ramp that starts later) reads it instead of replaying events, with a service principal holding dmarc:read. The dmarc api admits a sibling product's service principal only once the platform lists that product among the api's service callers (per environment, lane A).

What the answers mean for a consumer:

Timing

The first check runs on domain.verified.v1; the platform's target from that event to domain.auth.ready.v1 on the bus is under 30 seconds once the records are published. Each domain with monitoring on is checked again once a day when the tenant's plan includes DMARC, the tenant stays within its plan's monitored domain limit and the platform's daily monitoring capacity has room; a queued domain starts its daily checks on a later six-hourly pass once there is room (up to ten domains of a tenant per pass). A domain without daily checks keeps the readiness of its last check, and no later event follows until someone checks it. While DMARC is switched off for the platform, each domain's daily checks stop at its next cycle and start again after DMARC is switched back on. A tenant can run up to 6 checks per domain per hour from the panel or the API (POST /v1/dmarc/domains/{domain_id}/check, answered with 202); the result is readable through dmarc.getDomain afterwards, and an event follows only when it is a transition.