emailboxer.one cannot receive email

emailboxer.one cannot receive email at all.

No mail Spoofable

20 /100

Poor

Email authentication report card

What emailboxer.one 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?

Yes, a forgery is delivered

no DMARC record is published, 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.

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

  • Fail

    DMARC No record

    No DMARC record is published, so receivers get no instruction and judge a forged message on SPF and DKIM alone.

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

  1. This domain cannot receive email.
  2. No DMARC record, so receiving servers have no policy to apply to forged mail.

What to publish to close the gaps

The records emailboxer.one 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

    Nameemailboxer.one
    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. Publish a DMARC record

    Name_dmarc.emailboxer.one
    TypeTXT
    Valuev=DMARC1; p=none; rua=mailto:[email protected]; fo=1

    Start at p=none with a reporting address, read the reports for a few weeks to find the senders you forgot, then move the policy up.

  3. Publish an MTA-STS policy

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

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

  4. Publish a TLS reporting address

    Name_smtp._tls.emailboxer.one
    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 emailboxer.one

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

Is emailboxer.one a disposable email domain?
No. We classify emailboxer.one as no mail, not as a disposable mailbox service.
Is emailboxer.one spoofable?
Yes, a forgery is delivered. no DMARC record is published, 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 emailboxer.one publish SPF and DMARC?
emailboxer.one publishes an SPF record, though it does not end in -all, so hosts outside the list are not treated as forgeries. No DMARC record is published, so a failing message is left to each receiver to judge.
Who handles email for emailboxer.one?
We have not matched the mail hosts for emailboxer.one to a platform we track, so we do not name one. The hostnames themselves are available with an API key.
How old is the emailboxer.one domain?
The emailboxer.one domain was registered in the last year. The registrar of record is NameSilo, LLC.
How do I block emailboxer.one on my signup form?
We do not classify emailboxer.one 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 emailboxer.one?
emailboxer.one scores 20 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.