Email domain
yeah.net email servers, SPF and DMARC
Mail for @yeah.net goes to yeahmx01.mxmail.netease.com (MX priority 10) and 1 backup host, as DNS showed on 5 November 2026. The host sits under netease.com. The domain publishes an SPF record ending in -all and a DMARC policy of p=none, which decide whether mail claiming to be from @yeah.net is trusted.
Check one address
Five checks a minute, no account needed. Nothing is sent to the address — we ask its mail server whether the mailbox exists, then disconnect.
Checking a whole list? The first 100 addresses are free, with results to download. No card.
By continuing you agree to our Terms and Privacy Policy.
yeah.net mail DNS on 5 November 2026
| Priority | MX host | Platform |
|---|---|---|
| 10 | yeahmx01.mxmail.netease.com | Not identified |
| 50 | yeahmx00.mxmail.netease.com | Not identified |
| SPF | v=spf1 include:spf.mail.163.com -all |
|---|---|
| DMARC | v=DMARC1; p=none; |
| MTA-STS | v=STSv1; id=20250429T010101; |
| TLS reporting | None published |
Read on 5 November 2026 with dig against 1.1.1.1 (8.8.8.8 as fallback); nothing sent to the mail servers. Check the records today with the email provider lookup.
yeah.net MX records
yeah.net publishes 2 MX hosts; senders try the lowest priority number first (yeahmx01.mxmail.netease.com, 10) and fall back to the others in order.
2 other domains we checked on the same day also route mail to hosts under netease.com, with different records from yeah.net: 188.com and vip.163.com.
yeah.net SPF record
The record on 5 November 2026 was v=spf1 include:spf.mail.163.com -all.
In plain terms, it delegates to spf.mail.163.com. The top level uses 1 DNS-querying term; SPF allows 10 in total including nested includes (RFC 7208 §4.6.4).
It ends in a hard fail (-all): receivers may reject mail from any server the record does not list.
yeah.net DMARC policy
The record is v=DMARC1; p=none;.
p=none only asks for reports; failing mail is delivered as normal.
yeah.net TLS policy
_mta-sts.yeah.net publishes v=STSv1; id=20250429T010101;, so yeah.net uses MTA-STS: sending servers that support it must deliver over verified TLS or not at all (RFC 8461).
Can you verify @yeah.net addresses?
Our checker treats @yeah.net like any domain: syntax, MX, disposable and role checks first, then a made-up address to rule out a catch-all, then your address at RCPT TO, disconnecting without sending. We have not published a test of how yeahmx01.mxmail.netease.com answers for @yeah.net, so we make no claim here about whether single mailboxes can be confirmed; each result carries its own reason.
Cleaning a list with these addresses
DNS tells you where mail goes, not whether one person's mailbox still exists. For a list, run the whole file through a verifier before you send: invalid rows come out, risky rows (catch-all, unknown, refused) go in their own segment, and valid rows are safe to mail.
Common questions
- What are the MX records for yeah.net?
- On 5 November 2026:
yeahmx01.mxmail.netease.com(priority 10),yeahmx00.mxmail.netease.com(priority 50). - Does yeah.net have SPF and DMARC?
- On 5 November 2026
yeah.netpublished an SPF record ending in-alland a DMARC policy ofp=none. - Is yeah.net a disposable email domain?
- No.
yeah.netis not on the disposable domain list our checker uses, so @yeah.net addresses are checked like any other mailbox. See the disposable domain checker for the list.
Free checks for @yeah.net lists
- Bulk email checker for a pasted list or CSV
- Verify a whole file with a reason for every row
- SPF lookup counter
- MTA-STS checker
- Disposable email checker
Another domain? See every email domain we have mapped and what our checker does at each mailbox provider.
Got a list with @yeah.net addresses?
Sign in with Google and the first 100 addresses are checked free: valid, risky and invalid, with the reason for each row and a file to download. No card. After that, plans start at $9/mo for 2,500 emails a month.
By continuing you agree to our Terms and Privacy Policy.