Scanning
Scanning your domain…
Checking SPF, DMARC, DKIM, MX, DNS, blacklists and domain & SSL expiry. A domain we haven't scanned before takes a few seconds — hang tight.
Checking SPF, DMARC, DKIM, MX, DNS, blacklists and domain & SSL expiry. A domain we haven't scanned before takes a few seconds — hang tight.
Scanned Nov 3, 2026 14:42 UTC · 7 checks · public report
One finding blocks deliverability.
trustkill.com publishes DMARC with p=none — spoofed mail is monitored but not blocked.
Your SPF check is failing because the mail-sending rules for your domain require too many DNS lookups, which can cause email checks to break. This matters because some receiving servers may treat your messages as suspicious or reject them, hurting deliverability. The fix is to simplify the SPF setup by reducing nested includes and other lookup-heavy mechanisms so it stays within the allowed limit.
v=spf1 include:mailgun.org a DMARC is set up, but it is only monitoring messages and not blocking anything. That means spoofed or fake emails using your domain can still get through more easily. To fix it, change DMARC from monitoring-only to an enforcement mode so mail that fails checks is rejected or sent to spam.
What DNS shows against each provider's published rules. Not a compliance verdict.
3 of 4 met
We email you a link to the full report, with every finding and fix. Opening it signs you in to a free account and starts a 14‑day Monitor trial. No card, and you can unsubscribe in one click.
Check SPF, DMARC, DKIM, MX, DNS health, blacklists and domain & SSL expiry in one free scan, with the exact record to paste for each problem it finds.
Domain owner? Re-scan any time, or email hello@dnsdoctor.dev to have this page removed.
Edit your SPF record at Cloudflare — step-by-step guide.
v=DMARC1; p=none;Edit your DMARC record at Cloudflare — step-by-step guide.
Your email signing key for the DKIM selector named **smtp** is too small, so it is weaker than recommended. This matters because weaker keys are easier to attack, which can hurt email trust and deliverability. The fix is to replace it with a **stronger DKIM key**, usually by generating a new selector/key pair and updating the DNS record and mail server to use it.
Publish your DKIM record at Cloudflare — step-by-step guide.
3 of 4 met
2 of 3 met
2 of 3 met
Send one real email and see how Gmail, Yahoo, Outlook and Apple are likely to treat it.DNS can't show these 4. One real message can.
Send a test emailSpam complaint rate stays under 0.3%Only each provider's own sender tools show this. All senders at Gmail, Yahoo.
How we read these: sender rules in our methodology. Each provider's rules: Gmail · Yahoo · Outlook · Apple