burnermail.io is an email alias domain

burnermail.io issues forwarding aliases that hide a real mailbox, so the person is reachable but not identifiable.

Privacy relay

50 /100

Fair

Email authentication report card

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

1 pass 4 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.

  • Weak

    SPF ~all

    The record ends in ~all. Mail from a host outside the list is only marked, not rejected, so it usually still arrives.

  • Pass

    DMARC p=reject

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

  • Weak

    MTA-STS testing

    A policy is published in testing mode. Failures are reported but delivery still goes ahead over an unverified connection.

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

  1. Addresses here are forwarding aliases that hide the real mailbox, so one person can hold any number of identities on this domain.
  2. This domain hands out forwarding aliases that mask a real mailbox.

What to publish to close the gaps

The records burnermail.io 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. Tighten SPF to -all

    Nameburnermail.io
    TypeTXT
    Valuev=spf1 <your existing mechanisms> -all

    Keep the mechanisms you already have and change the final qualifier. Anything softer leaves the forgery path open.

  2. Switch MTA-STS to enforce

    Valuemode: enforce

    Change mode in https://mta-sts.burnermail.io/.well-known/mta-sts.txt and bump the id in the TXT record. Testing mode reports failures but still delivers.

  3. Publish a TLS reporting address

    Name_smtp._tls.burnermail.io
    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 burnermail.io

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

Is burnermail.io a disposable email domain?
No, but it is a privacy relay. burnermail.io mints forwarding aliases that hide a real mailbox, so the person is reachable while the identity stays masked.
Is burnermail.io 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 burnermail.io publish SPF and DMARC?
burnermail.io publishes an SPF record, though it does not end in -all, so hosts outside the list are not treated as forgeries. DMARC is published and enforced, so a failing message is rejected or quarantined.
Who handles email for burnermail.io?
We have not matched the mail hosts for burnermail.io to a platform we track, so we do not name one. The hostnames themselves are available with an API key.
How old is the burnermail.io domain?
The registry for .io does not publish a registration date we can read, so we do not state an age.
How do I block burnermail.io on my signup form?
We do not classify burnermail.io 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 burnermail.io?
burnermail.io scores 50 out of 100, which is a fair 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.