check_domain
Poll SES for verification status and unblock sending once DKIM succeeds.
›Check whether mail.acme.com has verified yet, and if not tell me which record is still missing.
What it does
This asks SES directly whether the identity has verified and syncs the answer back into Raechly. When DKIM verification succeeds the domain flips to verified and its mailboxes become send-eligible.
DNS propagation usually resolves in minutes, but it is genuinely variable — some resolvers hold a negative cache longer than the TTL suggests. The right pattern is to publish the records, wait, check, and wait again rather than assuming a failed first check means a typo.
Because the result is authoritative rather than cached, this is the tool that answers "why is nothing sending?" faster than anything else in the set.
The overwhelmingly common cause of a stuck verification is a missing third DKIM CNAME. Two get pasted, the third is lost somewhere between the terminal and the DNS panel, and SES waits indefinitely because two out of three is simply not verified. Ask your assistant to name the missing record rather than re-reading the zone yourself.
Parameters
| Name | Type | Notes |
|---|---|---|
| domain_id * | string | From `list_domains`. |
* required · Maps to POST /api/domains/:id/check
What comes back
Updated verification status. `verified: true` means the domain can send.
The thing people get wrong
A verified identity is necessary but not sufficient. The mailbox on it still needs reply capture and a finished warmup ramp before the pipeline will send campaign mail from it.
Use it with
More domains tools
See all 22 tools and the connection string on the MCP server page.