Email Authentication & Deliverability Tools

Mail that bounces or lands in spam usually comes down to a few DNS records and the reputation of the server that sent it. These tools read those records straight from DNS so you can check each piece of a domain's email setup.


Checking a domain's email setup, step by step

  1. Mail servers (MX). An MX Lookup shows where mail for the domain is delivered. If the MX records still point at a previous provider, incoming mail goes there.
  2. SPF. An SPF Lookup shows the v=spf1 TXT record that lists who may send mail for the domain. A domain must have exactly one SPF record, and evaluating it may take no more than 10 DNS lookups (include, a, mx, ptr, exists and redirect each count).
  3. DKIM. A DKIM Lookup fetches the public key at selector._domainkey.example.com. The selector is the s= value in the DKIM-Signature header of a message the domain sent. Need a key? Use the DKIM Generator, or the key your email provider gives you.
  4. DMARC. A DMARC Lookup shows the policy at _dmarc.example.com: what receivers should do with mail that fails (p=none, quarantine or reject) and where to send reports (rua=).
  5. Reverse DNS. The sending server's IP should have a PTR record, and that hostname should resolve back to the same IP. Check it with a Reverse DNS Lookup.
  6. Blocklists. An IP Blacklist Check shows whether the sending IP is listed on DNS blocklists such as Spamhaus ZEN or SpamCop.

SPF vs DKIM vs DMARC

SPFDKIMDMARC
Question it answersIs this server allowed to send for the domain?Was the message signed by the domain, and is it unchanged?What should receivers do when SPF and DKIM don't line up with the From address, and where should they report?
Where it is publishedTXT record on the domain, starting v=spf1TXT record at selector._domainkey.domainTXT record at _dmarc.domain, starting v=DMARC1
Domain it checksThe envelope sender (Return-Path)The d= domain in the DKIM-Signature headerThe visible From domain, which must match (align with) the SPF or DKIM domain
Common problemsTwo SPF records; more than 10 lookups; a sending service missing from the recordWrong selector; key not published or split incorrectly across stringsLeft at p=none indefinitely; no aligned SPF or DKIM, so legitimate mail fails

DMARC passes when either SPF or DKIM passes and uses a domain that aligns with the From address. Forwarded mail often breaks SPF, so a working DKIM signature is what keeps DMARC passing in practice.

Why this matters more than it used to

Since February 2024 Gmail and Yahoo require bulk senders (roughly 5,000 or more messages a day to their users) to publish SPF and DKIM, have a DMARC policy, and send from IPs with valid forward and reverse DNS. Smaller senders still need SPF or DKIM to avoid being filtered. If a domain sends any mail at all, every check above is worth running.