sunrise.ch email servers, SPF and DMARC

sunrise.ch publishes 2 MX hosts, all at priority 10, so senders spread mail across them.

2 other domains we checked on the same day also route mail to hosts under unified.services, with different records from sunrise.ch: hispeed.ch and swissonline.ch.

The record on 5 November 2026 was v=spf1 include:spf.sunrise.ch include:spf.sunrise.net include:spf-sunrise-ch.cname.unified.services -all.

In plain terms, it delegates to spf.sunrise.ch, spf.sunrise.net and spf-sunrise-ch.cname.unified.services. 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 hard fail (-all): receivers may reject mail from any server the record does not list.

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

p=quarantine asks receivers to send failing mail to spam.

Aggregate reports go to ag.eu.dmarcadvisor.com, so the domain's owner sees who sends mail as @sunrise.ch.

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

Our checker treats @sunrise.ch 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 mxin1-sunrise-ch.edge.unified.services answers for @sunrise.ch, 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.