401202.xyz cannot receive email

401202.xyz cannot receive email at all.

No mail

20 /100

Poor

Email authentication report card

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

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

  • Pass

    DNSSEC Signed

    The zone is signed, so the MX, SPF and DMARC answers above cannot be quietly rewritten in transit.

  • Pass

    TLS-RPT Published

    Sending servers have an address to report failed TLS deliveries to.

Why it scores 20?

  1. This domain cannot receive email.

What to publish to close the gaps

The records 401202.xyz 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

    Name401202.xyz
    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.401202.xyz
    TypeTXT
    Valuev=STSv1; id=<a version string you bump on every change>

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

Questions about 401202.xyz

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

Is 401202.xyz a disposable email domain?
No. We classify 401202.xyz as no mail, not as a disposable mailbox service.
Is 401202.xyz 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 401202.xyz publish SPF and DMARC?
401202.xyz 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 401202.xyz?
We have not matched the mail hosts for 401202.xyz to a platform we track, so we do not name one. The hostnames themselves are available with an API key.
How old is the 401202.xyz domain?
The 401202.xyz domain was registered 1 year ago. The registrar of record is Cloudflare, Inc.
How do I block 401202.xyz on my signup form?
We do not classify 401202.xyz 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 401202.xyz?
401202.xyz 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.