# Deliverability check

> Check a mailbox’s SPF, DKIM, DMARC and tracking domain so its emails are trusted.

Every section below does the same job: in the dashboard (Guide), from your code (API) or through an AI assistant (MCP).

## Guide — In the dashboard

Source: /docs/engage/mailboxes/deliverability

Each mailbox shows its DNS checks (SPF, DKIM, DMARC) and tracking. Run a check after changing DNS, and use your own domain for open and click tracking.

1. **Integrations → Email Accounts:** the Deliverability column shows the checks.
2. **⋮ → Check DNS Records** after a DNS change.
3. **⋮ → Custom Tracking Domain** to track with your own domain.


---

## API — From your code

Source: /docs/engage/mailboxes/deliverability/api

Authenticated with `?privateKey=YOUR_KEY` (see [Authentication](/docs/authentication)).

<Endpoints ops={["POST /admin/email-accounts/{id}/check-deliverability", "POST /admin/email-accounts/{id}/verify-tracking-domain"]} />

<ApiPlayground
  ops={["POST /admin/email-accounts/{id}/check-deliverability", "POST /admin/email-accounts/{id}/verify-tracking-domain"]}
  method="post"
  path="/admin/email-accounts/{emailAccountId}/check-deliverability"
  tool="run_deliverability_check"
  args={`{
  "emailAccountId": ""
}`}
/>

### Use case: After a DNS change [#use-case-after-a-dns-change]

`POST /admin/email-accounts/{id}/check-deliverability` runs the checks again and returns what is still missing.


---

## MCP — AI agents

Source: /docs/engage/mailboxes/deliverability/mcp

Connect the [MCP server](/docs/mcp#quickstart), then just ask.

<Tools names={["run_deliverability_check", "verify_tracking_domain"]} />

### Use case [#use-case]

> Is my new mailbox set up correctly?

<McpToolCall name="run_deliverability_check">

```json
{
  "emailAccountId": "6530c1d2e3f4a5b6c7d8e9f6"
}
```

</McpToolCall>

