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 28, 2026 09:44 UTC · 7 checks · public report
Solid base — two policy steps remain.
kazanc360.com publishes DMARC with p=none — spoofed mail is monitored but not blocked.
Your SPF setting is currently in “soft fail” mode, which means other mail servers are only being asked to treat unauthorized mail as suspicious rather than clearly rejecting it. That can make it easier for attackers to send mail that looks like it came from your domain. The fix is to change the SPF ending to a strict reject policy, but only after you’ve confirmed every legitimate sender is included.
v=spf1 ip4:159.253.43.74 +a +mx ~allYour domain has a DMARC setting, but it is only in monitoring mode, so it is not actually blocking fake or forged emails. This matters because attackers can still send messages that look like they came from your domain, which can hurt trust and increase phishing risk. To fix it, change the DMARC policy from monitoring only to an enforcing mode so email receivers are told to reject or quarantine suspicious mail.
v=DMARC1; p=none;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.
_dmarc · Record type: TXT · TTL: 3600v=DMARC1; p=quarantine;