Compliant
Messages that satisfy DMARC through aligned SPF or DKIM and do not carry stronger contradictory evidence.
Aggregate and failure report intelligence
Mailbox providers send aggregate reports as machine-readable XML. DMARC123 imports that evidence, consolidates related rows, classifies sending sources, and presents domain-level results without hiding the authentication details behind the totals.
Compliance categories
DMARC123 uses independent category toggles so administrators can compare any combination of expected, questionable, threatening, or forwarded traffic.
Messages that satisfy DMARC through aligned SPF or DKIM and do not carry stronger contradictory evidence.
Traffic that is not clearly malicious but contains configuration, alignment, or source-identity questions worth examining.
Unrecognized or suspicious sources, authentication failures, or actionable blacklist evidence requiring investigation.
Traffic identified through receiver policy overrides or forwarding evidence rather than inferred from authentication failure alone.
Related report rows can represent the same sender, infrastructure, authentication pattern, or recipient path. DMARC123 consolidates those records while retaining counts, variants, and evidence for drilldown.
Reverse DNS and source IPs identify the actual sending or receiving infrastructure. Authentication domains are retained as evidence but are not used as a substitute for infrastructure identity.
Scheduled workers cache SpamCop, Spamhaus DQS, and Abusix results. Report pages never perform request-time DNSBL lookups, keeping the interface predictable and the evidence auditable.
Built and operated by PM Technologies
Existing users can sign in. Organizations evaluating DMARC123 can contact PM Technologies to discuss account access and deployment.