tlen.pl email servers, SPF and DMARC

tlen.pl publishes a single MX host, mx.tlen.pl. 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.

The record on 5 November 2026 was v=spf1 include:wp.pl include:_spf.grupawp.pl mx -all.

In plain terms, it delegates to wp.pl and _spf.grupawp.pl. 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=none; rua=mailto:[email protected].

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

Aggregate reports go to o2.pl, so the domain's owner sees who sends mail as @tlen.pl.

1 other domain published exactly the same MX hosts and SPF record as tlen.pl on 5 November 2026: go2.pl. Mail to any of them lands on the same servers.

tlen.pl shares mx.tlen.pl with o2.pl. When we tested those servers for o2.pl on 13 October 2026, the result was: Verifiable. The server rejects unknown recipients during the SMTP conversation.

Our checker treats @tlen.pl 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 @tlen.pl itself, but its mail goes to the same servers as o2.pl, so expect @tlen.pl 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.