SurfaceMap › j › jd.com

jd.com

Checked 2026-10-22 09:23 UTC · first added 2026-10-21
✗Problems found Score 57 of 100

Domain & DNS

warn

22 passed 5 warn 0 failed

Areas

iRegistration !Delegation !Nameservers ✓SOA !DNSSEC !Records

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: ns1.jd.com, ns2.jd.com, ns3.jd.com, ns4.jd.com, ns5.jd.com. ns1.jd.com, ns1.jdcache.com, ns2.jd.com, ns2.jdcache.com, ns3.jd.com, ns3.jdcache.com, ns4.jd.com, ns4.jdcache.com, ns5.jd.com, ns5.jdcache.com report NS ns1.jd.com ns1.jdcache.com ns2.jd.com ns2.jdcache.com ns3.jd.com ns3.jdcache.com ns4.jd.com ns4.jdcache.com ns5.jd.com ns5.jdcache.com.
    #7
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    No EDNS
    Nameservers · These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: ns1.jd.com (111.13.28.10), ns1.jdcache.com (111.13.28.10), ns2.jd.com (111.206.226.10), ns2.jdcache.com (111.206.226.10), ns3.jd.com (120.52.149.254), ns3.jdcache.com (120.52.149.254), ns4.jd.com (106.39.177.32), ns4.jdcache.com (106.39.177.32), ns5.jd.com (120.52.149.254), ns5.jdcache.com (120.52.149.254).
    #20
  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), MX (2m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for jd.com ›

Mail

fail

20 passed 6 warn 1 failed

Areas

✓SPF ✗DMARC !DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mx.jd.com, mx1.jd.com
    #11
  • !
    Hosts are CNAMEs
    MX · MX records must point to a host name with A/AAAA records, not to a CNAME: mx.jd.com -> mx.jd.com.gslb.qianxun.com
    #22
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), k1 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 116.198.24.244 (mx.jd.com), 103.107.89.10 (mx1.jd.com). Ask your hosting provider to set one.
    #30
  • !
    Not configured
    TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32

Recent checks

✗

Full report

Mail report for jd.com ›