SurfaceMap › v › vzan.com

vzan.com

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

Domain & DNS

fail

21 passed 6 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: ns3.dnsv5.com (1.12.14.18): read udp 46.225.38.91:35149->1.12.14.18:53: i/o timeout.
    #14
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns4.dnsv4.com. ns3.dnsv5.com, ns4.dnsv4.com, ns4.dnsv5.com report NS ns3.dnsv5.com ns4.dnsv5.com.
    #7
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns3.dnsv5.com (glue 1.12.0.17, 1.12.0.18, 1.12.14.17, 1.12.14.18, 101.227.168.52, 108.136.87.44, 163.177.5.52, 220.196.136.52, 2402:4e00:1470:2::f, 35.165.107.227, zone 13.37.58.163, 162.62.49.74, 163.177.5.52, 15.160.102.38, 1.12.14.18, 1.12.14.17, 1.12.0.18, 18.134.75.163, 1.12.0.17, 240d:c000:3011::10); ns4.dnsv5.com (glue 1.12.0.16, 1.12.0.19, 1.12.14.16, 1.12.14.19, 117.135.128.152, 124.64.205.152, 13.37.58.163, 2402:4e00:111:fff::8, 49.7.107.152, zone 18.194.2.137, 63.34.1.181, 1.12.0.19, 1.12.14.19, 162.62.49.12, 13.48.202.4, 1.12.0.16, 1.12.14.16, 240d:c000:3011::f). 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.dnsv5.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; ns4.dnsv4.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; ns4.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 (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 vzan.com ›

Mail

fail

15 passed 4 warn 2 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
  • ✗
    No DKIM keys published
    DKIM · _domainkey.vzan.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: mx1.qiye.aliyun.com, mx2.qiye.aliyun.com, mx3.qiye.aliyun.com
    #11
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 47.246.167.188 (mx1.qiye.aliyun.com), 47.246.146.255 (mx2.qiye.aliyun.com), 47.246.137.47 (mx3.qiye.aliyun.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 vzan.com ›