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 Jul 21, 2026 15:13 UTC · 7 checks · public report
One finding blocks deliverability.
slop.watch has no enforceable DMARC policy, so mail that forges its domain is not blocked at the recipient.
Your domain does not have a DMARC policy set up, which means receiving mail servers have no clear instructions for what to do with messages that claim to come from your domain. This matters because it makes your domain easier to impersonate in phishing and spoofing attacks, and it also reduces your control and visibility over email delivery. The fix is to publish a DMARC record in your DNS for the domain.
_dmarc · Record type: TXT · TTL: 3600v=DMARC1; p=quarantineApply this at Cloudflare — step-by-step guide.
Your SPF check is using a soft fail setting at the end, which tells receiving mail servers to treat unauthorized messages more gently instead of rejecting them outright. This matters because it can make it easier for spoofed email to get through, or at least look less suspicious. The fix is to change the SPF policy to a hard fail end state once you’ve confirmed every legitimate sender is included.
v=spf1 include:_spf.mx.cloudflare.net ~allEdit your SPF record at Cloudflare — step-by-step guide.
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 [email protected] to have this page removed.