singnet.com.sg email servers, SPF and DMARC

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

11 other domains we checked on the same day also route mail to hosts under atmailcloud.com, with different records from singnet.com.sg: aapt.net.au, adam.com.au, dodo.com.au, iinet.net.au, internode.on.net, iprimus.com.au, netspace.net.au, ozemail.com.au and 3 more.

The record on 5 November 2026 was v=spf1 include:_spf.singnet.com.sg ~all.

In plain terms, it delegates to _spf.singnet.com.sg. The top level uses 1 DNS-querying term; 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=none; sp=none; pct=100; adkim=r; aspf=r; rua=mailto:[email protected],mailto:[email protected];.

p=none only asks for reports; failing mail is delivered as normal.

Aggregate reports go to staff.singnet.com.sg and orchid.atmailcloud.com, so the domain's owner sees who sends mail as @singnet.com.sg.

Our checker treats @singnet.com.sg 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 mx-10.orchid.atmailcloud.com answers for @singnet.com.sg, 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.