DMARCPROBLEM.comDMARC Record Analysis
Privacy Policy
When you use this site, we process the information you submit, such as domain names, selectors, email-authentication details, contact-form content, and any email address or IP address supplied for a sender test. We also process basic technical data such as request time, source IP address, request identifiers, browser security signals, and lookup results so the service can operate, diagnose faults, prevent abuse, and produce operational reports.
Form submissions are checked using Cloudflare Turnstile for spam prevention. Contact form submissions are sent using the AuthSMTP email service provider. Those providers may process technical request data and message content as part of delivering, protecting, and securing the service.
We do not sell submitted lookup data or contact-form content. Information may be retained in service logs or email records for troubleshooting, abuse prevention, security, and operational monitoring, and may be shared where necessary with service providers or where required to investigate abuse or comply with legal obligations.
Anti-Spam Policy
This site is provided to help domain owners, administrators, and email senders diagnose SPF, DKIM, DMARC, and related DNS configuration. It must not be used to support spam, phishing, spoofing, unsolicited bulk email, credential harvesting, or any other abusive activity. Advertising, promoting, or linking to this site using unsolicited messages is specifically prohibited.
Contact forms are for genuine questions about these services and email-authentication issues. Unsolicited commercial messages, automated submissions, misleading content, or attempts to abuse the forms may be blocked, ignored, logged, or reported where appropriate.
Validation and Liability
This DMARC checker inspects the policy record at the domain's _dmarc host and highlights policy, alignment, percentage rollout, and reporting-tag issues. It does not process aggregate report XML files or prove how every receiver will handle a specific message.
DMARC enforcement depends on SPF or DKIM alignment. A syntactically valid p=quarantine or p=reject policy can still cause delivery problems if legitimate senders are not aligned first.
Before changing p, sp, pct, rua, ruf, adkim, or aspf, confirm current authentication results from real mail, review reports where available, and obtain approval from your DNS and email administrators.
An incorrect DMARC policy can hide useful reporting, fail to protect the domain, or ask receivers to quarantine or reject legitimate mail before SPF and DKIM alignment are ready.
We aim to keep the site accurate and available, but we do not guarantee uninterrupted access, error-free operation, or compatibility across every browser and device at all times.
Use of this site is at your own discretion and risk. External services used by the site, including security or email providers, may affect availability or functionality from time to time.