A DMARC record on your domain also covers its subdomains. sp= gives them a policy of their own; np=, new in RFC 9989, gives one to subdomains that do not exist at all — the ones spammers invent.
| Syntax | sp=none|quarantine|reject np=none|quarantine|reject |
| sp= when absent | p= applies to subdomains |
| np= when absent | sp= if present, otherwise p= |
| np= | New in RFC 9989 (May 2026) |
| Defined in | RFC 9989 |
What it does
A subdomain with its own DMARC record uses that record. One without falls back to the organisational domain’s record, and then sp= applies if it is there, p= if not.
np= covers names that do not exist in DNS at all. Mail “from” billing.example.com, when billing.example.com was never created, is almost always forged; np=reject lets you refuse it even while your real subdomains are still on a gentler policy.
Examples
v=DMARC1; p=reject; sp=quarantine; np=reject; rua=mailto:dmarc@example.com
The domain: reject. Real subdomains without their own record: quarantine. Subdomains that do not exist: reject.
See what your own DMARC record says
Every term of your published record, read and explained — including this one.
Common mistakes
- sp=none under p=reject, which leaves every subdomain open to forgery.
What we recommend
Once your main domain is at reject, set np=reject, and bring sp= up to match as you confirm which subdomains send mail.
Sources
Checked on 25 September 2026 against these official sources: