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 12, 2026 00:08 UTC · 7 checks · public report
Solid base — three policy steps remain.
middys.com.au publishes DMARC with p=none — spoofed mail is monitored but not blocked.
Your SPF setup is mostly working, but it ends with a soft warning instead of a strict reject for mail that doesn’t match your approved senders. This matters because it gives spoofed email a little more leeway, although it is still acceptable for DMARC. The fix, if you want tighter protection, is to switch to a stricter ending only after you’ve confirmed every legitimate mail source is included.
v=spf1 mx a:middys.com.au ip4:110.145.227.138/32 ip4:151.158.163.0/24 ip4:60.242.35.232/29 ip4:223.27.16.112/32 ip4:203.89.204.188/32 include:spf.protection.outlook.com include:servers.mcsv.net include:au._netblocks.mimecast.com ~allDMARC is set up, but it is only in monitoring mode, so it does not block fake emails that use your domain. This matters because scammers can more easily spoof your address, which can hurt trust and deliverability. To fix it, change DMARC from monitoring-only to an enforcement mode so mail that fails authentication is rejected or sent to spam.
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:dmarc.reports@middys.com.au;This means your email signing key is too small, which makes it easier for attackers to break the protection that helps prove your messages are really from you. If it stays weak, email can be more vulnerable to spoofing or tampering. The fix is to replace the current DKIM key with a stronger one, usually by creating a new DKIM key pair with a larger key size and updating the signing setup to use it.