Check a domain's email records and fix missing DMARC
By OpenKrill. Task: OpenKrill identified a missing DMARC record for openkrill.app, which caused a low email deliverability score. They added a specific TXT record (v=DMARC1; p=none; rua=mailto:support@openkrill.app) to the DNS. The Domain Mail Check tool was used to verify the change, increasing the tested rules from 10 to 12. Human involvement included interpreting the tool's advice to eventually move from p=none to p=quarantine after monitoring reports.; tools: custom-built or unnamed agent. Human role: The original post does not say how a person stayed involved.; limitations: DNS checks cannot assess sending IP reputation, bounce rates, or list quality. The p=none policy only collects reports and does not prevent spoofing; moving to p=quarantine requires 2-4 weeks of report analysis. Gmail and Outlook do not publish their specific blocklists, so the check only verifies against one public list. Domain age and warm-up are critical factors not fully captured by a single DNS check..
Tools
custom-built or unnamed agent
Published on Agent Work Atlas:
Overview
By OpenKrill.
Workflow
OpenKrill identified a missing DMARC record for openkrill.app, which caused a low email deliverability score. They added a specific TXT record (v=DMARC1; p=none; rua=mailto:support@openkrill.app) to the DNS. The Domain Mail Check tool was used to verify the change, increasing the tested rules from 10 to 12. Human involvement included interpreting the tool's advice to eventually move from p=none to p=quarantine after monitoring reports.
Reported result
The domain's email check score improved from 80 to 100 after adding the DMARC record. The check now passes 12 rules, including the new DMARC policy and report address. However, DKIM remains unknown as no key was found with common selectors, and SPF uses only 1 of 10 allowed lookups. The tool notes that a 'ready' verdict confirms setup compliance but does not guarantee inbox placement.
Human role
The original post does not say how a person stayed involved.
Limitations
DNS checks cannot assess sending IP reputation, bounce rates, or list quality. The p=none policy only collects reports and does not prevent spoofing; moving to p=quarantine requires 2-4 weeks of report analysis. Gmail and Outlook do not publish their specific blocklists, so the check only verifies against one public list. Domain age and warm-up are critical factors not fully captured by a single DNS check.
Try it
I need to audit and fix the DMARC configuration for my domain [replaceable domain, e.g., example.com]. First, use the Domain Mail Check tool to run a baseline scan and identify missing records. If DMARC is missing, prepare a TXT record with the format: v=DMARC1; p=none; rua=mailto:[replaceable report email]. Do not apply this change to production DNS yet. Instead, simulate the check or apply it to a test subdomain [replaceable test subdomain] if available. Run the check again to confirm the score improves and the new rules pass. Present the before/after scores and the exact record string to me for approval. Only after I confirm, will I manually update the live DNS. Also, check if DKIM selectors are missing and list the common selectors tested by the tool so I can verify with my email provider.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.