SurfaceMap › z › zongheng.com

zongheng.com

Checked 2026-10-22 11:44 UTC · first added 2026-10-21
✗Problems found Score 17 of 100

Domain & DNS

fail

16 passed 6 warn 3 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns3.dnsv4.com (125.94.59.153): read udp 46.225.38.91:47919->125.94.59.153:53: i/o timeout.
    #14
  • ✗
    Lame delegation
    Nameservers · These nameservers don't answer authoritatively for the zone, so resolvers ignore them: ns3.dnsv4.com (43.134.249.54): REFUSED, authoritative=true; ns3.dnsv4.com (36.155.149.53): REFUSED, authoritative=true; ns3.dnsv4.com (1.12.0.24): REFUSED, authoritative=true; ns3.dnsv4.com (124.64.205.153): REFUSED, authoritative=true; ns3.dnsv4.com (1.13.76.53): REFUSED, authoritative=true; ns3.dnsv4.com (1.12.0.25): REFUSED, authoritative=true; ns3.dnsv4.com (2402:4e00:1470:2::10): REFUSED, authoritative=true; ns4.dnsv4.com (1.12.0.23): REFUSED, authoritative=true; ns4.dnsv4.com (220.196.136.53): REFUSED, authoritative=true; ns4.dnsv4.com (163.177.5.53): REFUSED, authoritative=true; ns4.dnsv4.com (111.13.203.53): REFUSED, authoritative=true; ns4.dnsv4.com (43.130.172.54): REFUSED, authoritative=true; ns4.dnsv4.com (1.12.0.26): REFUSED, authoritative=true; ns4.dnsv4.com (49.7.107.153): REFUSED, authoritative=true; ns4.dnsv4.com (101.227.168.53): REFUSED, authoritative=true; ns4.dnsv4.com (117.135.128.153): REFUSED, authoritative=true; ns4.dnsv4.com (2402:4e00:111:fff::d): REFUSED, authoritative=true.
    #15
  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns3.dnsv4.com (43.134.249.54): ; ns3.dnsv4.com (36.155.149.53): ; ns3.dnsv4.com (1.12.0.24): ; ns3.dnsv4.com (124.64.205.153): ; ns3.dnsv4.com (1.13.76.53): ; ns3.dnsv4.com (1.12.0.25): ; ns3.dnsv4.com (2402:4e00:1470:2::10): ; ns4.dnsv4.com (1.12.0.23): ; ns4.dnsv4.com (220.196.136.53): ; ns4.dnsv4.com (163.177.5.53): ; ns4.dnsv4.com (111.13.203.53): ; ns4.dnsv4.com (43.130.172.54): ; ns4.dnsv4.com (1.12.0.26): ; ns4.dnsv4.com (49.7.107.153): ; ns4.dnsv4.com (101.227.168.53): ; ns4.dnsv4.com (117.135.128.153): ; ns4.dnsv4.com (2402:4e00:111:fff::d): .
    #19
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: ns3.dnsv4.com, ns4.dnsv4.com. vip3.alidns.com, vip4.alidns.com report NS ns3.dnsv4.com ns4.dnsv4.com vip3.alidns.com vip4.alidns.com.
    #7
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: vip3.alidns.com (glue 121.40.6.163, 140.205.1.5, 170.33.32.210, 170.33.73.26, 170.33.80.10, 2408:4009:500::3, 39.103.26.212, 47.108.36.163, 47.116.84.178, 8.129.152.245, 8.212.93.3, zone 170.33.32.210, 140.205.1.5, 170.33.80.10, 8.212.93.3, 170.33.73.26, 2408:4009:500::3); vip4.alidns.com (glue 121.40.6.164, 140.205.1.6, 170.33.32.211, 170.33.73.27, 170.33.80.11, 2408:4009:500::4, 39.103.26.213, 47.108.36.164, 47.116.84.179, 8.129.152.246, 8.212.93.4, zone 140.205.1.6, 170.33.80.11, 170.33.32.211, 170.33.73.27, 8.212.93.4, 2408:4009:500::4). Update the glue at your registrar.
    #8
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns3.dnsv4.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; ns4.dnsv4.com: "DNSPod AUTHORITY DNS 7.3.2512.01". Hide or replace the version string.
    #17
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 2023101216 on vip3.alidns.com (170.33.73.26), vip3.alidns.com (2408:4009:500::3), vip4.alidns.com (140.205.1.6), vip4.alidns.com (170.33.73.27); 2026081316 on vip4.alidns.com (8.212.93.4); 2026081716 on vip3.alidns.com (170.33.80.10), vip4.alidns.com (170.33.80.11); 2026081810 on vip3.alidns.com (170.33.32.210), vip3.alidns.com (8.212.93.3), vip4.alidns.com (170.33.32.211), vip4.alidns.com (2408:4009:500::4); 2026082415 on vip3.alidns.com (140.205.1.5). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    Unusual SOA timers
    SOA · expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 1h, retry 20m, expire 1d, negative TTL 10m.
    #23
  • !
    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

Recent checks

✗

Full report

Domain & DNS report for zongheng.com ›

Mail

fail

18 passed 5 warn 2 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
  • ✗
    No DKIM keys published
    DKIM · _domainkey.zongheng.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    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: mxbiz1.qq.com, mxbiz2.qq.com
    #11
  • !
    Report address not authorized
    DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:mailauth-reports@qq.com (needs zongheng.com._report._dmarc.qq.com). Ask the report provider to publish the record, or check the address.
    #29
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 103.86.78.2 (mxbiz1.qq.com), 103.86.78.3 (mxbiz1.qq.com), 43.154.252.202 (mxbiz2.qq.com), 43.154.252.16 (mxbiz2.qq.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 zongheng.com ›