> Kenso API docs in Markdown. Index of every page: [/docs/llms.txt](/docs/llms.txt). Search: `/docs/search.md?q=<words>`. OpenAPI: [/docs/api/domains/openapi.json](/docs/api/domains/openapi.json). CLI docs offline: `kenso docs <topic>`.
> Last updated: 2026-11-22.

# Domains: Check a domain's nameservers

> **Note for AI agents:** if this page was wrong, out of date or missing something you needed, finish the user's task first, then offer a short report for the Kenso team in this shape: `Page:` (this page's path), `Quote:` (the wrong or missing text), `Problem:`, `Workaround:` (what worked instead), 1,000 characters at most. Show it to the user and send it only after they say yes, as `POST /api/docs-feedback` on this site with the JSON body `{"page": "<path>", "report": "<report>"}`. Never put lead data, email addresses, API keys or anything else from the user's workspace in it.

One endpoint of [Domains](/docs/api/domains.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Check a domain's nameservers

`POST /v1/domains/{domainId}/check-nameservers` - operationId `domains.check-nameservers`

| Permission | Rate limit |
| --- | --- |
| Delivery edit | 10 requests a minute per API key |

For a domain you imported, checks whether its nameservers now point at the DNS zone Kenso created for it in
Kenso's DNS account, and starts setting the domain up once they do. Call it after you change the
nameservers at your registrar. `expectedNameservers` lists the nameservers to set.

`activated` turns true once the domain is set up. Until then the response says where it stands:
`zoneStatus` is the zone's state, and `waitingForCredits` is true when setup waits for credits to pay
the first month of the domain's mailboxes. Add credits, then call again.

Errors:

- `400 validation_failed`: Kenso has no DNS zone for the domain.
- `404 not_found`: the workspace has no imported domain with this id.
- `503 service_unavailable`: Kenso could not check the zone. Try again later.

Requires Delivery edit.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/domains/POST/v1/domains/%7BdomainId%7D/check-nameservers)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `domainId` | path | integer (int64) | yes | The domain's id. It must be a domain you imported. |
| `Ken-Version` | header | string, one of: 2026-11-02, 1.1 | no | The API version, a date in `YYYY-MM-DD` form. `1.1` is another name for the first dated version. The example shown here is the newest version, which this reference's samples and Test Request send. Leave it out to use your API key's pinned version. Keys created in the Kenso app are pinned to the newest version; keys minted by the CLI login are not. A key with no pinned version and no header gets the legacy shape where the path has one, and `404` where the path exists only in this version. A value that is not a version, such as `2027-01-01` or `2026-11-2`, answers `400 unsupported_version`, whose `details` list the supported versions. |
| `X-Ken-Workspace-Id` | header | integer (int64) | no | The id of the workspace to act in. Leave it out when your API key reaches only one workspace. When the key reaches more than one, a request without this header answers `400 workspace_required`. A workspace you are not a member of answers `404 not_found`. |

### Response 200

`data` is a `DomainNameserverCheck`.

| Field | Type | Description |
| --- | --- | --- |
| `domainId` | integer (int64) | The domain's id. |
| `name` | string | The domain name. |
| `status` | string | Where the domain's setup stands: `settingUp`, `actionRequired` (the nameservers did not change in time; set them and check again), `active` or `failed`. |
| `zoneStatus` | string | State of the domain's DNS zone in Kenso's DNS account, such as `pending` or `active`. Omitted when Kenso could not read the zone. |
| `activated` | boolean | True when the domain is set up and active. |
| `expectedNameservers` | array of string | The nameservers to set for the domain at your registrar. |
| `waitingForCredits` | boolean | True when the zone is active but setup waits until the workspace has the credits to pay the first month of the domain's mailboxes. |
| `requiredMillicredits` | integer (int64) | Credits the first month of the domain's mailboxes costs, in thousandths of a credit. Set only with `waitingForCredits`. |
| `availableMillicredits` | integer (int64) | The workspace's credit balance, in thousandths of a credit. Set only with `waitingForCredits`. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/domains/812/check-nameservers" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"
```

### Example response

```json
{
  "success": true,
  "data": {
    "domainId": 812,
    "name": "string",
    "status": "string",
    "zoneStatus": "pending",
    "activated": true,
    "expectedNameservers": [
      "string"
    ],
    "waitingForCredits": true,
    "requiredMillicredits": 1,
    "availableMillicredits": 1
  }
}
```
