Email domain
139.com email servers, SPF and DMARC
Mail for @139.com goes to mx1.mail.139.com (MX priority 5) and 2 backup hosts, as DNS showed on 5 November 2026. The host sits under 139.com. The domain publishes an SPF record ending in ~all and no DMARC record, which decide whether mail claiming to be from @139.com 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.
139.com mail DNS on 5 November 2026
| Priority | MX host | Platform |
|---|---|---|
| 5 | mx1.mail.139.com | Not identified |
| 10 | mx2.mail.139.com | Not identified |
| 20 | mx3.mail.139.com | Not identified |
| SPF | v=spf1 include:spf.mail.10086.cn ~all |
|---|---|
| DMARC | None published |
| MTA-STS | None published |
| 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.
139.com MX records
139.com publishes 3 MX hosts; senders try the lowest priority number first (mx1.mail.139.com, 5) and fall back to the others in order.
139.com SPF record
The record on 5 November 2026 was v=spf1 include:spf.mail.10086.cn ~all.
In plain terms, it delegates to spf.mail.10086.cn. 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 soft fail (~all): mail from unlisted servers should be accepted but treated as suspicious.
139.com DMARC policy
_dmarc.139.com returned no DMARC record on 5 November 2026. Receivers therefore get no instruction about mail that fails SPF and DKIM, which makes @139.com easier to spoof (RFC 7489).
Can you verify @139.com addresses?
Our checker treats @139.com 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 mx1.mail.139.com answers for @139.com, 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 139.com?
- On 5 November 2026:
mx1.mail.139.com(priority 5),mx2.mail.139.com(priority 10),mx3.mail.139.com(priority 20). - Does 139.com have SPF and DMARC?
- On 5 November 2026
139.compublished an SPF record ending in~alland no DMARC record. - Is 139.com a disposable email domain?
- No.
139.comis not on the disposable domain list our checker uses, so @139.com addresses are checked like any other mailbox. See the disposable domain checker for the list.
Free checks for @139.com 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 @139.com 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.