# Sending Subdomain Architecture

## Differentiating Domains & Subdomains

An email subdomain is **a prefix** added to your **main domain name** that creates a distinct sending identity.&#x20;

<figure><img src="https://509463063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiAYaWDWqtFZeXxyg67F%2Fuploads%2FzIOu5rIrlxopkEfanH9m%2Fdeliverability_domain-anatomy_290925.png?alt=media&#x26;token=91465f36-1cff-404e-9c07-bb7054b476a6" alt="Email address anatomy"><figcaption></figcaption></figure>

If your company domain is **`company.com`**, you might use subdomains like:

* <mark style="background-color:yellow;">**news**</mark>**.company.com**, for your newsletters and marketing communications.
* <mark style="background-color:blue;">**account**</mark>**.company.com**, for your service related communications.
* Etc

## Why Use Separate Subdomains Instead of a Root Domain?

Most mailbox providers track the reputation of **each subdomain separately**. Think of it like having different phone numbers for different departments in your company—each builds its own reputation based on how it's used.

We strongly recommend using **dedicated subdomains for different email types**—particularly separating transactional emails (e.g. password resets, receipts, account notifications) from marketing emails (e.g. newsletters, promotional campaigns).&#x20;

Here is how a typical email setup looks like:

<figure><img src="https://509463063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiAYaWDWqtFZeXxyg67F%2Fuploads%2FpFNAZ5JQtUWGhqngAABD%2Fdeliverability_ip-pools_310325.png?alt=media&#x26;token=ee85c6b9-9f89-42fe-a43d-14efb59e308e" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Know more on the ideal sending structure and subdomains in our dedicated article: [sending-infrastructure-best-practices](https://doc.batch.com/guides-and-best-practices/email-deliverability/email-authentication-and-sending-structure/sending-infrastructure-best-practices "mention")
{% endhint %}
