onionmail.com is a free email provider

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

Free provider Spoofable

93 /100

Strong

Email authentication report card

What onionmail.com 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 Not published

    No MTA-STS policy, so a sending server has nothing that tells it to insist on verified TLS for this domain.

  • Pass

    DNSSEC Signed

    The zone is signed, so the MX, SPF and DMARC answers above cannot be quietly rewritten in transit.

  • Weak

    TLS-RPT Not published

    No reporting address, so failed TLS deliveries to this domain go unnoticed by its owner.

Why it scores 93?

  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 onionmail.com 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.onionmail.com
    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. Publish an MTA-STS policy

    Name_mta-sts.onionmail.com
    TypeTXT
    Valuev=STSv1; id=<a version string you bump on every change>

    Serve the policy body at https://mta-sts.onionmail.com/.well-known/mta-sts.txt, start it in testing mode, then switch it to enforce so senders refuse to deliver over an unverified connection.

  3. Publish a TLS reporting address

    Name_smtp._tls.onionmail.com
    TypeTXT
    Valuev=TLSRPTv1; rua=mailto:[email protected]

    Without it, a sending server that could not negotiate TLS with your mail hosts has nowhere to tell you.

Questions about onionmail.com

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

Is onionmail.com a disposable email domain?
No. onionmail.com is a consumer mailbox provider, so addresses are permanent, but anyone can open one in a minute.
Is onionmail.com 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 onionmail.com publish SPF and DMARC?
onionmail.com 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 onionmail.com?
We have not matched the mail hosts for onionmail.com to a platform we track, so we do not name one. The hostnames themselves are available with an API key.
How old is the onionmail.com domain?
The onionmail.com domain was registered 13 years ago. The registrar of record is GoDaddy.com, LLC.
How do I block onionmail.com on my signup form?
We do not classify onionmail.com 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 onionmail.com?
onionmail.com scores 93 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.