🎉 Black Friday Offer: 50% OFF on all Monthly Plans for 6 months. New Customers Only.
Check SPF, DKIM, DMARC, MX and blacklists in seconds, and get step-by-step fixes for anything that will send your cold email to spam.
The records Gmail, Outlook and Yahoo look at before deciding whether your email reaches the inbox.
SPF
One record, ≤10 lookups
Lists who can send for your domain. We check there's exactly one record, it ends in ~all or -all, and it stays under the 10 DNS lookup limit.
DKIM
1024-bit key or stronger
Proves your emails weren't altered. We scan 30+ common selectors (or the one you enter) and check the key isn't revoked or weak.
DMARC
p=quarantine with reports
Tells inbox providers what to do with spoofed email. We check the policy, the report address and whether a subdomain inherits it.
MX records
At least one
Where replies land. A domain that can't receive email bounces every reply and looks suspicious to spam filters.
Blacklists
Not listed
We check your website and mail server IPs against SpamCop, Barracuda, PSBL, Mailspike, UCEPROTECT and 0spam.
Health score
90+ is healthy
SPF, DKIM and DMARC carry the most weight, as they're what Gmail and Yahoo require from bulk senders since 2024.
Deliveryman sets up SPF, DKIM, DMARC and warmup on every domain automatically, and monitors blacklists daily.
It checks the DNS records inbox providers use to decide whether to trust your email: SPF, DKIM, DMARC and MX, plus whether your mail server IPs are on spam blocklists. Problems in any of these send email to spam or get it rejected.
DKIM records live under a selector name (like google._domainkey.yourdomain.com), and there's no way to list every selector. We check 30+ common ones. If your provider uses a custom selector, click “Add DKIM selector” and enter it. You'll find it as s= in the DKIM-Signature header of an email you sent.
Start with p=none and a report address to monitor, then move to p=quarantine once SPF and DKIM pass consistently. p=none meets Gmail and Yahoo's minimum requirement but doesn't protect your domain from spoofing.
SPF allows at most 10 DNS lookups (include, a, mx, redirect and similar) when checking a record, including nested includes. Go over and SPF fails for every email. It's easy to hit by adding several tools that each need an include.
SpamCop, Barracuda, PSBL, Mailspike, UCEPROTECT Level 1 and 0spam. Spamhaus isn't included because it doesn't answer lookups made through public DNS services, which this tool uses to run in your browser.
Less for IPs: Google and Microsoft manage their shared sending IPs. Your domain's reputation matters far more, and that's driven by SPF, DKIM, DMARC, sending volume and how recipients engage with your email.
No. Every lookup runs in your browser against public DNS (Cloudflare, with Google as a fallback). We don't log the domains you check.