ActiScore

MSPs

Does My DMARC Policy Protect My Subdomains Too?

Rodney Hall, COO— AI-assisted and reviewed prior to publication.

Photo for: Does My DMARC Policy Protect My Subdomains Too?

Your DMARC policy protects subdomains by default when they inherit your organizational domain's p= policy. The sp= tag lets you set a different policy for subdomains, such as keeping them at sp=none while enforcing p=reject on your root domain, or closing spoofing gaps by setting sp=reject when subdomains never send mail.

What the sp tag controls

The sp tag sets the DMARC policy for all subdomains that don't publish their own record, using the same values as the p tag: sp=none, sp=quarantine, or sp=reject (valimail.com). If you don't set sp, subdomains inherit the p policy. The tag belongs in your organizational domain's DMARC record at _dmarc.yourdomain.com, not on the subdomain itself.

A DMARC record published directly at a subdomain always takes precedence over the organizational domain's sp= tag (dmarcreport.com). If mail.yourdomain.com has its own _dmarc.mail.yourdomain.com TXT record with p=none, the root's sp=reject never applies to that subdomain. The guide (/guide) shows where policy discovery looks first and when it falls back.

Why is a made-up subdomain a spoofing gap?

Under the current DMARC standard, an attacker can fabricate any subdomain of your domain and send spoofed email from it (dmarcreport.com). An attacker can send spoofing emails from a non-existent subdomain (no MX record) of well-known email services, and the spoofing email only gets a "None" verification result (arxiv.org). If your record is v=DMARC1, p=reject, rua=mailto:dmarc@yourdomain.com and you omit sp, the subdomain inherits p=reject and the gap closes. If you add sp=none, the gap reopens. A spoofer invents a subdomain that was never created, such as random-invoice.brand.com or payroll.brand.com, and the np=reject blocks the non-existent-subdomain spoof that the permissive sp=none would otherwise have let through (dmarcguard.io).

The np tag, introduced in RFC 9989 (May 2026), explicitly handles subdomains that do not exist in DNS. np=reject is the DMARCbis (RFC 9989) fix for non-existent-subdomain spoofing, but it is not yet enforced at major receivers. Setting sp=reject today is the enforceable control.

How do you set a stricter subdomain policy without breaking a real subdomain?

If a subdomain sends legitimate mail, give it its own DMARC record before tightening the organizational domain's sp. The primary reason to publish a subdomain DMARC record is to apply a different policy or reporting address for a specific subdomain than what is set for the organizational domain, such as a p=reject policy on a sensitive transactional subdomain but a p=none policy on a marketing subdomain while you're still monitoring its traffic (suped.com).

The sequence:

  1. Publish _dmarc.marketing.yourdomain.com TXT v=DMARC1, p=none, rua=mailto:dmarc-marketing@yourdomain.com
  2. Confirm the subdomain's mail passes SPF or DKIM alignment by reviewing aggregate reports for that subdomain
  3. Tighten the subdomain's own policy once alignment holds
  4. Set sp=reject on the organizational domain to cover everything else

A policy of p=reject on example.com applies to every subdomain that lacks its own _dmarc record, and plenty of teams have published a strict root policy and quietly broken a subdomain they forgot was sending. The free AI-visibility check (/check) surfaces DNS and authentication issues before they block mail.

When to use sp versus a dedicated subdomain record

Use sp when every subdomain should follow the same rule. If marketing.example.com sends through one tool (your newsletter platform) and your main domain sends through another (your transactional email provider), each one has different authentication settings, and you might want a stricter DMARC policy on one than the other, especially while you are rolling out a new provider. The optional sp tag can be set on the organizational domain only, and it allows you to treat subdomains differently from the organizational domain without having to publish a DMARC record on each subdomain.

Publish a subdomain-specific record when that subdomain needs different reporting addresses, a separate rollout timeline, or uses a third-party ESP that cannot sign DKIM with your organizational domain. Publish a separate DMARC record at _dmarc.sub.yourdomain.com when a subdomain needs different reporting addresses, pct, or alignment modes (for example, a marketing subdomain still onboarding a vendor). Leave sp unset or at the same enforcement level as p when all subdomains share authentication infrastructure.

The MSP rollout pattern

Start the organizational domain at p=none with no sp tag, so every subdomain inherits monitoring mode. Review aggregate reports at ActiScore's pricing (/pricing) plans, which include DMARC checks in the Security category alongside SPF, DKIM, and TLS certificate health. Once alignment holds across legitimate senders, move p to quarantine, then reject. If a client subdomain still fails, carve out a dedicated subdomain record at p=none and fix authentication there before merging back into the stricter organizational policy.

If even a single subdomain is not at enforcement, the entire domain is not at enforcement. Set sp=reject once you have accounted for every legitimate sending subdomain, either by aligning it or publishing its own DMARC record. That closes the spoofing gap on every subdomain an attacker might invent.

Common questions

Do subdomains inherit my DMARC policy automatically?

Yes, subdomains inherit your organizational domain's p= policy by default when they don't publish their own DMARC record. If your root domain has p=reject and you haven't set an sp tag or published a subdomain-specific record, all subdomains automatically get the reject policy. Any DMARC record published directly at a subdomain always takes precedence over the organizational domain's sp tag, so a subdomain with its own _dmarc record will follow its own policy instead of inheriting yours.

What is the sp tag in DMARC and when should I use it?

The sp tag sets the DMARC policy for all subdomains that don't publish their own record, using the same values as the p tag: sp=none, sp=quarantine, or sp=reject. Use sp when every subdomain should follow the same rule that's different from your root domain policy, such as keeping subdomains at sp=none while enforcing p=reject on your organizational domain during rollout, or setting sp=reject to close spoofing gaps when subdomains never send mail. If you don't set sp, subdomains simply inherit whatever policy you've set with the p tag.

Can attackers spoof made-up subdomains of my domain?

Under the current DMARC standard, an attacker can fabricate any subdomain of your domain and send spoofed email from it, even if that subdomain has no MX record or DNS entry. If your record has sp=none or you omit sp while keeping p=none, the gap stays open and a spoofer can invent subdomains like random-invoice.brand.com or payroll.brand.com. Setting sp=reject closes this gap by applying a strict policy to every subdomain that doesn't have its own DMARC record, blocking non-existent-subdomain spoofs that a permissive policy would let through.

How do I protect subdomains without breaking legitimate email?

If a subdomain sends legitimate mail, publish its own DMARC record at _dmarc.subdomain.yourdomain.com before tightening the organizational domain's sp tag. Start the subdomain at p=none with its own reporting address, review aggregate reports to confirm mail passes SPF or DKIM alignment, then tighten the subdomain's policy once alignment holds. After securing each sending subdomain individually, you can safely set sp=reject on the organizational domain to cover all remaining subdomains and close spoofing gaps without breaking any real email flows.

Should I use sp or publish separate subdomain DMARC records?

Use sp when every subdomain should follow the same rule, such as sp=reject to block spoofing on all non-sending subdomains at once. Publish a subdomain-specific record when that subdomain needs different reporting addresses, a separate rollout timeline, uses a third-party ESP that cannot sign DKIM with your organizational domain, or requires different alignment modes or pct values. If marketing.example.com sends through one platform and your main domain through another with different authentication settings, each should have its own DMARC record so you can enforce different policies and monitor them independently.