Checking DMARC policy...
Checking DMARC policy...
DMARC (Domain-based Message Authentication, Reporting, and Conformance) is a TXT record at _dmarc.<domain> that tells receivers what to do when SPF or DKIM checks fail and where to send aggregate reports.
Cached result — last checked 86s ago.
v=DMARC1; p=none; fo=1; rua=mailto:dmarc_agg@auth.returnpath.net,mailto:dmarc-rua@yandex.ru; ruf=mailto:dmarc_afrf@auth.returnpath.net
| v | DMARC1 | provided |
| p | none | provided |
| sp | default | |
| pct | 100 | default |
| adkim | r | default |
| aspf | r | default |
| fo | 1 | provided |
| rua | mailto:dmarc_agg@auth.returnpath.net, mailto:dmarc-rua@yandex.rurua= is the mailto address where receivers send daily aggregate XML failure reports. Learn more → | provided |
| ruf | mailto:dmarc_afrf@auth.returnpath.net | provided |
These addresses are published by the domain owner in their public DMARC DNS record. To request removal, contact privacy@relaymetry.com.
Move to p=quarantine once aggregate reports show no legitimate-but-unaligned mail for 2+ weeks per RFC 7489 §6.7.
Learn how to fix this →The policy values p=none / p=quarantine / p=reject move from observation to enforcement. p=none reports issues without acting; p=quarantine routes failing mail to spam; p=reject blocks it outright. The pct= modifier scales enforcement (start at low pct=, ramp up).
Start with p=none + a working rua= reporting address to gather data without disrupting mail flow. Once reports show clean SPF + DKIM alignment for legitimate senders, ramp pct from 25 to 100 under p=quarantine, then promote to p=reject. Without a reporting address, DMARC enforcement is blind.