aliceadsl.fr email servers, SPF and DMARC

aliceadsl.fr publishes 2 MX hosts; senders try the lowest priority number first (mx1.free.fr, 10) and fall back to the others in order.

1 other domain we checked on the same day also route mail to hosts under free.fr, with different records from aliceadsl.fr: alicepro.fr.

The record on 5 November 2026 was v=spf1 include:_spf.free.fr ?all.

In plain terms, it delegates to _spf.free.fr. 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 neutral ending (?all): the record makes no claim about unlisted servers.

_dmarc.aliceadsl.fr returned no DMARC record on 5 November 2026. Receivers therefore get no instruction about mail that fails SPF and DKIM, which makes @aliceadsl.fr easier to spoof (RFC 7489).

2 other domains published exactly the same MX hosts and SPF record as aliceadsl.fr on 5 November 2026: libertysurf.fr and online.fr. Mail to any of them lands on the same servers.

aliceadsl.fr shares mx1.free.fr and mx2.free.fr with free.fr. When we tested those servers for free.fr on 12 October 2026, the result was: Verifiable. The server rejects unknown recipients during the SMTP conversation.

Our checker treats @aliceadsl.fr 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 tested @aliceadsl.fr itself, but its mail goes to the same servers as free.fr, so expect @aliceadsl.fr results to follow the pattern described there. 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.