SurfaceMap › k › kuaidi100.com

kuaidi100.com

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

Domain & DNS

warn

20 passed 6 warn 0 failed

Areas

iRegistration !Delegation !Nameservers !SOA !DNSSEC !Records

Problems

  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns1.dnsv5.com (glue 1.12.0.17, 1.12.0.18, 1.12.0.20, 1.12.14.18, 101.227.168.52, 108.136.87.44, 163.177.5.52, 18.194.2.137, 35.165.107.227, 36.155.149.52, 52.220.136.67, zone 1.12.0.20, 1.12.0.18, 1.12.14.18, 52.220.136.67, 1.12.0.17, 18.194.2.137, 101.227.168.52, 36.155.149.52, 163.177.5.52); ns2.dnsv5.com (glue 1.12.0.16, 1.12.0.19, 1.12.14.19, 117.135.128.152, 117.89.178.52, 13.37.58.163, 150.109.248.236, 49.7.107.152, 52.198.159.146, zone 1.12.0.19, 1.12.14.19, 52.198.159.146, 117.89.178.52, 49.7.107.152, 117.135.128.152, 1.12.0.16). Update the glue at your registrar.
    #8
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.dnsv5.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; ns2.dnsv5.com: "DNSPod AUTHORITY DNS 7.3.2512.01". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1h, retry 3m, expire 14d, negative TTL 3m.
    #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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (10s). 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 kuaidi100.com ›

Mail

fail

16 passed 6 warn 1 failed

Areas

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

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • !
    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: mail.kuaidi100.com
    #11
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: dkim (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: 120.92.182.57 (mail.kuaidi100.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 kuaidi100.com ›