mkomail.top is a disposable email domain

mkomail.top hands out throwaway mailboxes, so an address there identifies nobody.

Disposable

0 /100

Poor

Email authentication report card

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

3 pass 2 weak

Can mail be forged as this domain?

A forgery is sent to spam, not the inbox

DMARC is set to p=quarantine and enforced on every message, so a receiver that honours it does not reject a forgery outright but files it in spam rather than the inbox. Moving to p=reject would drop it entirely.

  • 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=quarantine

    Receivers are asked to send failing mail to spam rather than the inbox.

  • 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 0?

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

What to publish to close the gaps

The records mkomail.top 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. Raise DMARC to p=reject

    Name_dmarc.mkomail.top
    TypeTXT
    Valuev=DMARC1; p=reject; pct=100; rua=mailto:[email protected]

    Quarantine sends forgeries to spam, where people still find them. Reject stops delivery.

  2. Publish an MTA-STS policy

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

    Serve the policy body at https://mta-sts.mkomail.top/.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.mkomail.top
    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 mkomail.top

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

Is mkomail.top a disposable email domain?
Yes. mkomail.top hands out throwaway mailboxes, so an address there tells you nothing about who is behind it.
Is mkomail.top spoofable?
A forgery is sent to spam, not the inbox. DMARC is set to p=quarantine and enforced on every message, so a receiver that honours it does not reject a forgery outright but files it in spam rather than the inbox. Moving to p=reject would drop it entirely.
Does mkomail.top publish SPF and DMARC?
mkomail.top 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 mkomail.top?
Mail for mkomail.top is handled by Migadu, which carries 1 other domains we track.
How old is the mkomail.top domain?
The mkomail.top domain was registered 5 years ago. The registrar of record is Porkbun LLC.
How do I block mkomail.top on my signup form?
Blocking the exact string mkomail.top 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 mkomail.top?
mkomail.top 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.