Skip to content
  • There are no suggestions because the search field is empty.

Shared domains and multi-service setups

When several services send as one domain, each one needs its own aligned DKIM or SPF pass, or some of your mail will fail DMARC once you enforce. That doesn't mean each service gets its own SPF record. A domain name can have only one SPF record, shared by every sender on it and limited to 10 DNS lookups, while DKIM can have as many keys as you have services. The other choice is to move some services onto their own subdomains, which costs more DNS work and keeps them apart.

DMARC checks each message on its own. One domain might carry mail from Microsoft 365, a marketing platform, a CRM, a billing tool, and a web server. Each of those has to produce its own aligned pass. The trouble usually starts with the pieces they share: one SPF record that every team edits, one lookup budget, and one reputation covering very different kinds of mail.

What can be shared, and what can't

  • SPF: one record per name. All senders that use that name in MAIL FROM have to fit into a single v=spf1 record. Every include, a, mx, ptr, exists, and redirect counts toward the 10-lookup limit, nested ones included. More services on one name means more risk of permerror (The 10-lookup limit and SPF permerror, Multiple SPF records (why that is invalid)).
  • DKIM: many keys at once. Selectors exist so a domain can have multiple public keys at the same time, including when you delegate signing to a partner, such as an advertising provider. Give each service its own selector (DKIM selectors and DNS records). A message passes DMARC if any aligned signature validates.
  • DMARC: one record per name, inherited by subdomains. A subdomain without its own record is covered by the policy found higher up: sp if it's set, otherwise p, with np for subdomains that don't exist. Microsoft puts it this way: the DMARC record "automatically covers all subdomains (including nonexistent subdomains) that don't have their own DMARC TXT record". The details are in Subdomain policy (sp).
  • Alignment across subdomains. Under relaxed alignment, the default, d=news.example.com or a Return-Path on bounce.example.com aligns with From: example.com, and the reverse works too. Strict alignment removes that flexibility, which is why it rarely suits multi-service setups (Relaxed vs strict alignment).

Option 1: everything on one domain

This is simpler for recipients, who see one domain, and harder to run.

  • One SPF record holds every include. Watch the lookup count. Use ip4 and ip6 for senders with fixed addresses, since those don't cost lookups. Remove services you've retired, and review the SPF record periodically.
  • Lean on DKIM per service. Aligned DKIM doesn't use any SPF lookups, so SPF capacity shouldn't decide whether you can add a vendor (SPF include vs DKIM from the vendor).
  • Reputation is shared. Complaints about a marketing stream can affect invoices and staff mail on the same domain. Each IP and DKIM domain has a reputation, which can impact the delivery of your email. How reputation works is in IP and domain reputation.

Option 2: an email subdomain per service or stream

This takes more DNS work and gives cleaner separation.

  • Microsoft recommends it for "email services that aren't under your direct control (for example, bulk email services)," for example marketing.example.com, because "You don't want issues with mail sent from those email services to affect the reputation" of your main domain.
  • A subdomain used in MAIL FROM needs its own SPF record. Microsoft: "the SPF TXT record for contoso.com doesn't cover marketing.contoso.com; marketing.contoso.com needs its own SPF TXT record." SPF is checked for the exact MAIL FROM domain.
  • Each name has its own lookup budget. Microsoft: "Each subdomain has its own 10 lookup budget." Splitting services across subdomains spreads the load.
  • DMARC can stay inherited or be overridden. A new vendor subdomain can run at p=none with its own record while the apex is enforced. Microsoft: "you can disrupt the inheritance of DMARC on a subdomain by creating a DMARC TXT record in that subdomain."
  • Google and Yahoo point the same way on message types. Google recommends a different IP address for each message type when you send from several, and the same From address for messages of the same category. To "Segregate Email types by IP or DKIM domain."

A subdomain can limit the impact of one noisy sender. It doesn't guarantee inbox placement, and the reputation benefit is provider guidance, not a measured effect.

What a subdomain really needs

Microsoft's DMARC page says "each subdomain requires an SPF and DKIM record for DMARC." That's a useful rule of thumb, but the protocol is narrower. SPF is needed only for names used in MAIL FROM, and DKIM keys only for names used as d=. A subdomain that appears only in From can still align through records on the parent domain under relaxed alignment. If you're unsure, follow the vendor's records and test with real headers (How to add a third-party sender without breaking DMARC).

