Inspect any domain's _dmarc TXT record in real time, verify its enforcement policy (none, quarantine, or reject), and check aggregate reporting (rua).
SPF and DMARC are DNS records that prove your email is really from you. Without them, anyone can spoof your domain, and mailbox providers are far more likely to send your mail to spam. Gmail and Yahoo require bulk senders to authenticate with SPF, DKIM and DMARC. A missing or p=none DMARC means you have no protection against spoofers and no enforcement.
Authentication gets your mail accepted; list quality keeps it in the inbox. Verify addresses with the email validator, clean a whole list with the bulk email cleaner, and check the mail servers with the MX lookup tool. For the full breakdown, read SPF, DKIM & DMARC explained.
SPF (Sender Policy Framework) is a DNS TXT record that lists which servers may send mail for your domain. DMARC builds on SPF and DKIM: it tells receivers what to do with mail that fails authentication (p=none monitors, p=quarantine sends to spam, p=reject blocks) and where to send reports. Together they stop spoofing and protect deliverability.
Enter your domain above and click Check Records. This tool queries DNS live for the SPF TXT record on the domain and the DMARC TXT record at _dmarc.yourdomain, then parses the policy and key settings. No account is required.
RFC 7208 restricts SPF records to at most 10 DNS-querying mechanisms (include, a, mx, ptr, exists, redirect). If your record exceeds 10 lookups, receiving servers abort evaluation with a PermError.
Start at p=none to monitor with aggregate reports (rua) without affecting delivery, confirm your legitimate mail authenticates, then move to p=quarantine and finally p=reject for full protection. p=none alone provides reporting but no enforcement against spoofers.