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 6, 2026 02:30 UTC · 7 checks · public report
Solid base — two policy steps remain.
verso.fans publishes DMARC with p=none — spoofed mail is monitored but not blocked.
Your SPF check is using a soft-fail setting at the end, which means other servers are told to treat unexpected senders as suspicious but not always block them. This matters because it makes your domain a little easier to spoof, though it still works for DMARC. The fix, if you want to tighten security, is to switch to a hard-fail setting only after you’re sure every legitimate sender is included.
v=spf1 include:_spf.mx.cloudflare.net ~allEdit your SPF record at Cloudflare — step-by-step guide.
DMARC is set up, but it is only in monitoring mode, so it reports abuse without telling receiving mail servers to reject or quarantine fake messages. That means your domain can still be used in phishing or spoofing attempts, even though you may be getting reports about them. To fix it, change DMARC from monitoring-only to an enforcement mode so unauthenticated mail is handled more strictly.
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:4ad7f25306924a6295665dc51d78ac8a@dmarc-reports.cloudflare.netEdit your DMARC record at Cloudflare — step-by-step guide.
Publish your DKIM record at Cloudflare — step-by-step guide.