Subdomain policy (sp)
One DMARC record on your organizational domain, say example.com, also covers its subdomains, unless a subdomain publishes its own record. The sp tag lets you give subdomains that exist, such as mail.example.com, a different policy from the parent. The newer np tag covers subdomains that don't exist at all. If you set neither, subdomains get the same policy as p.
_dmarc.example.com. TXT "v=DMARC1; p=reject; sp=quarantine; np=reject; rua=mailto:dmarc-reports@example.com"
Here example.com asks for reject, existing subdomains for quarantine, and made-up subdomains for reject.
Which policy a subdomain actually gets
Say a message arrives from billing@news.example.com. A receiver works it out like this (simplified):
- Look for the subdomain's own record at
_dmarc.news.example.com. If there is one, itspapplies, and you're done. - If not, walk up the DNS tree to the organizational domain's record,
_dmarc.example.com. The walk is capped at eight queries. - Pick the tag from the parent record:
- The subdomain exists in DNS: use
spif set, otherwisep. - The subdomain doesn't exist: usenpif set, otherwisesp, otherwisep. - No record anywhere: DMARC doesn't apply.
The fallback in step 3 can be read two ways. One reading falls back from np to sp and then p. Another can be read as falling back to p whenever np is absent, even if sp is set. If you care about non-existent names, set np explicitly so the result doesn't depend on which reading a receiver uses.
If you don't set a subdomain policy in the record, subdomains inherit the DMARC policy set for the parent domain. The parent record automatically covers all subdomains (including nonexistent subdomains) that don't have their own DMARC TXT record, and you can break that inheritance by publishing a record on the subdomain.
sp only works in the parent record
sp will be ignored for DMARC records published on subdomains. If _dmarc.news.example.com contains sp=reject, it does nothing. The policy for news.example.com itself comes from that record's p.
sp and np take the same values as p: none, quarantine, or reject. The other tags are in DMARC tags explained: p, sp, np, adkim, aspf, rua, ruf, fo, and t.
sp vs np
sp |
np |
|
|---|---|---|
| Covers | Subdomains that exist in DNS | Names that don't exist (NXDOMAIN) |
| Example | news.example.com with an A, MX, or TXT record |
invoice-2026.example.com, never created |
| If missing | Falls back to p |
Falls back to sp, then p |
np started as an experimental tag and is now part of the current standard. It's useful because spoofers like inventing names under a real domain. There's nothing at the name to check, but the parent's policy still applies.
What "doesn't exist" means
A name is non-existent when the DNS lookup returns NXDOMAIN. If any record exists at the name, the name exists. So:
- A subdomain with only an A record exists, and gets
sp(orp). - A subdomain with a null MX, which says "this name takes no mail," also exists, and gets
sp(orp), notnp. - If a name returns NXDOMAIN, every name below it doesn't exist either.
Don't read np as "subdomains without mail." It's strictly about names that aren't in DNS.
Receiver support for np since the current standard came out hasn't been measured, so treat it as an added layer, not your only protection.
Do subdomains need their own DMARC record?
No, not by default. A subdomain without its own record inherits from the parent through sp, np, or p. Publish a separate record when a subdomain needs:
- A different policy. For example, a newly added marketing subdomain you want at
p=nonewhile you check its reports. - Separate reports. Aggregate reports are produced per policy domain, so a subdomain with its own record and
ruagets its own reports. Without one, its mail shows up under the parent's reports (A field-by-field walk-through of a DMARC aggregate report). - A very deep name. Because the tree walk stops after eight queries, domains longer than eight labels that need a specific policy must publish a record at that exact name.
Microsoft also suggests sending bulk mail from services "that aren't under your direct control" from a subdomain, such as marketing.example.com, and rolling out DMARC subdomain by subdomain, "saving the parent domain for last." Once everything is aligned and you want the same policy everywhere, it notes you can remove subdomain records and let the parent cover them.
Inheritance covers policy, not authentication
A subdomain inherits a DMARC policy. It doesn't inherit SPF or DKIM. A useful rule of thumb is that each subdomain used for sending needs its own SPF and DKIM setup, 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 under relaxed alignment. In Microsoft 365, each subdomain you use to send email still needs its own DKIM configuration (DMARC for Microsoft 365). The multi-service detail is in Shared domains and multi-service setups.
sp=none and enforcement
A common record looks like this:
_dmarc.example.com. TXT "v=DMARC1; p=reject; sp=none; rua=mailto:dmarc-reports@example.com"
The parent is at reject, but every subdomain is at none, so anyone can send as anything.example.com with no policy behind it. Enforcement means the organizational domain and all subdomains below it are not at p=none. This record isn't there yet.
That matters for BIMI. DMARC must be at enforcement on the organizational domain and its subdomains, so sp=none keeps you out (BIMI requirements checklist).
sp=none is fine as a temporary step while you check which subdomains send. Plan to raise it.
Common patterns
| Goal | Record at _dmarc.example.com |
|---|---|
| Same policy everywhere | v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@example.com |
| Parent enforced, subdomains still being checked (temporary) | v=DMARC1; p=quarantine; sp=none; rua=mailto:dmarc-reports@example.com |
| Lock down made-up names | v=DMARC1; p=quarantine; np=reject; rua=mailto:dmarc-reports@example.com |
| One subdomain with its own policy | Keep the parent record, and publish _dmarc.news.example.com with its own p and rua |
Before you set sp=reject or np=reject, confirm in your reports which subdomains really send mail. A stricter subdomain policy blocks a forgotten system just as it blocks a spoofer. The same per-domain caution about p=reject covered in What is DMARC and how it works applies here. The staged rollout is in A safe rollout: p=none to quarantine to reject.
Mistakes worth avoiding
p=reject; sp=noneand assuming subdomains are protected.- Putting
spin a subdomain's own record. It's ignored there. - Publishing a broken subdomain record, such as one missing
v=DMARC1. A TXT that isn't a DMARC record should be skipped, and the tree walk should continue to the parent. A record that looks valid but has a badp,sp, ornpvalue is the typo case below. Check the record after every change. - Typos in
spornpvalues. The current standard can be read two ways, and implementations already disagree. Check the record after every edit. - Treating null-MX subdomains as non-existent. They exist, so
spapplies, notnp. - Forgetting unused domains. To publish DMARC for registered domains you don't send from, including your
*.onmicrosoft.comdomain if you don't use it for mail.
If a subdomain policy isn't behaving the way you expected, see Subdomain policy is not doing what we expected.
Free DMARC account
Turn raw DMARC reports into a readable dashboard
Point your rua address to our platform and read the results by sender and source instead of opening XML files.
- Results grouped by sending source
- SPF, DKIM and alignment results per sender
- The original XML reports are still there to download
FAQ
Do I need a DMARC record on every subdomain?
No. Subdomains without their own record inherit from the parent through sp, np, or p. Add one when a subdomain needs a different policy or separate reports.
What's the difference between sp and np?
sp covers subdomains that exist in DNS. np covers names that return NXDOMAIN.
If I don't set sp, what do subdomains get?
Your p value.
Why does sp in my subdomain's record do nothing?
sp is only read from the organizational domain's record.
Does p=reject with sp=none count as enforcement?
Not under the current definition of enforcement, and not for BIMI.
Is subdomain alignment the same as subdomain policy?
No. Policy decides what happens to failing mail. Alignment decides whether a subdomain's SPF or DKIM pass counts for the From domain; under relaxed alignment, it does (Relaxed vs strict alignment).