SurfaceMap › i › item.jd.com

item.jd.com

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

Domain & DNS

fail

21 passed 5 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC !Records

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns4.jd.com (106.39.177.32): read udp 46.225.38.91:60109->106.39.177.32:53: i/o timeout.
    #14
  • !
    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.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.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 item.jd.com ›

Mail

fail

4 passed 3 warn 2 failed

Areas

✗SPF ✗DMARC !DKIM !DNSSEC !MX 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
  • ✗
    No SPF record
    SPF · No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.
    #6
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    No MX records
    MX · No MX records found. If this domain is used for email, add MX records to specify mail servers. If it never receives mail, publish a null MX ("MX 0 .").
    #9

Recent checks

✗

Full report

Mail report for item.jd.com ›