exetel.com.au email servers, SPF and DMARC

exetel.com.au publishes 2 MX hosts, all at priority 10, so senders spread mail across them.

1 other domain we checked on the same day also hand their mail to Proofpoint (security gateway) servers, with different records from exetel.com.au: turk.net.

The record on 5 November 2026 was v=spf1 include:spf.protection.outlook.com include:spfva.exetel.com.au include:amazonses.com include:spfvb.exetel.com.au include:spf-00aa7201.pphosted.com ~all.

In plain terms, it delegates to spf.protection.outlook.com, spfva.exetel.com.au, amazonses.com, spfvb.exetel.com.au and spf-00aa7201.pphosted.com. The top level uses 5 DNS-querying terms; SPF allows 10 in total including nested includes (RFC 7208 §4.6.4).

It ends in a soft fail (~all): mail from unlisted servers should be accepted but treated as suspicious.

The record is v=DMARC1; p=reject; rua=mailto:[email protected],mailto:[email protected];.

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

Aggregate reports go to exetel.com.au and reports.verifydmarc.com, so the domain's owner sees who sends mail as @exetel.com.au.

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

_mta-sts.exetel.com.au publishes v=STSv1; id=20260705001;, so exetel.com.au uses MTA-STS: sending servers that support it must deliver over verified TLS or not at all (RFC 8461).

It also asks for TLS reports with v=TLSRPTv1; rua=mailto:[email protected] (RFC 8460).

Our checker treats @exetel.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 published a test of how mxa-00aa7201.gslb.pphosted.com answers for @exetel.com.au, so we make no claim here about whether single mailboxes can be confirmed; 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.