SPF and DMARC records for 163.com
Live SPF and DMARC lookup for 163.com: the raw TXT records and the policy they enforce.
try:
- mail hosts
- 163mx02.mxmail.netease.com, 163mx01.mxmail.netease.com, 163mx03.mxmail.netease.com, 163mx00.mxmail.netease.com
- provider
- other
- spf record
- v=spf1 include:spf.mail.163.com -all
- dmarc policy
- none
- dmarc record
- v=DMARC1; p=none;
- disposable domain
- no
- free consumer provider
- yes
SPF for 163.com
163.com publishes an SPF record; it authorises 1 included sender list, and the record ends in -all (hard fail): mail from a server that is not listed should be rejected.
DMARC for 163.com
163.com has DMARC in monitoring mode (p=none). Receivers report what they see but deliver failing mail anyway, so the record protects nothing yet.
Why it matters
Receivers use SPF, DKIM, and DMARC together to decide whether a message really came from 163.com. A domain with a strict SPF record and an enforcing DMARC policy is hard to spoof and easier to deliver for; one without either is neither. Spaw reports has_spf and dmarc_policy on every lookup and adds a small risk weight when SPF is missing.
More checks for 163.com
checked 2026-09-03 · sources: live-dns 2026-09-03 · disposable-domains 2026-09-02 · free-provider-domains 2026-09-02 · mx-provider-patterns 2026-09-03
Need this at scale?
The Spaw API runs the same checks plus mailbox-level SMTP verification, batch and bulk endpoints, and list monitoring — 10 free lookups a month, no card required.