163.com is a free email provider

163.com is a major consumer mailbox provider. Anyone can open an address, and at this scale a forged message is usually caught by the provider even where the domain's own records would let it through.

Major provider Spoofable

93 /100

Strong

Email authentication report card

What 163.com 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?

Yes on paper, but unlikely to land

DMARC is set to p=none, which only asks for reports, so nothing this domain publishes tells a receiver to reject a forged message. In practice a forgery will still be caught: a provider this size runs its own reputation and content filtering on top of what the domain publishes. That safety net is the provider's, not the domain's.

  • Pass

    SPF -all

    The record ends in -all, so a receiver is told to treat mail from any host outside the list as a forgery.

  • Weak

    DMARC p=none

    A DMARC record is published, but p=none only asks for reports. Receivers are told to deliver failing mail anyway, so this stops no forgery.

    A checker that reports "DMARC found" here is telling you nothing useful.

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

  1. Registered more than five years ago.
  2. Accepts mail through 4 MX hosts.
  3. SPF ends in -all, so mail from any other server is rejected.

What to publish to close the gaps

The records 163.com 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. Move DMARC off p=none

    Name_dmarc.163.com
    TypeTXT
    Valuev=DMARC1; p=quarantine; pct=100; rua=mailto:[email protected]

    p=none blocks nothing. Once your reports show every legitimate sender passing, raise the policy to quarantine and then to reject.

  2. Publish an MTA-STS policy

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

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

  3. Publish a TLS reporting address

    Name_smtp._tls.163.com
    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 163.com

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

Is 163.com a disposable email domain?
No. 163.com is a consumer mailbox provider, so addresses are permanent, but anyone can open one in a minute.
Is 163.com spoofable?
Yes on paper, but unlikely to land. DMARC is set to p=none, which only asks for reports, so nothing this domain publishes tells a receiver to reject a forged message. In practice a forgery will still be caught: a provider this size runs its own reputation and content filtering on top of what the domain publishes. That safety net is the provider's, not the domain's.
Does 163.com publish SPF and DMARC?
163.com publishes an SPF record that ends in -all, the strict form. DMARC is published but set to p=none, which only asks for reports. It looks like protection and is not.
Who handles email for 163.com?
Mail for 163.com is handled by NetEase Mail, which carries 2 other domains we track.
How old is the 163.com domain?
The 163.com domain was registered 28 years ago. The registrar of record is MarkMonitor Information Technology (Shanghai) Co., Ltd.
How do I block 163.com on my signup form?
We do not classify 163.com 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 163.com?
163.com scores 93 out of 100, which is a strong 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.