> ## Documentation Index
> Fetch the complete documentation index at: https://sendmux.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Domains

> Add, verify, and manage custom domains for sending and receiving.

Use a custom domain when you want branded sending, hosted mailboxes, or both. Choose the domain mode when you add it: sending only avoids MX changes, while sending & receiving lets you create mailboxes after verification.

## Domain options

| Option | Best for | DNS required |
| - | - | - |
| `myagent.mx` shared domain | Fast tests and simple agents | No |
| Custom domain, sending only | Branded outbound mail while another inbox receives | TXT and CNAME |
| Custom domain, sending & receiving | Branded mailboxes hosted in Qubrics | TXT, CNAME, MX |

> [!NOTE]
>
> If you're using a Free team, you can have **1 domain**. Check your current
> limit on the **Domains** page. Free limits are fixed. If you need more
> capacity, delete an unused domain or upgrade to Pro. See [Team
> limits](https://sendmux.ai/docs/account/team-limits.md).

## Add a domain

**1. Open Domains**

Open **Domains** in the team workspace and select **Add domain**.

**2. Enter the domain**

Enter the domain you own, such as `mail.example.com` or `example.com`.

**3. Choose usage**

Choose **Sending only** if Qubrics should only send from the domain. Choose
**Sending & receiving** if Qubrics should also receive mail and host
mailboxes on the domain.

**4. Copy DNS records**

Qubrics shows the records required for your chosen usage. Sending-only
domains do not show or check an MX record.

**5. Publish the records**

Add each record at your DNS provider. Copy values exactly as shown.

**6. Verify**

Select **Verify** after the records have propagated. Sending-only domains
check ownership, sending policy, message policy, email signing, and bounce
handling. Sending & receiving domains also check inbound routing.

## DNS records

| Purpose | Record | Required for | What it does |
| - | - | - | - |
| Ownership | TXT | Both modes | Confirms you control the domain. |
| Email signing | CNAME | Both modes | Enables DKIM signing through Amazon SES. |
| Sending policy | TXT | Both modes | Authorises Qubrics to send for the domain. |
| Message policy | TXT | Both modes | Defines DMARC handling for suspicious mail. |
| Bounce handling | MX and TXT | Both modes | Routes bounce handling through a subdomain. |
| Receive mail | MX | Sending & receiving | Routes inbound mail for the domain to Qubrics. |

You can download the records as a zone file from the domain detail page.

For DMARC, verification checks only that a TXT record at `_dmarc.{your-domain}` contains `v=DMARC1`. You can keep your existing policy.

## Enable receiving later

Open the sending-only domain and choose **Switch to sending & receiving**. Qubrics adds the MX requirement, resets the domain to pending, and asks you to verify again. Add the MX record before creating mailboxes.

## Verification states

| State | Meaning |
| - | - |
| `pending` | Records are missing, still propagating, or still being checked. |
| `verified` | All required records are present and ready. |
| `failed` | One or more records could not be verified after repeated checks. |

Qubrics rechecks DNS every six hours. A short DNS issue does not immediately trigger an email. Persistent failures notify team owners.

Amazon SES status is checked separately on a five-minute schedule, even when DNS checks cannot complete. This schedule does not guarantee an update within five minutes.

Your domain list and detail page refresh while visible and when you return to the tab. The **Action required** label includes a temporary Amazon SES authentication failure. Review the individual status checks and the last-checked time.

For previously verified managed domains, Qubrics compares authentication status reported by Amazon SES, including DKIM. It creates an alert when authentication degrades, worsens or fully recovers. Repeated observations of the same status do not create duplicate alerts.

Team owners choose email and in-app notices, including recovery notices, in their Deliverability notification preferences. Alerts that include disabled sending or signing use both channels for active owners and admins, even if those channels are disabled in their preferences. Email notices can arrive after the status update.

Managed sending from your custom domain requires a successful Amazon SES identity check, sending enabled, healthy DKIM and signing enabled. If custom MAIL FROM is configured, it must also be healthy and match the configured domain. Checks expire after one hour. Missing, incomplete, unhealthy or older checks block managed sending, including saved mailbox drafts, and remove its options from mailbox sender choices until verification and a fresh, healthy check succeed. Connected sending accounts keep their existing rules.

## Troubleshooting

> [accordion] Ownership is not found
>
> Check that the TXT record name and value match Qubrics exactly. Some DNS
> providers append the zone name automatically, which can duplicate the
> domain.

> [accordion] Inbound routing is not found
>
> This only applies to sending & receiving domains. Check that the MX record
> is on the same domain you added to Qubrics. DNS proxying features do not
> apply to MX records.

> [accordion] SPF is failing
>
> Keep only one SPF record for the same domain name. Merge all `include:`
> values into the same TXT record.

> [accordion] Bounce handling is failing
>
> Check the MX and TXT records on the `bounce.{your-domain}` subdomain. The
> MX record must use the target Qubrics shows, and the TXT record must match
> the generated SPF value.

> [accordion] DMARC is failing
>
> Publish a TXT record containing `v=DMARC1` at `_dmarc.{your-domain}`. The
> policy and other fields do not affect verification.

> [accordion] Email signing is still pending
>
> DKIM records can take longer to verify. Confirm all three CNAME records are
> present, then wait and verify again.

## Delete a domain

Deleting a sending-only domain stops sending from it. Deleting a sending & receiving domain is blocked while active mailboxes still use it. Delete or move those mailboxes first, then delete the domain.

After deletion, remove the DNS records from your DNS provider if you no longer need them.

## API access

Use the Management API when you want to create, list, upgrade, verify, or delete domains from your own tooling. Keep API shape, permissions, and error handling in the generated reference so your client follows the current contract.

> [card] [Management API](https://sendmux.ai/docs/api/introduction.md)
>
> Open the generated Domains endpoint reference.

## Related guides

> [card] [Mailboxes](https://sendmux.ai/docs/mailboxes)
>
> Create addresses on verified sending & receiving domains.

> [card] [Domain settings](https://sendmux.ai/docs/domains/settings.md)
>
> Review inbound controls for sending & receiving domains.

> [card] [Sending accounts](https://sendmux.ai/docs/sending/accounts)
>
> Connect providers for outbound sending.

> [card] [Team limits](https://sendmux.ai/docs/account/team-limits.md)
>
> Request more domain capacity.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.