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

Subdomain policy is not doing what we expected

When a subdomain's DMARC policy surprises you, the cause is usually one of four things. The parent's sp applied (or its p, if there's no sp). The subdomain has its own DMARC record, and that record's p won. You expected np to apply to a name that actually exists. Or the policy was fine, but the mail had no aligned SPF or DKIM pass: the subdomain didn't use the parent's records, and it has none of its own. Find out which record the receiver used before you change anything.

If you want the concept first, how sp and np work is in Subdomain policy (sp). This article starts from the symptom.

Step 1: find the record that actually applied

For mail from billing@news.example.com, a receiver works it out like this:

  1. Is there a valid record at _dmarc.news.example.com? If yes, that record's p applies. Any sp in it is ignored.
  2. If not, it walks up the DNS tree to the organizational domain's record and takes sp (or p) for a subdomain that exists, or np for a name that doesn't. If you care about non-existent names, set np explicitly. The current standard can be read two ways: one reading falls back from np to sp and then p; another can be read as going straight to p. Implementations already disagree, so set np yourself rather than relying on either reading (Subdomain policy (sp)).
  3. No record anywhere means DMARC doesn't apply.

So the first two lookups are always the same: query _dmarc.<the exact From domain> and _dmarc.<your organizational domain>. Many surprises become obvious once you have both records side by side.

Symptoms and likely causes

What you see Likely cause
Parent is p=reject, but a subdomain's mail isn't being enforced The parent has sp=none, or the subdomain has its own record with p=none. Its own p wins.
You set sp=reject on the parent, and one subdomain ignores it That subdomain has its own _dmarc record. Microsoft: you "can disrupt the inheritance of DMARC on a subdomain by creating a DMARC TXT record in that subdomain."
You added sp= to a subdomain's own record and nothing changed sp is ignored on DMARC records published on subdomains. That record's p is what counts.
A record at b.example.com doesn't govern a.b.example.com The receiver doesn't use the nearest record. It uses the organizational domain's, which is normally the one with the fewest labels, example.com.
np=reject didn't apply to a subdomain The name exists in DNS. Any record at the name, even just an A record or a null MX, makes it exist, so sp (or p) applies. np is only for names that return NXDOMAIN.
The whole record started behaving oddly after an edit A typo in p, sp, or np, such as sp=rejct. The current standard can be read two ways on what happens next (see below).
Subdomain mail fails DMARC even though the policy looks right The mail had no aligned SPF or DKIM pass. Policy is inherited; SPF and DKIM records are not. Under relaxed alignment, a parent DKIM signature can still pass.
A scanner reports no DMARC record on a subdomain Usually fine. Many scanners only query _dmarc.<subdomain>. If the parent's record covers it, receivers still apply the parent's policy.
Reports for one subdomain are missing That subdomain has its own record, and its reports go to that record's rua, or nowhere if it has none (Why DMARC reports do not arrive).

The causes in more detail

A record you forgot about

An easy one to miss is a _dmarc record on a subdomain left over from a test or a vendor setup, still at p=none. Because a subdomain's own p wins, that one record quietly exempts the subdomain from everything you set on the parent. Delete it if you want the parent to govern, or update its p. Microsoft notes that once DMARC is set up and the settings are "effectively identical for the parent domain and all subdomains," you can remove the subdomain records and rely on the parent's.

Deeper names and intermediate records

It's easy to expect a record at b.example.com to cover a.b.example.com. By default, it doesn't. The tree walk picks the organizational domain from the records it found, and without a psd tag that's the record with the fewest labels: example.com. So a.b.example.com gets example.com's sp or p. To give it a specific policy, publish a record at _dmarc.a.b.example.com.

A record with psd=n can mark itself as the organizational domain. That also changes which domains count as aligned with each other, so use it only if you understand that effect (Relaxed vs strict alignment).

Very deep names have a limit too. The walk makes at most eight queries, and domains longer than eight labels that need a specific policy must publish a record at that exact name.

np and names that exist

np covers names that don't exist in DNS at all. A subdomain with any record, including only an A record or a null MX, exists, so it gets sp or p. Don't read np as "subdomains that don't send mail."

Typos in sp or np

If a value is misspelled, the current standard can be read two ways. One reading is to ignore a bad tag and use its default. The other is that an invalid sp or np is treated like a missing p: act as p=none if the record has a valid rua, otherwise apply no DMARC processing at all. Implementations already disagree. Either way, one typo can weaken your whole policy, so check the record after every edit (DMARC tags explained: p, sp, np, adkim, aspf, rua, ruf, fo, and t).

Policy is inherited. SPF and DKIM aren't.

A subdomain gets the parent's DMARC policy, but not its SPF record or DKIM keys. A useful rule of thumb is that each subdomain used for sending needs its own SPF and DKIM setup, and in Microsoft 365 each subdomain you use to send email requires its own DKIM configuration. The protocol itself 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 under relaxed alignment. If a new marketing subdomain starts sending under an enforced parent with its own MailFrom or d=, or under strict alignment, its mail can be quarantined or rejected because nothing authenticates it, not because the policy is wrong.

Alignment mode matters here too. Under strict alignment, a DKIM signature for d=example.com doesn't align with mail from news.example.com. Under relaxed alignment, it does (Relaxed vs strict alignment). Vendor-specific alignment problems are in Third-party mail fails alignment.

Receivers can differ on edge cases

The current standard replaced the older public-suffix-list approach with the DNS tree walk. Google and Microsoft don't publish which method their receivers use, so on edge cases, such as psd tags or very deep names, two receivers may not agree.

sp=none and enforcement

p=reject; sp=none leaves every subdomain unprotected, and that is not enforcement, which covers the organizational domain and its subdomains. That also matters for BIMI (Subdomain policy (sp), BIMI requirements checklist). A record of p=quarantine; sp=none is sometimes used to isolate a marketing subdomain. Treat that as a time-boxed step while you fix the subdomain's authentication, not an end state.

Check it in order

  1. Query _dmarc.<exact From domain>. Any record there? What's its p?
  2. Query _dmarc.<organizational domain>. What are p, sp, and np? Any typos?
  3. Does the subdomain exist in DNS? That decides between sp and np.
  4. Does the subdomain have its own SPF record and DKIM signing for mail it sends?
  5. Check your aggregate reports for that subdomain's From domain: the policy published, the disposition, and the SPF and DKIM results (A field-by-field walk-through of a DMARC aggregate report).

If several services send from different subdomains, see Shared domains and multi-service setups.

Mistakes worth avoiding

  • A forgotten _dmarc record on a subdomain still at p=none from testing.
  • sp=none set "temporarily" and never raised.
  • Putting sp in a subdomain's record and expecting it to apply.
  • Expecting np to cover subdomains that exist.
  • Sending from a new subdomain without aligned SPF or DKIM for the names it actually uses.
  • Publishing a separate record on every subdomain by default. Subdomains inherit. Add one only when a subdomain needs a different policy or separate reports.

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

Why does my sp tag on the subdomain do nothing?

sp is ignored in records published on subdomains. That record's p applies.

A scanner says my subdomain has no DMARC record. Is that a problem?

Usually not, if the parent's record covers it. Check the parent's sp (or p).

Why is my subdomain's mail failing when the policy is correct?

Probably because the mail had no aligned SPF or DKIM pass. Policy is inherited; SPF and DKIM records are not. Check whether the subdomain sends with its own MailFrom or d=, and whether alignment is strict.

My parent is at p=reject. Why isn't a subdomain enforced?

Look for sp=none on the parent, or a record on the subdomain with its own p=none.