/v1/workspaces/{workspace_id}/domains/{domain_id}/dns-recordsAuthPer-record DNS status for a domain.
Every record the domain needs for its intent, with its state (`missing`, `mismatch`, `conflict`, `propagating`, `verified`), what was found, a propagation hint and timestamps, as of the last check (the verifier re-checks pending domains every 5 minutes and active ones hourly). Does not run a DNS lookup; use `POST .../dns-records/check` for that.
Path parameters
workspace_id*string · uuidId of the workspace.
domain_id*string · uuidId of the domain.
Query parameters
zonestring · hostnameRender `name_relative` against this zone (the domain itself or one of its parents). Defaults to the zone found by walking SOA records.
Response · 200
domain_id*string · uuidThe domain id.
fqdn*stringThe domain name.
Example: "mail.example.com"
status*objectVerification status of the domain.
health*objectDrift on a verified domain. `degraded`: a required record (DKIM, or MX for receiving) went missing or changed, or DKIM signing no longer verifies; mail still flows and workspace owners are emailed. `failing`: still degraded 72 h later; sends from the domain are refused with 422 `domain_not_verified_by_provider`. Back to `ok` as soon as the records are. A failed DNS lookup never changes it, and recommended records (MAIL FROM, DMARC) never do. Always `ok` while the domain is not `active`.
Example: "ok"
health_changed_at*string · date-timeWhen `health` last changed; null if it has always been `ok`.
health_grace_ends_at*string · date-timeWhile `health` is `degraded`: when the 72 h grace ends and the domain becomes `failing` unless the records are back. Null otherwise.
zone*stringZone the relative names are rendered against: the `zone` query parameter, else the zone found by walking SOA records (null before the first check).
Example: "example.com"
last_checked_at*string · date-timeWhen the records were last checked; null if never.
records*arrayEach required and recommended record with its current state.
ses*objectenabled*booleanWhether sending verification (DKIM signing) is switched on for this deployment.
dkim_status*objectDKIM signing verification of the DKIM record. `not_enabled` where sending verification is off in this environment (local, preview); null while the domain is not registered for signing yet.
mail_from_status*objectVerification of the custom MAIL FROM host; null when none is configured.
Example
Request
GET https://api.mail.productcraft.co/v1/workspaces/{workspace_id}/domains/{domain_id}/dns-records
Authorization: Bearer YOUR_TOKENResponse
{
"domain_id": "00000000-0000-0000-0000-000000000000",
"fqdn": "mail.example.com",
"status": {},
"health": "ok",
"health_changed_at": "2026-01-01T00:00:00.000Z",
"health_grace_ends_at": "2026-01-01T00:00:00.000Z",
"zone": "example.com",
"last_checked_at": "2026-01-01T00:00:00.000Z",
"records": [
{
"id": "00000000-0000-0000-0000-000000000000",
"purpose": "dkim",
"type": "TXT",
"host": "productcraft._domainkey.mail.example.com",
"name_relative": "productcraft._domainkey.mail",
"value": "v=DKIM1; k=rsa; p=MIIBIjANBgkqh…",
"priority": 10,
"ttl": 3600,
"required": true,
"state": "verified",
"found": [
"string"
],
"conflicts": [
{
"code": "spf_multiple",
"severity": {},
"message": "string",
"suggested_value": "v=spf1 include:amazonses.com include:_spf.google.com ~all"
}
],
"hint": "Your nameservers already serve it; public resolvers will within ~30 min (the zone's negative-cache TTL is 1800 s).",
"covered_by": "_dmarc.example.com",
"first_verified_at": "2026-01-01T00:00:00.000Z",
"last_checked_at": "2026-01-01T00:00:00.000Z",
"last_changed_at": "2026-01-01T00:00:00.000Z"
}
],
"ses": {
"enabled": false,
"dkim_status": {},
"mail_from_status": {}
}
}