A worked example

example.com sends staff mail from Microsoft 365 and newsletters from a marketing platform on news.example.com:

example.com          TXT  "v=spf1 include:spf.protection.outlook.com ~all"
_dmarc.example.com   TXT  "v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com"

news.example.com     TXT  "v=spf1 include:spf.vendor.example ~all"
_dmarc.news.example.com  TXT  "v=DMARC1; p=none; rua=mailto:dmarc@example.com"

The apex covers staff mail. The newsletter subdomain has its own SPF record for the platform's Return-Path, plus the platform's DKIM selector records (not shown, because the values come from the vendor). It also has its own p=none record while you confirm the platform passes, and you can remove that record later to let it inherit the apex policy. Our stance is ~all for sending domains; Microsoft's own examples end in -all. spf.vendor.example is a placeholder for whatever include the vendor documents.

Special cases

  • Two mailbox platforms on one domain, such as Microsoft 365 and Google Workspace during a migration or a split organization. Both need to be in the SPF record, and both need aligned DKIM with distinct selectors. Platform steps are in DMARC for Microsoft 365 and DMARC for Google Workspace.
  • A SaaS product sending as its customers' domains. The SaaS becomes a source in every customer's DMARC reports, and each customer has to publish DKIM records for it. The alternative is to send from the SaaS's own subdomain with the customer's address in Reply-To, using a Header From under the sender's control. Neither approach is wrong, so choose per message type.
  • Departments that run their own parts of the DNS tree. How subdomain policies are discovered, and the limits of very deep names, is covered in Subdomain policy (sp).

Reporting when everything shares a domain

All streams on a domain report to the same rua address, unless a subdomain has its own record with a different one. Grouping rows by DKIM domain and selector, and by envelope domain, separates the services again (A field-by-field walk-through of a DMARC aggregate report, How to inventory sending sources). DMARC analysis tools, including ours, show results per sending source, which makes a crowded domain much easier to read. Reports show IPs and domains, not service names, so you still have to match each source to a service.

Ownership and change control

This part is our working method:

If BIMI comes later

BIMI is a later step, after every service on the domain passes DMARC and the domain is at enforcement. The "DMARC policy MUST be at enforcement on the organizational domain and subdomains," meaning p and sp at quarantine or reject. So a subdomain that's still at p=none for a new vendor affects BIMI readiness too. See What is BIMI, and why DMARC comes first and Why BIMI is not a deliverability shortcut.

Mistakes worth avoiding

  • A vendor's custom Return-Path subdomain with no SPF record.
  • Two SPF records after two teams each "added" their vendor.
  • A new subdomain for a vendor that still signs with its own d=, so the mail is still unaligned.
  • Enforcing the apex with sp unset while a vendor on a subdomain isn't aligned yet. The subdomain inherits p.
  • Retired services left in SPF, using up lookups.
  • Switching to strict alignment on a domain where services sign with subdomains.

The steps for adding each new service are in How to add a third-party sender without breaking DMARC, and what different tool types need is in Email sending platforms: SPF, DKIM and DMARC setup.

Free DMARC account

Not sure which sender is failing?

Connect your domain's DMARC reports and see every service that sends as your domain, and whether each one passes SPF, DKIM and DMARC.

  • Every sending source in one dashboard
  • SPF, DKIM and alignment results per sender
  • No XML files to read

Create a free DMARC accountTalk to an expert

FAQ

Can two services both use our apex domain?

Yes, as long as each has aligned DKIM, or an aligned Return-Path, and the SPF record stays a single valid record under 10 lookups.

Can a domain have multiple DKIM records?

Yes. Each key lives at its own selector, and many selectors can exist at once.

Should marketing use a subdomain?

Microsoft recommends a subdomain for services you don't directly control, and Google and Yahoo recommend separating message types. It's a design choice, not a DMARC requirement.

Does a subdomain need its own DMARC record?

Not necessarily. Without one, it inherits the policy from the parent domain. Publish one only when the subdomain needs a different policy or reporting address.

Does a subdomain need its own SPF record?

Yes, if it's used in MAIL FROM. The parent's SPF record doesn't cover it.