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

# Sender domains

> The domains your e-mail comes from: who may add one, the three DNS records, what verified means, the 72 hours, the default from address, and how a domain is removed.

Every message Tawked Email sends comes from an address on a domain your application verified. A domain is added on **Email → Setup** (named **Domains** once the application has sent its first message) by the account owner, an admin or a developer of the application, once Tawked's team has approved the account for early access.

## The rules

* **Your own domain only.** Add a domain you control: `acme.sa`, or a subdomain such as `mail.acme.sa`.
* **No public mailbox domains.** `gmail.com`, `outlook.com`, `hotmail.com`, `live.com`, `yahoo.com`, `icloud.com`, `me.com`, `proton.me` and the other public mailbox providers, and any subdomain of one, are refused: nobody owns them but their provider. So are Tawked's own domains.
* **One application per domain.** A domain belongs to the application that added it, for good. Another application, in your account or any other, cannot add it.
* **Up to 5 domains per application.** A removed domain no longer counts.
* **Arabic domains work.** A domain in Arabic letters is stored in its ASCII form for DNS and shown as you typed it.

## The three records

Adding a domain shows three CNAME records, in the form `<token>._domainkey.<your domain>` pointing to `<token>.dkim.amazonses.com`. Add the three at your DNS provider exactly as shown. They publish the keys that sign each message with DKIM, which is how receiving servers know the mail really comes from your domain.

The domain's page also shows where your domain's DNS lives, read from its nameservers (for example Cloudflare, GoDaddy, Namecheap, Route 53 or Hostinger), with a link to that provider's DNS records page and its own steps. When the domain is on Cloudflare, GoDaddy or IONOS, the page can offer to add the three records for you: you sign in at your provider, approve once, and come back to Tawked, which checks the domain at once.

Nothing else changes: no MX record, no SPF change, and your mailboxes keep working. DKIM is also what makes your messages pass DMARC, so if your domain has no DMARC record yet, add one (a TXT record at `_dmarc.<your domain>`, starting with `v=DMARC1; p=none`).

## States

| State | What it means | Can it send? |
| - | - | - |
| Pending | The domain is added; Tawked is waiting for the three records. | No |
| Verified | The three records were found and the signing works. | Yes, from any address on the domain |
| Failed | The records were not found within 72 hours of adding the domain, or the check failed. | No |
| Removed | You removed the domain. | No |

Tawked checks a pending domain every ten minutes, and **Check now** checks it at once. The console tells you when the domain is verified. A failed domain can be added again: it gets three new records.

A verified domain is checked again once a day. If its records disappear, it goes back to **Pending** and sends from it answer `422 sender_not_verified` until the records are back.

## The default from address

A verified domain has a default from name and a default local part (`no-reply` unless you change it), set on the domain's own page under **Email → Setup**. A send without `from` uses them: `"Acme Store" <no-reply@acme.sa>`. A send with `from` can use any address on the domain, `orders@acme.sa` or `support@acme.sa`, without adding it first.

## Test message

From a verified domain's page, you can send one test message to your own e-mail address. It is free and appears on **Email → Messages** like any other.

## Removing a domain

Removing a domain stops sending from it at once, and its records can be deleted from your DNS. The messages it sent stay on **Email → Messages** with their history. The domain stays with your application: the same application can add it again later, and it gets three new records.


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