Sending domains and identity verification
Configure DNS through the actual workflow, understand verification statuses, and separate customer and operator steps.
A sending domain proves that you are authorized to send from that domain. It also supports DKIM, DMARC, sender mailboxes, and delivery reputation. This page separates customer actions from steps handled by platform operators.
Prerequisites
- You own the domain or can manage its DNS.
- The domain is not a public mailbox domain, shared mail platform, or restricted brand domain.
- Email product is enabled for your account. The domain must be approved for sending before you create a mailbox.
Add and verify a domain
Submit the domain
Open Sending Domains, click Add Domain, and enter a fully qualified domain such as mail.example.com. The precheck warns about formatting, restricted domains, or DNS lookup risks. It does not replace later verification or mean the domain is approved.
Wait for platform records
A new domain starts in Pending authorization. The platform configures its domain authorization service and prepares the DNS details shown on the detail page. No customer action is needed yet; wait for platform operations or AI support to complete this step and check the updated status.
Configure records at your DNS provider
Add each record shown in the detail page, checking its type, host, and value. Do not copy another domain's DKIM public key or overwrite SPF for existing legitimate senders.
| Record or capability | What to do |
|---|---|
| DKIM | Add the records shown on the page to authenticate the sending domain and message signatures. |
| MX / SPF for custom MAIL FROM | Configure only when explicitly shown and enabled by the platform. Do not invent records when none are shown. |
Last updated on