Checking domain status
Three endpoints report on a domain, and they read DNS differently. Picking the wrong one is why a record you just published appears to be missing.
| Endpoint | Resolver | Reads | Use it for |
|---|---|---|---|
GET /v1/domains/{domain}/detail |
cached recursive | MX, SPF, DKIM, DMARC | a dashboard view |
POST /v1/domains/{domain}/verify |
recursive | the ownership token only | completing setup |
POST /v1/domains/{domain}/recheck |
authoritative, direct | every record, live | “I just published it” |
Account-wide summary
GET /v1/domains/status scope: tenant:read
Every domain with its verification state, for a status page or a health check.
Note the different scope: tenant:read, not domains:read.
One domain, with live DNS
GET /v1/domains/{domain}/detail scope: domains:read
The domain plus a per-record view of what we can currently see. Good for rendering a setup page; subject to caching, so do not use it to confirm a change you made seconds ago.
Forcing a fresh look
POST /v1/domains/{domain}/recheck scope: domains:write
{
"domain": "yourcompany.com",
"verified": true,
"dns_checks": [ ... ],
"checked_at": "2026-10-17T09:41:02Z"
}
It queries the authoritative nameservers, so there is no cache between you and
the answer. It also re-runs the same idempotent reconciliation /verify does,
pushing DKIM to the mail server and provisioning the DMARC mailbox, so it
doubles as a repair for a domain whose setup partly failed.
It never un-verifies a domain. Verification is monotonic: ownership was proven once and a later DNS change does not retract that, even if the token record is gone.
Note it needs domains:write, not domains:read, because of that
reconciliation. A read-only key cannot call it.
Reading verified correctly
verified: true means one thing: the ownership token was seen at least
once. It does not mean SPF, DKIM, MX or DMARC are in place, because
verification never checks them.
For “is this domain actually ready to send”, read the per-record status from
/detail or /recheck. For “may I send as this address”, the rules are in
Sender identity.