# Sending Domains {#sending-domains}


You can send from a domain you own or from a Nitrosend address such as
`hello@your-brand.nitrosend.net`. Your own domain is the better choice for
reaching the inbox. A Nitrosend address needs no DNS setup and does not use your
custom-domain allowance, so you can start now and connect your domain later.


## What to know before you choose {#what-to-know-before-you-choose}


- **Reputation:** a Nitrosend address has to warm up its sending reputation over
  time, so start with your most engaged contacts and build up. That reputation
  stays with the address and does not move to your own domain when you switch.
- **Capacity:** a Nitrosend address shares sending capacity with other senders,
  so big lists go out more slowly than from your own domain.
- **DNS:** your own domain needs DNS records, which can take from a few minutes
  to a couple of days to take effect. You can leave while they do. We keep
  checking and email you when the domain is ready to send from.
- **The Nitrosend footer:** on the Free plan your emails carry the footer from a
  Nitrosend address and from your own domain alike.
  [How to remove it](https://docs.nitrosend.com/faq.md#how-do-i-remove-the-sent-with-nitrosend-badge-from-my-emails).


## Use your Nitrosend address {#use-your-nitrosend-address}


Choose an address during setup and activate it. If you complete your Brand Kit
first, Nitrosend can suggest a name from your company name. Activating an address
does not send any email. An existing custom sender stays selected until you
choose to replace it.

Under **Settings → Domains**, your Nitrosend address is listed with your domains.
Open it and select **Use this address** to make it your default.

The shared `nitrosend.net` sender is paced, so larger sends go out gradually.
Small bursts are allowed, and individual flow and transactional messages go
ahead of campaigns. Queued mail continues automatically, and this pacing is
separate from your plan's rolling 24-hour allowance.

For sustained campaign volume, connect your own sending subdomain. It does
not use the shared-domain rate pool; your plan allowance and other provider
and safety limits still apply. Upgrading alone does not remove shared-domain pacing.


## Change your Nitrosend address {#change-your-nitrosend-address}


In **Settings → Domains**, open your Nitrosend address and select **Change
address**, then **Change address name**. You can also make this change from **Inbox → Manage inboxes**.
For example, `hello@old-name.nitrosend.net` can become
`hello@new-name.nitrosend.net`.

The same inbox keeps its messages and attachments. Previous addresses keep
receiving mail, and new replies use the new address. Past emails stay unchanged.
Old names remain reserved to your brand, so another customer cannot claim them.
System names and names that impersonate other businesses are unavailable.

Address changes share your existing address allowance. If you change the name too
often, you'll be asked to wait an hour. A campaign, flow or reply still using the
address must finish or be updated before you change it.
The new sender goes through the usual sending checks.

For API clients, send `subdomain` and the current `brand_subdomain.fqdn` as
`expected_fqdn` to `POST /v1/my/brands/{sid}/rename_hosted_sender`. An exact retry
returns the same address. The response is the updated brand. The agent tool uses
`nitro_manage_domains` with `operation: "rename_brand_subdomain"`, the same two
parameters, and `confirm: true`.


## Add a sending subdomain {#add-a-sending-subdomain}


1. Go to **Settings → Domains** ([app.nitrosend.com/my/settings/domains](https://app.nitrosend.com/my/settings/domains)).
2. Choose your own domain and enter it. Nitrosend sets up
   `send.yourdomain.com` so your emails come from `hello@yourdomain.com`. Select
   **Change domain** to use a different one. If you already have a domain, choose
   **Add another domain** and enter the subdomain.
3. If your DNS provider supports one-click setup, select **Connect** and authorise
   it. Otherwise, Nitrosend shows the DNS records for that subdomain to add at your
   DNS provider (see below).
4. Nitrosend verifies the records automatically. Once they resolve, the domain
   flips to **Verified** and we email the account owner, the first time it verifies.

Verifying alone does not change your From address. Open the domain and select
**Send from**, or set your From address under **Brand → Sender**. If you chose the
domain for your first send, Nitrosend moves it for you.


## Use a dedicated sending subdomain {#use-a-dedicated-sending-subdomain}


A subdomain such as `send.yourdomain.com` helps separate sending configuration
from your team's everyday mail. Add the records Nitrosend supplies without
replacing the MX records used by your existing inbox provider.

The technical sending domain and the address recipients see can differ. Use
the verified From address offered by Nitrosend; a technical sending subdomain
does not mean your visible address must also use it.

Subdomains help separate mail streams, but inbox providers can consider the
parent domain, related domains, shared IPs and links together. They do not
guarantee independent reputation or Inbox placement. See
[Sending to Outlook and Microsoft 365](https://docs.nitrosend.com/guides/microsoft-delivery.md).


## Add the DNS records {#add-the-dns-records}


The **Domains** screen lists the exact records for your subdomain: typically a
verification record, **SPF**, **DKIM**, and a return-path / tracking record. Add
each one at your DNS provider (Cloudflare, GoDaddy, Namecheap, Route 53, and so on).

Enter each record's **Host** in your provider's Host or Name field, with the type
and value as shown. Most providers add your domain to that field themselves, so
`send` becomes `send.yourdomain.com`, and `@` means the domain itself. Some
providers, such as Cloudflare, accept the full name too.



> [!IMPORTANT]
> DNS changes can take anywhere from a few minutes to a couple of days to
> propagate. Nitrosend re-checks automatically, so you don't need to trigger
> verification or stay on the page.




## Share a subdomain with another brand or client {#share-a-subdomain-with-another-brand-or-client}


The account owner or an administrator can share an exact subdomain of a verified
domain. For example, the owner of `alvin.finance` can give one brand
`envoy.alvin.finance` and another `travel.alvin.finance`.

1. Open **Settings → Domains** in the brand that owns the verified domain.
2. Select **Share a subdomain**, enter a name such as `envoy`, and choose the
   destination brand or eligible managed client.
3. Select **Share subdomain**, then **Open domain setup** to finish the usual DNS
   setup in that brand. Only the new subdomain's records need to change.
4. Open **Inbox → Manage inboxes**. If receiving is not configured yet, choose
   **New inbox → Set up another domain**, select the verified shared subdomain,
   and finish receiving setup. Add its MX record only on that subdomain.
5. Add further named inboxes on the same subdomain from **New inbox**.

The new brand has its own sending identity and inboxes. Sharing does not switch
an existing sender, expose another brand's messages, or reuse its sending history.
The sending domain (`send.envoy.alvin.finance`) and visible From domain
(`envoy.alvin.finance`) use one custom-domain slot in the destination account.
Inboxes use that account's existing inbox allowance and paid capacity.

Managed clients still use the existing ownership claim and client-paid
subscription. Sharing a domain does not bypass those requirements.

To withdraw permission, open the same section and choose **Stop sharing**.
Subsequent sends, including queued mail, and receiving stop for that subdomain.
Existing messages stay in their original brand; other subdomains keep working.
**Share again** restores permission after the owner confirms the same destination.
If a managed relationship ends, a new relationship needs fresh sharing permission.

For API clients, the owner brand uses:

- `GET /v1/my/domains/{domain_id}/subdomains` to list shared children (25 per page).
- `POST /v1/my/domains/{domain_id}/subdomains` with
  `{ "subdomain": { "subdomain": "envoy", "brand_sid": "destination-brand-sid" } }`.
- `DELETE /v1/my/domains/{domain_id}/subdomains/{id}` to stop sharing.

The response identifies the child sending domain. Use the destination brand's
credentials for its normal domain and inbox setup. Brand-pinned keys do not
receive a directory of other brands. An exact creation retry reuses the same
claim. Agents use the same sharing actions, with confirmation before changes.


## Route different mail through different subdomains {#route-different-mail-through-different-subdomains}


You can verify more than one subdomain and push different email through each by
changing the send-from address:

- `hello@news.yourdomain.com` — marketing campaigns
- `hello@txn.yourdomain.com` — transactional / product email

Splitting sending this way helps manage mail types separately. Providers may
still associate their reputation, so it cannot guarantee that a promotional
send will never affect receipts or password resets. This is most useful for
**large-volume senders**; many brands can use a single sending subdomain.


## Set a reply-to address {#set-a-reply-to-address}


Your send-from address doesn't have to be where replies land. Set a **Reply-To**
under **Brand → Sender** ([app.nitrosend.com/my/brand/sender](https://app.nitrosend.com/my/brand/sender)) and replies go to whatever inbox you like — independent of
the subdomain you send from.

For example, send from `news@send.yourdomain.com` but have replies arrive at
`hello@yourdomain.com`. The Reply-To can be any mailbox you actually monitor, on
another domain used by your business. Keep sender details accurate and use a
working mailbox your team monitors.


## How sending capacity grows {#how-sending-capacity-grows}


Sending allowance depends on your plan and sender standing: Probation, Standard
or Trusted. Standing ranks attributable delivery history, positive current list
verification, domain strength and account signals together. Strong evidence can
earn a higher standing on day one; payment alone cannot. Trusted receives the
full plan allowance immediately, without a second volume ramp. See
[Pricing](https://docs.nitrosend.com/pricing.md) for the plan-and-standing allowances.

Each effective sending identity still owns its own delivery and reputation
history. History is not copied between domains, and changing sender context
does not copy its first-send content clearance. Probation continues to require
review of each changed content identity; higher standing does not bypass sender
authentication, suppression or safety checks.

The account's fixed plan/standing allowance, provider limits, and delivery
pacing are separate inputs to one admission decision. The API, MCP status, and
review responses report the binding result; clients should not calculate a
private limit from plan names.
