emails.garden is a disposable email domain

emails.garden hands out throwaway mailboxes, so an address there identifies nobody.

Disposable Spoofable

0 /100

Poor

Email authentication report card

What emails.garden 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 0?

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

What to publish to close the gaps

The records emails.garden 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.emails.garden
    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.emails.garden
    TypeTXT
    Valuev=STSv1; id=<a version string you bump on every change>

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

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

Is emails.garden a disposable email domain?
Yes. emails.garden hands out throwaway mailboxes, so an address there tells you nothing about who is behind it.
Is emails.garden 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 emails.garden publish SPF and DMARC?
emails.garden 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 emails.garden?
We have not matched the mail hosts for emails.garden to a platform we track, so we do not name one. The hostnames themselves are available with an API key.
How old is the emails.garden domain?
The emails.garden domain was registered in the last year. The registrar of record is NameCheap, Inc.
How do I block emails.garden on my signup form?
Blocking the exact string emails.garden 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 emails.garden?
emails.garden 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.