Updated · Volt Ghost team
One host family per NetEase brand
Each row is what Cloudflare's DNS-over-HTTPS resolver returned on 14 November 2026.
| Address domain | Priority 10 | Priority 50 (backup) |
|---|---|---|
163.com | 163mx01, 163mx02, 163mx03 | 163mx00 |
126.com | 126mx01, 126mx02, 126mx03 | 126mx00 |
yeah.net | yeahmx01 | yeahmx00 |
vip.163.com | vip163mx01 | vip163mx00 |
188.com | 188mx01 | 188mx00 |
All host names end in .mxmail.netease.com. Number 00 is always the backup at priority 50, the reverse of how QQ Mail numbers its hosts. Seen from Cloudflare's resolver, every 163 and 126 host returned two to four IPv4 addresses and no IPv6. Seven of the eight sat in Alibaba Cloud ranges registered in the US (AS45102); the eighth, 126mx03, returned two addresses on NetEase Hong Kong's own network (AS137263), the same ranges listed in NetEase's SPF. That mix suggests region-aware DNS, so a resolver inside China may get different addresses. Do not hard-code the IPs; resolve the names.
SPF, DMARC and the DNS behind it
| Record | Where | Value on 14 November |
|---|---|---|
| SPF | apex TXT of all five domains | v=spf1 include:spf.mail.163.com -all |
| SPF list | spf.mail.163.com | five includes (spf-a to spf-e.mail.163.com), -all |
| DMARC | _dmarc.163.com, 126.com, yeah.net, vip.163.com | v=DMARC1; p=none; with no report address |
| DMARC | _dmarc.188.com | none published |
| MTA-STS / TLS-RPT | _mta-sts.163.com, _smtp._tls.163.com | not published |
| Name servers | 163.com | five nease.net and two 166.com hosts, all NetEase's own |
The SPF side is strict: a hard -all at both levels, so a receiver that checks SPF has a clear answer. The DMARC side is the opposite. p=none without a rua tag means NetEase neither asks receivers to act on spoofed 163.com mail nor collects aggregate reports about it. Spoofed mail is therefore judged on SPF and the receiver's own rules. Compare Mail.ru, which publishes p=reject.
Practical notes for senders and forms
If your messages to @163.com or @126.com bounce, the bounce text names the host that refused them, which tells you which brand's pool you hit. Sign-up codes that never arrive are a common complaint with large free providers; verification code not received walks through the checks in order. A business domain hosted on NetEase's enterprise mail also points at mxmail.netease.com, and our email host lookup labels it NetEase Mail.
Not a throwaway provider
NetEase mailboxes are meant to last, and their MX hosts are NetEase's own, so MX-based screening treats them as ordinary mail. The domains that do get flagged usually share a handful of servers; the 2026 disposable email domains report counts how concentrated they are. How sites detect disposable email lists the other checks, and the disposable email checker answers for one address at a time.
Questions
What is the MX record for 163.com?
163.com lists four hosts: 163mx01, 163mx02 and 163mx03.mxmail.netease.com at priority 10, which share the load, and 163mx00.mxmail.netease.com at priority 50 as the backup.
Do 163.com and 126.com share mail servers?
They share the mxmail.netease.com zone and the same SPF include, but each brand has its own host names: 126.com uses 126mx00 to 126mx03, yeah.net uses yeahmx00 and yeahmx01.
Does NetEase enforce DMARC?
Not on 14 November 2026. 163.com, 126.com, yeah.net and vip.163.com published p=none, which asks for no action on failing mail, and 188.com published no DMARC record at all.
Is 163.com a temporary email service?
No. 163.com and 126.com are long-standing free mailboxes. None of the five NetEase domains on this page is on the public disposable-domain list our checker uses.
