Running diagnostic
Running your DNS diagnostic…
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 Oct 1, 2026 06:30 UTC · 7 checks · public report
Solid base — three policy steps remain.
sakthisaran.in publishes DMARC with p=none — spoofed mail is monitored but not blocked.
Your SPF setup is working, but it uses a softer “fail” mode, which means mail from servers not listed can still be treated as suspicious rather than fully rejected. This matters because it gives you some protection, but it is a little weaker than a stricter setting. The fix, if you want to harden it, is to switch to the stricter ending only after you’re sure every legitimate sender is already included.
v=spf1 include:zoho.in ~allEdit your SPF record at Cloudflare — step-by-step guide.
DMARC is set up, but it is only in monitoring mode, so it does not stop spoofed or fake emails from being delivered. This matters because attackers can still pretend to send mail from your domain, which can hurt trust and increase phishing risk. The fix is to change the DMARC policy from monitoring-only to a stricter enforcement mode so failing messages are rejected or quarantined.
One send: the full report — every finding and fix — lands in your inbox, with a free account waiting. Opening it signs you in and starts a 14-day Monitor trial. No card, and you can unsubscribe in one click.
Domain owner? Re-scan any time — or email hello@dnsdoctor.dev to have this page removed.
v=DMARC1; p=none; rua=mailto:936fbb8b701c4e3391b92022d40f1ec8@dmarc-reports.cloudflare.netEdit your DMARC record at Cloudflare — step-by-step guide.
DKIM helps prove that your emails really came from your domain and were not changed in transit. A 1024-bit DKIM key is considered weak, so it is easier to attack than a stronger key. The fix is to replace it with a new, stronger DKIM key and update the matching DNS entry for that selector.
Publish your DKIM record at Cloudflare — step-by-step guide.