westnet.com.au email servers, SPF and DMARC

westnet.com.au publishes 2 MX hosts; senders try the lowest priority number first (mx-10.au-east.atmailcloud.com, 10) and fall back to the others in order.

8 other domains we checked on the same day also route mail to hosts under atmailcloud.com, with different records from westnet.com.au: adam.com.au, dodo.com.au, iinet.net.au, internode.on.net, iprimus.com.au, singnet.com.sg, tpg.com.au and virgin.net.

The record on 5 November 2026 was v=spf1 redirect=spf.iinet.net.au.

In plain terms, it delegates to spf.iinet.net.au. The top level uses 1 DNS-querying term; SPF allows 10 in total including nested includes (RFC 7208 §4.6.4).

The record is v=DMARC1; p=reject; aspf=r; adkim=r; sp=reject;.

p=reject asks receivers to refuse mail that fails DMARC.

What that means for you: if a contact gives an @westnet.com.au address and you send to them, nothing changes. But never put an @westnet.com.au address in the From line of mail sent through your own tool or ESP. It can't pass DMARC for westnet.com.au, and this policy tells receivers to refuse it.

3 other domains published exactly the same MX hosts and SPF record as westnet.com.au on 5 November 2026: aapt.net.au, netspace.net.au and ozemail.com.au. Mail to any of them lands on the same servers.

westnet.com.au shares mx-10.au-east.atmailcloud.com and mx-20.au-east.atmailcloud.com with optusnet.com.au. When we tested those servers for optusnet.com.au on 13 October 2026, the result was: Verifiable. The server rejects unknown recipients during the SMTP conversation.

Our checker treats @westnet.com.au like any domain: syntax, MX, disposable and role checks first, then a made-up address to rule out a catch-all, then your address at RCPT TO, disconnecting without sending. We have not tested @westnet.com.au itself, but its mail goes to the same servers as optusnet.com.au, so expect @westnet.com.au results to follow the pattern described there. Each result carries its own reason.

DNS tells you where mail goes, not whether one person's mailbox still exists. For a list, run the whole file through a verifier before you send: invalid rows come out, risky rows (catch-all, unknown, refused) go in their own segment, and valid rows are safe to mail.