surewest.net email servers, SPF and DMARC

surewest.net publishes 4 MX hosts; senders try the lowest priority number first (mx1c25.carrierzone.com, 10) and fall back to the others in order.

6 other domains we checked on the same day also route mail to hosts under carrierzone.com, with different records from surewest.net: alaska.net, consolidated.net, hargray.com, lumos.net, myfairpoint.net and ntelos.net.

The record on 5 November 2026 was v=spf1 mx a include:spf.mycci.net ~all.

In plain terms, it delegates to spf.mycci.net. The top level uses 3 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=quarantine; sp=none; rua=mailto:[email protected]; ruf=mailto:[email protected].

p=quarantine asks receivers to send failing mail to spam. Subdomains get sp=none.

Aggregate reports go to consolidated.net, so the domain's owner sees who sends mail as @surewest.net.

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

Our checker treats @surewest.net 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 mx1c25.carrierzone.com answers for @surewest.net, 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.