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

# Subdomain or root domain

> Verify a subdomain for automated mail so your reputation stays separate from the mailboxes people use every day.

You can verify either `yourshop.co.za` or a subdomain such as `mail.yourshop.co.za`. Both work; the choice affects reputation and DNS hygiene.

## We recommend a subdomain

* **Separate reputation.** Receivers track reputation per domain. If a campaign performs badly, the mail your staff send from Google Workspace or Microsoft 365 on the root domain is unaffected.
* **No DNS conflicts.** Your root domain already has MX and SPF records for your mailbox provider. A subdomain starts empty.
* **Clear intent.** `orders@notify.yourshop.co.za` tells people, and filters, what kind of mail it is.

Good names: `mail`, `notify`, `send`, `updates`. Use another one, such as `news`, for marketing so the two classes never share a reputation.

## When the root domain is right

Small teams that want replies to land in the same mailbox, or brands whose customers expect `@yourshop.co.za` exactly, can verify the root. Nothing else changes: the DKIM records still go on `_domainkey` hosts and the return path still lives on the `mail` subdomain, so your existing MX and SPF stay untouched.

## Subdomains of a verified domain

Once `yourshop.co.za` is verified, `from` may use any subdomain (`orders@notify.yourshop.co.za`) without extra set-up. The reverse is not true: verifying `notify.yourshop.co.za` does not let you send from `yourshop.co.za`.

## Limits

The number of verified domains depends on your plan; see [plans](https://docs.sendbaze.com/resources/plans.md). Adding one beyond the limit fails with `403 plan_limit`; the error body carries the limit and an `upgradeUrl`.


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