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 05:47 UTC · 7 checks · public report
One finding blocks deliverability.
cnzone.net publishes DMARC with p=none — spoofed mail is monitored but not blocked.
Your SPF setting is too permissive because it effectively says any server can send mail for your domain. That makes it easier for attackers to spoof your address and can hurt email delivery and trust. The fix is to tighten the SPF rule so it only allows your real mail server(s) and does not include a catch-all permission.
v=spf1 ip4:58.242.244.250 Your domain has DMARC set up, but it is only in monitoring mode, so it does not stop fake or spoofed emails from being accepted. This matters because attackers can more easily send messages that look like they came from your domain, which can hurt trust and increase phishing risk. The fix is to change DMARC from monitoring-only to an enforcement setting so unauthenticated mail is rejected or quarantined.
What DNS shows against each provider's published rules. Not a compliance verdict.
3 met · 1 not checked
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; rua=mailto:cf6e97f9c65d402387cc5ff0aa5b5818@dmarc-reports.cloudflare.net,mailto:postmaster@cnzone.netEdit your DMARC record at Cloudflare — step-by-step guide.
Your domain has a mail server listed in DNS, which tells other mail systems where to send email for your domain. This matters because if that server is wrong, offline, or not meant for your domain, you can miss incoming email or have delivery problems. The fix is to confirm the mail server name is correct for your email provider and update the MX setting if your mail is handled somewhere else.
mail.cnzone.netPublish your DKIM record at Cloudflare — step-by-step guide.
3 met · 1 not checked
2 met · 1 not checked
2 met · 1 not checked
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