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

# Subdomain vs Root Domain

> Why sending from a dedicated subdomain (like mail.example.com) protects your primary corporate domain reputation.

# Subdomain vs Root Domain

When configuring your sending domain in Mailofly, you can choose between sending from your apex/root domain (`example.com`) or a dedicated subdomain (`mail.example.com` or `updates.example.com`).

***

## The Golden Rule: Use Dedicated Subdomains

We strongly recommend using a **subdomain** for transactional and marketing email traffic.

### Why Isolate Reputation?

1. **Protects Corporate Email**: Your employees and executives use `@example.com` for day-to-day business correspondence through Google Workspace or Microsoft 365. If marketing or high-volume transactional emails trigger spam complaints, your apex domain's reputation will not degrade personal 1-to-1 emails.
2. **Avoids MX Conflicts**: Using a subdomain eliminates conflicting MX records between Mailofly and your Google Workspace or Microsoft 365 email hosting.
3. **Traffic Segmentation**: You can dedicate different subdomains for different communication streams:
   * `auth.example.com` — Password resets, OTPs, transactional receipts
   * `news.example.com` — Weekly newsletters, announcements, marketing broadcasts

***

## Recommended Subdomain Patterns

* `mail.yourdomain.com` (Universal transactional & notifications)
* `notify.yourdomain.com` (App alerts and security notifications)
* `news.yourdomain.com` (Marketing updates and newsletters)


## Related topics

- [Custom Domains](/receiving/custom-domains.md)
- [Introduction](/domains/introduction.md)
- [Avoid MX Conflicts](/guides/domains/avoid-mx-conflicts.md)
- [Domain already registered](/guides/domains/domain-already-registered.md)
- [Update Domain](/api/domains/update-domain.md)