DMARC for Subdomains: What Every Admin Should Know
Subdomains inherit parent DMARC policy unless you say otherwise. Here’s what every admin needs to know about sp=, per-subdomain records, and edge cases.
Archive
Subdomains inherit parent DMARC policy unless you say otherwise. Here’s what every admin needs to know about sp=, per-subdomain records, and edge cases.
DMARC p=none is monitor mode — receivers report failures but deliver everything. Here’s exactly what it does, why it’s a starting point, and when to move past it.
DMARC p=reject is the end state — receivers bounce failing mail at SMTP. Here’s what it means, when to deploy it, and how to do so without breaking real mail.
DMARC aggregate reports are the daily XML summaries receivers send back. Here’s what they contain, how to read them, and what the fields actually mean.
DMARC failure reports — also called forensic reports — give per-message detail. Here’s what’s in them, when to enable them, and when to skip them entirely.
DMARC alignment is what makes SPF and DKIM meaningful. Here’s how relaxed vs strict alignment works and when each is the right choice.
DMARC tells the world’s mailbox providers which mail from your domain is real. Learn what it is, how SPF and DKIM feed into it, and the safe rollout path.
The DMARC `p` tag tells receivers what to do with failing mail. None vs. quarantine vs. reject — what each means, when to move, and how to do it without breaking real mail.
A DMARC record is a single line of DNS text. This guide walks through every tag, what it does, and how to read a real-world example line by line.
DMARC without the acronyms: what it does, why your company needs it, and what your IT team is actually working on when they bring it up. Built for non-engineers.