Jd.com

No. jd.com is not a disposable email provider. It is classified as Corporate Email operated by JD.com and addresses on jd.com are persistent rather than throwaway. Mail sent to a valid jd.com mailbox reaches a real recipient.

The fastest way to verify a jd.com email address is to use our free email checker. Enter any @jd.com mailbox at the top of this page and our system performs a real-time SMTP handshake against jd.com's mail servers, confirming whether the mailbox exists, is reachable, and is safe to send to. No email is ever delivered during the check.

Yes. Our real-time email verification API connects directly to jd.com's mail server, opens an SMTP session, and queries the mailbox using the RCPT TO command without ever transmitting an actual email. The server's response confirms whether the jd.com mailbox is valid, full, or non-existent. The recipient never receives anything and never sees the check.

jd.com currently publishes 2 mail exchange (MX) records. The primary MX is mx.jd.com, which is the first server contacted when other mail systems try to deliver email to a jd.com address. The full list with priorities and IP addresses is in the MX Records panel above. MX records tell sending servers where to route email for jd.com.

jd.com enforces all three email authentication standards: SPF, DKIM, and DMARC (policy: none). This is the gold-standard configuration. It means receivers can verify that mail claiming to come from @jd.com is genuine, and jd.com's DMARC policy of 'none' instructs receivers how to handle messages that fail those checks.

Bounces from jd.com usually fall into three buckets: the mailbox doesn't exist (5xx user unknown), the inbox is full, or your sending domain isn't authenticated to jd.com's satisfaction. The fastest fix is to run each address through a free email verifier before you send, and to make sure your own SPF, DKIM, and DMARC are configured correctly so jd.com's receivers trust you.

Our bulk email verifier accepts CSV or TXT uploads with thousands or millions of jd.com addresses (or any mix of domains). Every address goes through 30+ checks including SMTP existence, jd.com catch-all detection, role-account detection, and disposable-domain matching. Results typically come back within minutes and previously-failed addresses on your blacklist are reprocessed for free. For continuous high-volume needs, see our unlimited email verification API.

Yes, with normal hygiene. jd.com is a legitimate email service and signups from @jd.com behave like any other real user. Pipe each address through a real-time email verifier API at the moment of signup to catch typos and dead mailboxes, but there is no need to block jd.com by default.

Most jd.com mailboxes follow common patterns like first.last@jd.com, firstinitiallast@jd.com, or first@jd.com, but the actual local-part rules depend on JD.com. The only reliable way to confirm whether a specific @jd.com address exists is to run it through a free email verification tool. Guessing patterns will produce a high bounce rate and damage your sender reputation.

The 0-to-100 risk score for jd.com combines disposable-domain classification, mail-server reachability, MX record presence and depth, SPF / DKIM / DMARC enforcement, DMARC policy strength, SMTP banner response, and domain age. Lower scores mean safer to send to. Disposable domains are pinned at the high end of the scale. The jd.com score is recomputed on every audit so it always reflects the live state of the domain.