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 Oct 19, 2026 13:25 UTC · 7 checks · public report
Solid base — two policy steps remain.
computer.srl publishes DMARC with p=none — spoofed mail is monitored but not blocked.
Your SPF record currently uses a soft-fail at the end, which means mail from servers not on the approved list is treated as suspicious rather than strictly rejected. This still works for DMARC, but it is a weaker setting. If you want to harden it, the change is to switch to a strict reject at the end, but only after you are sure every legitimate email sender is already included.
v=spf1 include:spf.sendinblue.com mx ~allDMARC is set up, but it is only in monitoring mode, so it does not tell receiving mail servers to block or quarantine fake messages using your domain. This matters because scammers can still spoof your email address more easily, which can hurt trust and deliverability. The fix is to change the DMARC policy from monitoring only to a stricter enforcement mode, after you confirm your legitimate mail is passing SPF and DKIM.
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; sp=none; rua=mailto:dmarc@mailinblue.com!10m; ruf=mailto:dmarc@mailinblue.com!10m; rf=afrf; pct=100; ri=86400