# EMAIL_DOMAIN_NOT_READY

The domain is still being registered. Try again in a few seconds.

<Callout type="info">
**Category:** [Email delivery](/errors/category/email)
</Callout>

| | |
|---|---|
| HTTP status | `409` Conflict |
| Retry | After fixing the cause |

## When it happens

The domain is still being registered: it has no DNS records yet (`dns_records` is empty).

## How to fix it

Read the domain again in a few seconds. If it still has no records, delete it and register it again.

## Retry

Not as is: the same request fails the same way. Fix the cause described above, then send the request again, under a new `Idempotency-Key` if the body changed.

## Returned by

The operations where this code is most likely. The list is not exhaustive.

- [`POST /v1/accounts/{account_id}/email-domains/{email_domain_id}/verify`](/emails/verifyAccountEmailDomain)
- [`PUT /v1/companies/{company_id}/email-configuration`](/emails/updateCompanyEmailConfiguration)

## Example response

When this error occurs, the API answers `409` Conflict with a JSON body of this shape:

```json
{
  "type": "https://docs.beel.es/errors/EMAIL_DOMAIN_NOT_READY",
  "title": "EMAIL_DOMAIN_NOT_READY",
  "detail": "The domain is still being registered. Try again in a few seconds.",
  "instance": "/v1/<resource>",
  "errors": [],
  "success": false,
  "error": {
    "code": "EMAIL_DOMAIN_NOT_READY",
    "message": "The domain is still being registered. Try again in a few seconds.",
    "details": {}
  },
  "meta": {
    "timestamp": "2026-05-21T10:00:00Z",
    "request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
  }
}
```

The `type` URI is stable and always resolves to this page.

## Message

<Tabs items={["English", "Spanish", "Catalan"]}>
  <Tab value="English">{"The domain is still being registered. Try again in a few seconds."}</Tab>
  <Tab value="Spanish">{"El dominio se está registrando todavía. Inténtalo de nuevo en unos segundos."}</Tab>
  <Tab value="Catalan">{"El domini encara s’està registrant. Torna-ho a provar d’aquí a uns segons."}</Tab>
</Tabs>

Send the request with `Accept-Language: <es|en|ca>` to receive the message in your preferred language.

## Other errors in this category

<div className="grid grid-cols-2 gap-3 not-prose">
  <Card title="EMAIL_DOMAIN_INVALID" description="The domain is not valid. Provide a full domain name, such as invoices.example.com." href="/errors/EMAIL_DOMAIN_INVALID" />
  <Card title="EMAIL_DOMAIN_LIMIT_REACHED" description="You have reached the maximum number of email domains for your account (‹value›)." href="/errors/EMAIL_DOMAIN_LIMIT_REACHED" />
  <Card title="EMAIL_DOMAIN_NOT_FOUND" description="No email domain with that id belongs to your account." href="/errors/EMAIL_DOMAIN_NOT_FOUND" />
  <Card title="EMAIL_DOMAIN_RESERVED" description="That domain is reserved and cannot be used to send emails." href="/errors/EMAIL_DOMAIN_RESERVED" />
  <Card title="EMAIL_DOMAIN_UNAVAILABLE" description="That domain cannot be registered: it is already in use." href="/errors/EMAIL_DOMAIN_UNAVAILABLE" />
</div>

## Keep exploring

<div className="grid grid-cols-2 gap-3 not-prose">
  <Card title="All Email delivery errors" description="Every code in this category in one table." href="/errors/category/email" />
  <Card title="Error reference home" description="Browse every category or jump to the handling guide." href="/errors" />
</div>

---

Full OpenAPI spec: https://docs.beel.es/api/openapi