inboxes.app cannot receive email

inboxes.app cannot receive email at all.

No mail Disposable

0 /100

Poor

Email authentication report card

What inboxes.app 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. The domain accepts no mail itself, but that never stopped anyone sending in its name.

  • 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. This domain cannot receive email.
  3. No SPF record, so anyone can send as this domain.

What to publish to close the gaps

The records inboxes.app 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

    Nameinboxes.app
    TypeTXT
    Valuev=spf1 -all

    This domain sends no mail, so the shortest correct record says exactly that: nothing is authorized.

  2. 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 inboxes.app

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

Is inboxes.app a disposable email domain?
No. Nothing accepts mail for inboxes.app at all, so it hands out no mailboxes of any kind.
Is inboxes.app 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. The domain accepts no mail itself, but that never stopped anyone sending in its name.
Does inboxes.app publish SPF and DMARC?
inboxes.app 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 inboxes.app?
Nothing handles mail for inboxes.app. Its DNS publishes no host that would accept a message for it.
How old is the inboxes.app domain?
The inboxes.app domain was registered 5 years ago. The registrar of record is Namecheap Inc.
How do I block inboxes.app on my signup form?
We do not classify inboxes.app 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 inboxes.app?
inboxes.app 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.