aufu.de is a disposable email domain

aufu.de hands out throwaway mailboxes, so an address there identifies nobody.

Disposable

0 /100

Poor

Email authentication report card

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

1 pass 3 weak 1 fail

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.

  • Fail

    SPF No record

    No SPF record is published, so receivers have no list of hosts allowed to send as this domain.

  • 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.
  2. No SPF record, so anyone can send as this domain.

What to publish to close the gaps

The records aufu.de 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 SPF record

    Nameaufu.de
    TypeTXT
    Valuev=spf1 include:<your mail platform> -all

    List every platform that sends on your behalf, then end the record in -all so everything else fails.

  2. Publish an MTA-STS policy

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

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

  4. 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 aufu.de

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

Is aufu.de a disposable email domain?
Yes. aufu.de hands out throwaway mailboxes, so an address there tells you nothing about who is behind it.
Is aufu.de 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 aufu.de publish SPF and DMARC?
aufu.de publishes no SPF record, so no receiver is told which hosts may send in its name. DMARC is published and enforced, so a failing message is rejected or quarantined.
Who handles email for aufu.de?
Mail for aufu.de is handled by emailfake.com, which carries 14 other domains we track.
How old is the aufu.de domain?
The registry for .de does not publish a registration date we can read, so we do not state an age.
How do I block aufu.de on my signup form?
Blocking the exact string aufu.de 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 aufu.de?
aufu.de 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.