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 Sep 18, 2026 00:07 UTC · 7 checks · public report
Solid base — two policy steps remain.
kombi.cl publishes DMARC with p=none — spoofed mail is monitored but not blocked.
Your SPF check is using a softer “maybe not allowed” setting for mail that isn’t listed, instead of a stricter “block it” setting. This matters because it can make spoofed or misconfigured emails a little less clearly rejected by other mail servers. The fix is to switch to the stricter setting only after you’re sure every legitimate sender is already included in your SPF setup.
v=spf1 include:_spf.google.com ~allEdit your SPF record at Cloudflare — step-by-step guide.
Your domain has DMARC set up, but it is only in monitoring mode, so it does not tell receiving mail servers to reject or quarantine fake messages. This matters because attackers can still more easily spoof your domain in phishing emails, which can hurt trust and deliverability. To fix it, change DMARC from monitoring-only to an enforcement mode after confirming your legitimate mail is passing authentication checks.
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.
v=DMARC1; p=none; sp=none; adkim=s; aspf=s; rua=mailto:[email protected]Edit your DMARC record at Cloudflare — step-by-step guide.