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:
- SPF: one valid
v=spf1record that includes the platform's sending servers (include:spf.<base domain>) and needs at most 10 DNS lookups. - DKIM: the identity's active selector (or, on a hosted identity, the token that publishes the key) is published with a key of at least 1,024 bits (2,048 recommended) and the signature domain aligns with the From domain under the record's
adkim. - DMARC: one
_dmarc.<domain>record parses, carries a policy, names at least one validmailto:address inrua, and is not weaker than the last policy step the tenant's plan verified.
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.
| Event | Emitted when | data fields |
|---|---|---|
domain.auth.ready.v1 | a 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.v1 | a ready domain loses a gate, and again whenever the reason set of a degraded domain changes | domain_id, domain, reasons (one to many codes), previous_readiness, checked_at |
Rules a consumer can rely on:
- Edge-triggered. A daily check that finds the same state emits nothing. Recovery is a new
domain.auth.ready.v1, never a "degraded cleared" event. - At least once. Deduplicate on the envelope
id; a redelivered event is the same event. - **Order by
checked_at.** Two events of one domain can arrive out of order; the laterchecked_atwins. - Our resolver is never your problem. When the platform's DNS resolver cannot answer, the check is stored as history and retried; no event is emitted and the domain keeps its readiness. A
resolver.code never appears inreasons. - Unknown codes. New reason codes may be added; treat a code you do not know as a generic degradation, never as an error.
Reason codes
| Code | Meaning |
|---|---|
spf.missing | No SPF record is published. |
spf.over_lookup_limit | The SPF record needs more than 10 DNS lookups. |
spf.include_missing | The SPF record does not include the platform's sending servers. |
spf.invalid | Several SPF records, +all, a loop or an unknown term. |
dkim.active_selector_missing | The active selector's key is missing or shorter than 1,024 bits. |
dkim.key_revoked | The active selector's key is revoked (empty p=). |
dkim.not_aligned | The DKIM signature domain does not align with the From domain. |
dmarc.missing | No DMARC record at _dmarc.<domain>. |
dmarc.invalid | Several DMARC records, a record that does not parse, or one without a policy. |
dmarc.weakened | The published policy is weaker than the last step the tenant's plan verified. |
dmarc.rua_removed | The DMARC record names no valid mailto: address for aggregate reports. |
dns.lookup_budget_exceeded | The 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).
GET /v1/dmarc/domains/{domain_id}(dmarc.getDomain):readiness,ready_since,degraded_since,last_checked_at, the last check's summary per gate with its reasons (last_check.degraded_reasons, never aresolver.code) and the recent runs (recent_runs). The runs are history: a run our resolver could not complete showspendingwithresolver.unavailableand does not changereadiness.GET /v1/dmarc/domains(dmarc.listDomains): one summary row per domain of the tenant, a cursor page of up to 100 rows (next_cursor), filtered byreadinesswhen asked.
What the answers mean for a consumer:
200: the state as oflast_checked_at.402(entitlement_required) or503(product_disabled): DMARC is not installed for this tenant or not running; show "skipped: product not installed" and do not block on readiness.503with any other code (provider_unavailable): a passing outage; retry afterRetry-After.401or403: the caller's credentials or scope; fix the caller, never treat it as a state.404: the domain is not an identity of this tenant.
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.