market-re.quest cannot receive email

market-re.quest cannot receive email at all.

No mail No authenticationSpoofable

20 /100

Poor

Email authentication report card

What market-re.quest publishes in DNS to stop other people sending mail in its name, read record by record.

1 pass 2 weak 2 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.

  • Fail

    SPF No record

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

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

What to publish to close the gaps

The records market-re.quest 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

    Namemarket-re.quest
    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 a DMARC record

    Name_dmarc.market-re.quest
    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.market-re.quest
    TypeTXT
    Valuev=STSv1; id=<a version string you bump on every change>

    Serve the policy body at https://mta-sts.market-re.quest/.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.market-re.quest
    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 market-re.quest

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

Is market-re.quest a disposable email domain?
No. We classify market-re.quest as no mail, not as a disposable mailbox service.
Is market-re.quest 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 market-re.quest publish SPF and DMARC?
market-re.quest publishes no SPF record, so no receiver is told which hosts may send in its name. No DMARC record is published, so a failing message is left to each receiver to judge.
Who handles email for market-re.quest?
We have not matched the mail hosts for market-re.quest to a platform we track, so we do not name one. The hostnames themselves are available with an API key.
How old is the market-re.quest domain?
The market-re.quest domain was registered 1 year ago. The registrar of record is Spaceship, Inc.
How do I block market-re.quest on my signup form?
We do not classify market-re.quest 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 market-re.quest?
market-re.quest 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.