What is a DMARC record?
DMARC builds on SPF and DKIM to tell receivers what to do with mail that fails authentication, and where to send reports. A policy of 'p=none' only monitors; 'quarantine' and 'reject' actually protect your domain from spoofing. IPeek reads the record at _dmarc.your-domain, parses every tag and grades the policy strength.
How DMARC works with alignment
DMARC is a TXT record at _dmarc.your-domain starting with v=DMARC1. It passes when a message passes SPF or DKIM and that authenticated domain aligns with the visible From domain. Alignment is the key: spoofers can pass raw SPF or DKIM on their own domain, but they can't align it with yours. A record like v=DMARC1; p=reject; rua=mailto:reports@your-domain; adkim=s; aspf=s enforces rejection and demands strict alignment for both DKIM and SPF.
Reading p=none, quarantine, and reject
The p tag sets your policy. p=none monitors only — mail still flows, but you collect reports to see who sends as you. p=quarantine routes failing mail to spam, and p=reject blocks it outright, the strongest protection against spoofing. The pct tag can ramp enforcement gradually (for example pct=25), and sp sets a separate policy for subdomains. Start at none to gather data, then tighten to quarantine and reject once your legitimate senders pass. IPeek grades how strong your current policy is.
DMARC reports and the rua tag
DMARC's reporting is what makes it actionable. The rua tag names a mailbox that receives daily aggregate XML reports summarizing which sources sent mail as your domain and whether they passed SPF, DKIM, and alignment. Use these reports to find legitimate senders you forgot to authorize before tightening your policy. The optional ruf tag requests forensic (per-failure) reports, though most receivers no longer send them for privacy reasons. Without rua, you're enforcing policy blind.