What a DMARC policy applies to
DMARC helps receiving mail systems evaluate messages that claim to be from a domain in the visible From address. A message passes DMARC when it passes SPF or DKIM and the passing domain aligns with that From domain. If neither mechanism passes with alignment, the published DMARC policy tells receivers what handling the domain owner requests. Receivers ultimately decide how to handle a message.
DMARC records are published as DNS TXT records under names beginning with _dmarc. For example, a record at _dmarc.example.com describes policy for mail claiming to be from example.com. Its p tag can request none, quarantine, or reject. The none setting requests no DMARC-based disposition, which makes it useful while checking what mail a domain sends.
The difference between p and sp
The optional sp tag specifies a policy for subdomains of an organizational domain when those subdomains do not publish their own DMARC records. Consider a TXT record at _dmarc.example.com containing "v=DMARC1; p=reject; sp=quarantine". If no more specific DMARC record exists, mail claiming to be from example.com is subject to p=reject, while mail claiming to be from news.example.com is subject to sp=quarantine.
If sp is omitted, subdomains without their own records inherit the p policy instead. Thus, a record containing "v=DMARC1; p=reject" also requests reject for those subdomains. The sp tag does not change the policy for the organizational domain itself; it provides a way to request different treatment for its subdomains.
Here, “organizational domain” means the registrable domain determined using public-suffix rules. For a typical name such as news.example.com, that is example.com. It is not simply whichever parent name is one level above the From domain.
When a subdomain has its own record
A subdomain can publish a DMARC record of its own. If _dmarc.news.example.com contains "v=DMARC1; p=none", that record supplies the policy for mail with a From address at news.example.com. It takes precedence over the sp=quarantine setting at _dmarc.example.com. The subdomain’s record needs its own p tag; it does not borrow p from the organizational domain.
DMARC discovery is not a step-by-step search through every parent name. A receiver checks the exact From domain first. If it finds no DMARC record there, it checks the organizational domain. For example, a record at _dmarc.news.example.com is not automatically the policy for mail from offers.news.example.com. If offers.news.example.com has no record of its own, the applicable policy is found at the organizational domain, example.com. This distinction matters when teams assume one delegated or intermediate subdomain controls everything beneath it.
Plan subdomain policies around real mail
Before requesting quarantine or reject, list the subdomains that appear in visible From addresses. Include mail sent by your own systems and by services you have authorized to send on your behalf. Check that each stream can pass aligned SPF or DKIM; merely having an SPF record or a DKIM signature does not guarantee DMARC alignment. A subdomain used for a newsletter, for instance, may have a different sending setup from the main domain.
Decide whether a shared inherited policy is appropriate. An sp tag is convenient when many subdomains should receive the same treatment, including subdomains with no mail program. A subdomain that needs a different policy can publish its own DMARC record. Starting with p=none or sp=none while reviewing authentication results can help reveal legitimate mail that would otherwise be affected. DMARC’s optional reporting settings may help with that review, but reports require careful interpretation.
When changing a policy, check both the intended DNS record name and its TXT value. A record placed at _dmarc.example.com is not the same as one placed at _dmarc.news.example.com. Also check for conflicting DMARC TXT records at the same name, which can prevent a usable policy from being discovered.
A quick way to reason through an example
For any message, first identify the domain in its visible From address. Look for a DMARC record at _dmarc followed by that exact domain. If a valid record is there, its p setting is the relevant policy. If not, find the organizational domain and look for its DMARC record. For a subdomain, use that record’s sp setting if present; otherwise use its p setting.
Finally, remember that the requested disposition matters when the message fails DMARC authentication. A message with aligned SPF or DKIM can pass DMARC regardless of whether the published policy says none, quarantine, or reject. Keeping policy discovery separate from authentication results makes subdomain behavior much easier to troubleshoot.



