belgacom.net email servers, SPF and DMARC

belgacom.net publishes a single MX host, mx.glb.proximus.be. With no backup host, a sender that can't reach it queues the message and retries until the server answers or the queue gives up.

3 other domains we checked on the same day also route mail to hosts under proximus.be, with different records from belgacom.net: proximus.be, scarlet.be and skynet.be.

The record on 5 November 2026 was v=spf1 include:ispmail.spf.secure-mail.be -all.

In plain terms, it delegates to ispmail.spf.secure-mail.be. 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 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].

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

Aggregate reports go to proximus.com, so the domain's owner sees who sends mail as @belgacom.net.

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

Our checker treats @belgacom.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 mx.glb.proximus.be answers for @belgacom.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.