DNS Record Explainer

v=DMARC1
Version tag. Always "DMARC1". This tells receivers the record follows DMARC spec.

p=none
Policy directive. Tells receivers what to do with mail that fails DMARC checks (SPF or DKIM alignment). "none" means monitor only—don't reject or quarantine, just report. Receivers will still deliver the message.

rua=mailto:[email protected]
Reporting URI for aggregate reports. DMARC receivers send you a compressed XML summary once per day (or per reporting interval) of all mail claiming your domain. Reports include pass/fail counts, IP addresses, and sender breakdown. The mailbox must exist and accept mail from external sources or reports won't arrive.

• p=none is a monitoring-only policy. You won't block anything. Move to p=quarantine or p=reject once you've verified legitimate senders pass DMARC checks and SPF/DKIM are properly aligned.

• rua address points to example.com, which almost certainly doesn't accept mail for [email protected] unless you own that domain and configured it. If reports don't arrive after 24 hours, check: mailbox existence, SPF records allowing report senders, spam filters.

• No ruf (forensic report) URI set. Optional, but useful during initial rollout to see failure samples in real time instead of waiting for aggregates.

• No subdomain policy (sp=) or alignment mode (aspf=/adkim=) specified. Defaults are permissive—subdomain mail uses the main policy, and alignment is "relaxed" (allows subdomains to pass). This is safe for p=none but tighten these later.

DMARC ties SPF and DKIM together, ensuring domain name matches the actual sender authentication. Without it, attackers can pass SPF or DKIM checks using lookalike domains (example.com vs examp1e.com). Reports tell you who's sending mail as your domain—critical for spotting spoofing and phishing. p=none lets you collect data risk-free before enforcement.