o2.pl is a free email provider

o2.pl is a consumer mailbox provider, so anyone can open an address there in a minute.

Free provider Spoofable

79 /100

Strong

Email authentication report card

What o2.pl publishes in DNS to stop other people sending mail in its name, read record by record.

2 pass 3 weak

Can mail be forged as this domain?

Yes, a forgery is delivered

DMARC is set to p=none, which only asks for reports, so a receiver that honours what this domain publishes is not told to reject a message with it in the From header, and delivers it.

  • Pass

    SPF -all

    The record ends in -all, so a receiver is told to treat mail from any host outside the list as a forgery.

  • Weak

    DMARC p=none

    A DMARC record is published, but p=none only asks for reports. Receivers are told to deliver failing mail anyway, so this stops no forgery.

    A checker that reports "DMARC found" here is telling you nothing useful.

  • Weak

    MTA-STS testing

    A policy is published in testing mode. Failures are reported but delivery still goes ahead over an unverified connection.

  • Weak

    DNSSEC Not signed

    The zone is not signed. A resolver has no cryptographic way to tell a real answer from a forged one.

  • Pass

    TLS-RPT Published

    Sending servers have an address to report failed TLS deliveries to.

Why it scores 79?

  1. Registered more than five years ago.
  2. Accepts mail through 1 MX host.
  3. SPF ends in -all, so mail from any other server is rejected.

What to publish to close the gaps

The records o2.pl is missing, in the order they are worth doing. Owner names are written out in full, so they work whether your DNS panel wants a full name or a relative one.

  1. Move DMARC off p=none

    Name_dmarc.o2.pl
    TypeTXT
    Valuev=DMARC1; p=quarantine; pct=100; rua=mailto:[email protected]

    p=none blocks nothing. Once your reports show every legitimate sender passing, raise the policy to quarantine and then to reject.

  2. Switch MTA-STS to enforce

    Valuemode: enforce

    Change mode in https://mta-sts.o2.pl/.well-known/mta-sts.txt and bump the id in the TXT record. Testing mode reports failures but still delivers.

  3. Sign the zone with DNSSEC

    Turn DNSSEC on with your DNS provider, then publish the DS record it hands you at your registrar. Every record above is only as trustworthy as the answer that carries it, and signing the zone is what makes the answers verifiable.

Questions about o2.pl

Every answer below is generated from the stored record for this domain.

Is o2.pl a disposable email domain?
No. o2.pl is a consumer mailbox provider, so addresses are permanent, but anyone can open one in a minute.
Is o2.pl spoofable?
Yes, a forgery is delivered. DMARC is set to p=none, which only asks for reports, so a receiver that honours what this domain publishes is not told to reject a message with it in the From header, and delivers it.
Does o2.pl publish SPF and DMARC?
o2.pl publishes an SPF record that ends in -all, the strict form. DMARC is published but set to p=none, which only asks for reports. It looks like protection and is not.
Who handles email for o2.pl?
We have not matched the mail hosts for o2.pl to a platform we track, so we do not name one. The hostnames themselves are available with an API key.
How old is the o2.pl domain?
The o2.pl domain was registered 26 years ago. The registrar of record is AZ.pl Sp. z o.o.
How do I block o2.pl on my signup form?
We do not classify o2.pl as disposable, so blocking it outright would turn away real people. If you want to act on it, decide on the signals listed above rather than the name.
Can I trust email from o2.pl?
o2.pl scores 79 out of 100, which is a strong band. The score is a summary of the classification, infrastructure, authentication, reputation and lifecycle signals we hold, not a judgment about any individual sender at that domain.

Last verified . We recheck every domain on a schedule, and this report changes only when its records or its verdict do.