TL;DR: Nonexistent subdomains now have an explicit DMARC policy path, giving brand owners a clearer way to signal how invented sender names should be handled, according to Valimail. Mailbox providers still have to interpret that signal consistently, or spoofed mail can keep slipping through on policy ambiguity.
Editorial analysis by NHI Mgmt Group, based on content published by Valimail: “What the new DMARC np= tag means for email security”.
Key questions
Q: Why do invented subdomain sender names increase phishing risk?
A: Because the visible From address can look legitimate even when the subdomain does not exist in DNS.
Q: What are the signs that DMARC policy is still ambiguous?
A: Ambiguity shows up when existing subdomains and nonexistent subdomains are handled the same way, when receiver behaviour varies widely, or when your organisation has no published rule for invented sender identities.
Q: How should security teams handle nonexistent subdomains in DMARC policy?
A: Treat nonexistent subdomains as part of your email identity surface, not as a harmless edge case.
Practitioner guidance
- Define explicit policy for nonexistent subdomains Review your subdomain namespace and decide whether invented sender names under your brand should be rejected, quarantined or ignored by receiver policy.
- Align p=, sp= and np= settings Make sure your organisational domain policy, existing subdomain policy and nonexistent subdomain policy tell a consistent story to mailbox providers.
- Test receiver behaviour before assuming enforcement Validate how your major mailbox partners handle np= and whether their filtering or rejection behaviour matches your published intent.
Bottom line: DMARC’s new np= tag addresses a real policy gap around nonexistent subdomains, which attackers can exploit for brand impersonation.
Glossary terms: Non-existent Subdomain, Subdomain Namespace, DMARC None Policy, Email Brand Impersonation
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
np= closes a DMARC ambiguity, but it does not change the core trust model. The control value is not in inventing a new anti-phishing mechanism. It is in giving domain owners a formal way to describe how receivers should treat mail that claims to come from a subdomain that does not exist. That makes policy intent more precise, which is useful because security outcomes often fail at the boundary between authentication and receiver interpretation. Practitioners should see np= as policy clarification, not as a standalone protection layer.
A question worth separating out:
Q: What is the difference between sp= and np= in DMARC?
A: sp= applies to real, existing subdomains that are part of your DNS namespace. np= applies to subdomains that do not exist at all. That separation matters because it lets domain owners state a policy for delegated subdomains and a different policy for invented ones that attackers may use in spoofed mail.
👉 Read our full editorial: DMARC np= adds explicit policy control for nonexistent subdomains