Identity
22
F
jd.com
Posture Score: 21/100
Scanned May 27, 2026 at 12:44 PM UTC
Score History
Attack Surface
0
Reputation
41
Identity Findings
Weak DKIM RSA key (~1296 bits) for selector 'mail'
RSA keys shorter than 2048 bits are considered weak. Current key is approximately 1296 bits.
💡 Generate a new 2048-bit (or larger) RSA key pair and update the DKIM record.
Weak DKIM RSA key (~1296 bits) for selector 'k1'
RSA keys shorter than 2048 bits are considered weak. Current key is approximately 1296 bits.
💡 Generate a new 2048-bit (or larger) RSA key pair and update the DKIM record.
Subdomains have no DMARC enforcement
No sp= tag set and p=none. Subdomains inherit the monitoring-only policy, leaving them open to spoofing.
💡 Add sp=reject (or sp=quarantine) to your DMARC record to protect subdomains.
MX hostname resolves via CNAME: mx.jd.com
MX records should not point to a CNAME (RFC 2181). This can cause delivery failures.
💡 Point the MX record directly to an A/AAAA record, not a CNAME.
FCrDNS failure: no PTR for 103.107.89.10 (mx1.jd.com)
The IP 103.107.89.10 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.
💡 Configure a PTR record for the IP that matches the mail server hostname.
FCrDNS failure: no PTR for 116.198.6.213 (mx.jd.com)
The IP 116.198.6.213 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.
💡 Configure a PTR record for the IP that matches the mail server hostname.
DMARC policy is monitoring-only (p=none)
The p=none policy only monitors; it does not instruct receivers to quarantine or reject unauthenticated mail.
💡 Upgrade to p=quarantine or p=reject after reviewing aggregate reports.
No PTR record for MX IP: 103.107.89.10
The IP 103.107.89.10 (for mx1.jd.com) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 116.198.6.213
The IP 116.198.6.213 (for mx.jd.com) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No MTA-STS record found
Without MTA-STS, mail transport encryption cannot be enforced and is vulnerable to downgrade attacks.
💡 Publish a _mta-sts TXT record and host a policy file at https://mta-sts.jd.com/.well-known/mta-sts.txt
STARTTLS without MTA-STS or DANE protection
STARTTLS alone is vulnerable to downgrade attacks. Neither MTA-STS nor DANE is configured to enforce encryption.
💡 Deploy MTA-STS and/or DANE to protect against STARTTLS stripping attacks.
No CAA records found
No CAA records are configured. Any certificate authority can issue certificates for this domain.
💡 Add CAA records to restrict certificate issuance. Example: 0 issue "letsencrypt.org"
No TLS-RPT record found
Without TLS-RPT, you will not receive reports about TLS negotiation failures.
💡 Publish a _smtp._tls TXT record (e.g. "v=TLSRPTv1; rua=mailto:tls-reports@jd.com").
ARC support not detected
No evidence of ARC (Authenticated Received Chain) support on MX servers. Forwarded messages may lose authentication.
💡 Consider enabling ARC signing on your mail servers to preserve authentication through forwarding.
Very low TTL on MX records: 120s
2 MX records have a TTL of 120s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT record: 120s
The TXT record has a TTL of 120s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 120s
The SPF record has a TTL of 120s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 120s
The DMARC record has a TTL of 120s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (99 bytes)
SPF record is within safe DNS packet size limits.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
DKIM key strength indicates modern key management
All DKIM keys use RSA-2048+ or Ed25519, consistent with current best practices.
No external DMARC report destinations
All DMARC report URIs point to the same domain — no external authorization needed.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
Meets bulk sender authentication requirements
Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.
SMTP security checks passed
No open relay, VRFY/EXPN, or banner disclosure issues detected.
SMTP RFC 5321 compliance checks passed
The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.
NS delegation is properly configured
All nameservers are responsive, consistent, and properly secured.
DNS responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
DKIM2 not detected
No DKIM key record with v=2 was found across common selectors. DKIM2 is an emerging standard and not yet widely deployed.
DMARC alignment: adkim=r, aspf=r
DKIM alignment is relaxed, SPF alignment is relaxed.
DMARCbis np tag absent
The DMARC record does not include the np (non-existent subdomain policy) tag. Consider adding np=reject to protect non-existent subdomains under DMARCbis.
DMARCbis psd tag absent
The DMARC record does not include the psd (public suffix domain) indicator. Consider adding psd=n to explicitly identify this as an organizational domain.
REQUIRETLS not advertised
The primary MX does not advertise REQUIRETLS (RFC 8689). This is an emerging standard — MTA-STS and DANE provide adequate TLS enforcement for most deployments.
No DANE/TLSA records found
DANE is not configured for any MX server. This is optional but provides strong certificate binding.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open mail ports on mx1.jd.com
Detected open mail-related ports: 25
Domain is IPv4-only
No AAAA records found for the domain, MX servers, or nameservers. The domain operates on IPv4 only.
RFC 8058 one-click unsubscribe assessment
DKIM signing is configured. RFC 8058 compliance depends on List-Unsubscribe and List-Unsubscribe-Post headers being included in outbound messages and DKIM signatures.
MX IP network diversity
MX IPs span 2 different /16 networks, providing good diversity.
SOA record parameters
Serial: 2015280403, Refresh: 10800s, Retry: 3600s, Expire: 604800s, Min TTL: 38400s
Attack Surface Findings
Non-routable IPv4 in public DNS: imap.jd.com → 192.168.180.126
The subdomain imap.jd.com resolves to non-routable IP 192.168.180.126, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: vpn.jd.com → 172.31.12.1
The subdomain vpn.jd.com resolves to non-routable IP 172.31.12.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: admin.jd.com → 172.28.60.166
The subdomain admin.jd.com resolves to non-routable IP 172.28.60.166, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: admin.jd.com → 172.20.33.146
The subdomain admin.jd.com resolves to non-routable IP 172.20.33.146, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: admin.jd.com → 172.16.135.165
The subdomain admin.jd.com resolves to non-routable IP 172.16.135.165, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: portal.jd.com → 172.31.12.30
The subdomain portal.jd.com resolves to non-routable IP 172.31.12.30, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: dev.jd.com → 172.28.56.29
The subdomain dev.jd.com resolves to non-routable IP 172.28.56.29, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: dev.jd.com → 172.18.255.195
The subdomain dev.jd.com resolves to non-routable IP 172.18.255.195, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: test.jd.com → 192.168.171.197
The subdomain test.jd.com resolves to non-routable IP 192.168.171.197, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: cdn.jd.com → 172.20.35.68
The subdomain cdn.jd.com resolves to non-routable IP 172.20.35.68, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: store.jd.com → 172.18.255.156
The subdomain store.jd.com resolves to non-routable IP 172.18.255.156, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: store.jd.com → 172.28.56.180
The subdomain store.jd.com resolves to non-routable IP 172.28.56.180, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: docs.jd.com → 10.24.211.185
The subdomain docs.jd.com resolves to non-routable IP 10.24.211.185, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: status.jd.com → 172.20.37.68
The subdomain status.jd.com resolves to non-routable IP 172.20.37.68, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: status.jd.com → 172.18.227.67
The subdomain status.jd.com resolves to non-routable IP 172.18.227.67, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: git.jd.com → 172.20.39.31
The subdomain git.jd.com resolves to non-routable IP 172.20.39.31, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: ci.jd.com → 172.18.239.71
The subdomain ci.jd.com resolves to non-routable IP 172.18.239.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: grafana.jd.com → 172.20.37.182
The subdomain grafana.jd.com resolves to non-routable IP 172.20.37.182, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: grafana.jd.com → 10.199.200.42
The subdomain grafana.jd.com resolves to non-routable IP 10.199.200.42, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: grafana.jd.com → 172.18.227.241
The subdomain grafana.jd.com resolves to non-routable IP 172.18.227.241, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: prometheus.jd.com → 172.20.36.188
The subdomain prometheus.jd.com resolves to non-routable IP 172.20.36.188, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: prometheus.jd.com → 172.16.201.21
The subdomain prometheus.jd.com resolves to non-routable IP 172.16.201.21, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
DNSSEC is not enabled
No DNSKEY or DS records were found. DNS responses are not cryptographically authenticated.
💡 Enable DNSSEC by generating DNSKEY records and publishing DS records at the registrar.
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
All MX records resolve correctly
No dangling MX records detected — all MX hostnames resolve to valid IP addresses.
Explicit MX records present
The domain has explicit MX records — no implicit A-record fallback delivery.
No excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
36 subdomain(s) discovered for jd.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
0 certificate(s) found in CT logs
Certificate Transparency logs contain 0 certificate(s) for jd.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.jd.com, resolving to 111.13.28.191. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Microsoft Autodiscover endpoint detected (authenticated)
The Autodiscover endpoint at autodiscover.jd.com is active and requires authentication.
Mozilla Autoconfig endpoint detected
The Autoconfig endpoint at autoconfig.jd.com is publicly accessible.
Reputation Findings
Listed on dnsbl-3.uceprotect.net
103.107.89.10 (mx1.jd.com) is listed on blacklist dnsbl-3.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-3.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl.spfbl.net
103.107.89.10 (mx1.jd.com) is listed on blacklist dnsbl.spfbl.net (response: 127.0.0.5).
💡 Visit the dnsbl.spfbl.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl.spfbl.net
116.198.6.213 (mx.jd.com) is listed on blacklist dnsbl.spfbl.net (response: 127.0.0.4).
💡 Visit the dnsbl.spfbl.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
SMTP banner mismatch: jd
The SMTP banner identifies as 'jd' but the MX hostname is 'mx.jd.com'. Microsoft and other receivers flag this mismatch as suspicious infrastructure.
💡 Configure the SMTP server banner to match the MX hostname or PTR record (mx.jd.com).
Wildcard MX records detected
Domain jd.com has wildcard MX records, which can be abused for spam or phishing.
💡 Remove wildcard MX records and configure explicit MX entries only for legitimate mail-handling subdomains.
HSTS enabled but missing preload directive on jd.com
Strict-Transport-Security: max-age=3600
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
HSTS enabled but missing preload directive on webmail.jd.com
Strict-Transport-Security: max-age=31536000
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
security.txt present
Found security.txt at https://jd.com/.well-known/security.txt.
TLS certificate valid for 206 days
Certificate for jd.com expires on 2026-12-20.
Certificate issued by GlobalSign RSA OV SSL CA 2018
The certificate for jd.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for jd.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for jd.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for jd.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on jd.com.
Domain valid for 1015 days
Domain jd.com expires on 2029-03-08.
Domain transfer and delete locks enabled
Domain jd.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for jd.com do not match known disposable email provider patterns.
Domain is 12293 days old
Domain jd.com was registered 1992-09-29.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
DMARC reporting destinations look legitimate
DMARC rua/ruf addresses do not point to known URL shortener services.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (mx.jd.com) uses TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 including Forward Secrecy.
Google Safe Browsing DNS check — no flag detected
DNS-based Safe Browsing lookup returned no results. Full verification requires the Google Safe Browsing API key.
Abuse contacts found for MX IPs
Abuse contact information retrieved via abusix.org DNS lookup.
PhishTank — API key required
PhishTank phishing database check requires an API key.
Sender Score — API key required
Sender Score reputation check requires an API key.
Cisco Talos — API key required
Cisco Talos IP reputation check requires an API key.
WHOIS registration data
Registrar: MarkMonitor Information Technology (Shanghai) Co., Ltd. | Created: 1992-09-29 | Expires: 2029-03-08 | Updated: 2023-07-11
WHOIS privacy protection not detected
Domain jd.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
Bulletproof Hosting Detection — API key required
Checking IPs against known bulletproof hosting providers requires a threat intelligence API key.
Threat Intelligence Feeds — API key required
Checking domain against threat intelligence feeds requires API keys (e.g., VirusTotal, AbuseIPDB).
Typosquat detected: dj.com (has MX!), hd.com (has MX!), ud.com (has MX!), id.com (has MX!), md.com (has MX!)
23 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 23. Domains with MX records can send and receive email, making them high-risk phishing vectors.
Dependency Chains
DMARC Authentication Chain (SPF)
DMARC uses SPF to verify that emails come from authorized servers
SPF Record
SPF record found and configured
→
DMARC Policy
DMARC policy: none
DMARC Authentication Chain (DKIM)
DMARC uses DKIM to verify that emails have not been tampered with
DKIM Signature
DKIM signature configured
→
DMARC Policy
DMARC policy: none
Mail Server Identity: mx1.jd.com
PTR record proves mail server legitimacy
MX: mx1.jd.com
Mail server at 103.107.89.10
→
PTR Record
No PTR record
⚠️ Mail server mx1.jd.com (103.107.89.10) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: mx.jd.com
PTR record proves mail server legitimacy
MX: mx.jd.com
Mail server at mx.jd.com.gslb.qianxun.com
→
PTR Record
No PTR record
⚠️ Mail server mx.jd.com (mx.jd.com.gslb.qianxun.com) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Reputation: mx1.jd.com
RBL check ensures server is not blacklisted
MX: mx1.jd.com
Mail server at 103.107.89.10
→
RBL Status
Not blacklisted
Mail Server Reputation: mx.jd.com
RBL check ensures server is not blacklisted
MX: mx.jd.com
Mail server at mx.jd.com.gslb.qianxun.com
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
Mail servers support TLS encryption
→
MTA-STS Policy
Mode:
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC not enforced (p=none or missing)
→
BIMI Record
BIMI not configured
⚠️ DMARC is not enforced. BIMI requires a DMARC policy of "quarantine" or "reject" to prove you have strong email authentication. Without enforcement, email clients will not display your logo.
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
Mail servers support TLS encryption
→
TLS-RPT Reporting
TLS failure reporting configured
Security Checks
MX Records
✓
SPF Record
✓
DKIM Record
✓
DMARC Policy
✓
BIMI Record
✗
CAA Records
✗
DNSSEC
✗
MTA-STS
✓
TLS-RPT
✓
Embed Badge
Display your domain's security grade on your website or README:
<img src="https://scan.ractermx.com/badge/jd.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan jd.com Again