What This Tool Does
This DMARC record checker and generator queries live _dmarc DNS TXT records or parses pasted raw v=DMARC1 strings to validate RFC 7489 syntax and identifier alignment. Enter a public domain name, paste a raw DMARC policy, or select one of the preset test targets (such as google.com, paypal.com, cloudflare.com, github.com, or a weak p=none policy) to run an immediate audit. Alongside the _dmarc record, the tool queries the domain's root v=spf1 TXT record, retrieves up to four primary Mail Exchanger (MX) hosts, and performs live cross-domain DNS verification (<domain>._report._dmarc.<external-host>) for any external aggregate (rua) or forensic (ruf) reporting addresses.
The audit output assigns a security grade from A+ to F, displays a tag-by-tag breakdown table (v, p, sp, adkim, aspf, pct, rua, ruf, fo, and ri) with status badges (OK, WARN, ERR), and lists specific RFC 7489 syntax errors or configuration warnings. Below the auditor, an interactive DMARC Policy Builder lets you configure main and subdomain policies, strict or relaxed DKIM/SPF alignment, rollout percentage (1% to 100%), and reporting URIs to generate and copy a ready-to-publish DNS TXT record.
Email Authentication Engineering: RFC 7489 DMARC Policies, Identifier Alignment, and Anti-Spoofing Architecture
When an email arrives in a recipient's inbox, the Simple Mail Transfer Protocol (SMTP, RFC 5321) provides zero built-in verification of the sender's identity. Just as anyone can write any return address on a paper envelope, any server on the internet can transmit an email claiming to originate from [email protected]. While SPF (Sender Policy Framework, RFC 7208) and DKIM (DomainKeys Identified Mail, RFC 6376) were created to authenticate sending servers and cryptographic signatures, neither protocol protects the address the human recipient actually sees in their email client: the RFC 5322 `From:` header.
DMARC (Domain-based Message Authentication, Reporting, and Conformance, RFC 7489) bridges this critical security gap. Our DMARC Record Checker & Policy Builder resolves your domain's `_dmarc` DNS TXT record in real time, evaluates root SPF and MX records, validates external aggregate reporting (`_report._dmarc`) authorization, and grades your anti-spoofing posture from `A+` to `F`.
1. How DMARC Identifier Alignment Works (`adkim` and `aspf`)
An email can pass both SPF and DKIM checks and still be a dangerous phishing spoof! Consider an attacker who registers `evil-mailer.net`, sets up valid SPF and DKIM records for `evil-mailer.net`, and sends an email where the SMTP envelope `Return-Path` is `[email protected]`, the DKIM `d=` signature is `evil-mailer.net`, but the visible header shown to the victim is `From: Billing <[email protected]>`. Without DMARC, receiving mail servers see `SPF=PASS` and `DKIM=PASS` (for `evil-mailer.net`) and deliver the forged email.
DMARC defeats this attack through Identifier Alignment, which requires that the authenticated SPF domain or DKIM signing domain match the visible `RFC5322.From` organizational domain:
- Relaxed Alignment (`adkim=r` / `aspf=r`, Default): The organizational root domain of the `RFC5322.From` header must match the organizational domain of the DKIM `d=` tag or SPF `MailFrom` domain. For example, if the visible sender is `[email protected]`, an SPF Return-Path of `[email protected]` passes relaxed alignment because both share the organizational root `example.com`.
- Strict Alignment (`adkim=s` / `aspf=s`): Requires an exact, character-for-character Fully Qualified Domain Name (FQDN) match. If `From:` is `[email protected]`, a DKIM signature with `d=sub.example.com` will fail strict alignment.
2. The Three DMARC Enforcement Policies: `none`, `quarantine`, and `reject`
Every DMARC record must declare a primary policy tag (`p=`) immediately following `v=DMARC1;` (and optionally a subdomain policy tag `sp=`):
- Monitoring Mode (`p=none`): Instructs receiving mail providers (Gmail, Microsoft 365, Yahoo) to take no enforcement action when an email fails DMARC alignment, delivering spoofed messages normally while sending daily XML aggregate reports to the address specified in `rua=`. Warning: `p=none` provides zero active protection against phishing and should only be used temporarily during initial deployment.
- Quarantine Mode (`p=quarantine`): Instructs receivers to treat unaligned messages as suspicious and route them directly to the recipient's Spam or Junk folder rather than the primary inbox.
- Reject Mode (`p=reject`): The gold standard of email security. Receivers block unauthorized emails outright during the SMTP transaction (`550 5.7.1 Unauthenticated email is not accepted`), preventing spoofed messages from ever reaching users.
3. Aggregate (`rua`) vs. Forensic (`ruf`) Reporting & External DNS Authorization
When you configure `rua=mailto:[email protected]`, participating mail servers send daily gzipped XML reports detailing every IP address that attempted to send mail as your domain, alongside its SPF and DKIM pass/fail results. However, if you send reports to an external domain (for example, `domain-a.com` specifies `rua=mailto:[email protected]`), RFC 7489 Section 7.1 mandates an external DNS verification check to prevent attackers from flooding third-party inboxes with report spam.
Specifically, the receiving mail server queries the TXT record at:
domain-a.com._report._dmarc.dmarc-vendor.net
Unless `dmarc-vendor.net` publishes a `v=DMARC1` TXT record at that exact subdomain, receivers will silently drop your aggregate reports. Our auditor automatically performs this cross-domain DNS verification for every external `rua` and `ruf` URI in your policy.
4. Safe DMARC Deployment Roadmap: From `pct=10` to BIMI Readiness
Jumping straight to `p=reject` on a complex corporate domain can accidentally block legitimate third-party mail streams (such as CRM platforms, ticketing desks, or payroll providers). Follow a phased rollout: start with `v=DMARC1; p=none; rua=mailto:[email protected]`, inspect XML aggregate reports for 14 days to authorize all legitimate senders via SPF/DKIM, transition to `p=quarantine; pct=25`, increase `pct` to `100`, and finally lock down the domain with `p=reject; sp=reject;`. Note that an enforced policy (`p=quarantine; pct=100` or `p=reject`) is a mandatory prerequisite for BIMI (Brand Indicators for Message Identification) to display your verified brand logo in Gmail and Apple Mail.