neko2.net is a disposable email domain

neko2.net hands out throwaway mailboxes, so an address there identifies nobody.

Disposable Spoofable

0 /100

Poor

Email authentication report card

What neko2.net 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?

No, a forgery is rejected

DMARC is set to p=reject and enforced on every message, so a receiver that honours it throws away any mail that fails alignment for this domain.

  • 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.

  • Pass

    DMARC p=reject

    Receivers are asked to reject any message that fails DMARC. This is the strongest published setting.

  • 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.

  • Weak

    DNSSEC Not signed

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

  • Weak

    TLS-RPT Not published

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

Why it scores 0?

  1. Mailboxes on this domain are throwaway, so no identity stands behind them.

What to publish to close the gaps

The records neko2.net 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. Publish an MTA-STS policy

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

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

  2. Publish a TLS reporting address

    Name_smtp._tls.neko2.net
    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.

  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 neko2.net

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

Is neko2.net a disposable email domain?
Yes. neko2.net hands out throwaway mailboxes, so an address there tells you nothing about who is behind it.
Is neko2.net spoofable?
No, a forgery is rejected. DMARC is set to p=reject and enforced on every message, so a receiver that honours it throws away any mail that fails alignment for this domain.
Does neko2.net publish SPF and DMARC?
neko2.net publishes an SPF record that ends in -all, the strict form. DMARC is published and enforced, so a failing message is rejected or quarantined.
Who handles email for neko2.net?
Mail for neko2.net is handled by kuku.lu, which carries 48 other domains we track.
How old is the neko2.net domain?
The neko2.net domain was registered 21 years ago. The registrar of record is Cloudflare, Inc.
How do I block neko2.net on my signup form?
Blocking the exact string neko2.net is not enough on its own: a disposable provider adds domains, and some hand out unlimited subdomains under one name. Match the mail platform behind the domain rather than the domain alone, which is what the lookup behind this page does.
Can I trust email from neko2.net?
neko2.net scores 0 out of 100, which is a poor 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.