DMARC record check
Explains how to read a DMARC record, assess SPF and DKIM alignment, and make a staged policy decision without treating a DNS record as proof of mail delivery.
Quick answer#
DMARC is a DNS policy at _dmarc.yourdomain.com. It tells receiving mail systems what to do when a message fails DMARC and where aggregate reports may be sent. A record check can assess syntax and the published policy; it cannot prove that every sending service is aligned or that a provider will deliver a particular message.
What to review#
v=DMARC1 and valid tag syntaxp=none, quarantine, or rejectrua= and any required external-destination authorisationaspf and adkim)sp=Use the result carefully#
A p=none policy is commonly used to observe traffic while a sender inventory is being built; it is not, by itself, a configuration error. Likewise, an rua address is useful only when its reports are collected and reviewed. Check the current requirements of each mailbox provider you send to, because bulk-sender rules and thresholds can change.
A staged remediation path#
FAQ#
Does DMARC require both SPF and DKIM to pass?#
No. DMARC can pass when either SPF or DKIM passes and that mechanism aligns with the visible From domain.
What is a good rua address?#
Use an address or reporting service that you control and actively monitor. If it is hosted on another domain, follow the DMARC external-reporting authorisation rules before relying on it.
Related#
Related Articles
SPF record check
Parses your SPF record, counts DNS lookups (10 max), and warns before you hit the RFC 7208 limit that silently breaks deliverability.
DKIM record check
Verifies DKIM selector records exist and use ≥1024-bit keys — the invisible half of email deliverability that most teams forget.
DNS MX record check
Monitors MX records so a fat-fingered mail edit or expired provider does not silently break customer email.
Certificate Transparency Monitoring
Monitor SSL certificate issuance and detect unauthorized certificates.