SurfaceMap › y › yunzhan365.com

yunzhan365.com

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

Domain & DNS

fail

17 passed 4 warn 2 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC ✗Records

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: dns14.hichina.com (47.118.199.201): read udp 46.225.38.91:43652->47.118.199.201:53: i/o timeout.
    #14
  • ✗
    CNAME at the apex
    Records · The zone apex is a CNAME to yunzhan365.com.w.kunluncan.com. A CNAME can't coexist with the SOA and NS records (RFC 1034); use your provider's ALIAS/flattening feature instead.
    #33
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns1.alidns.com, ns2.alidns.com; only in the zone: dns13.hichina.com, dns14.hichina.com. dns13.hichina.com, dns14.hichina.com, ns1.alidns.com, ns2.alidns.com report NS dns13.hichina.com dns14.hichina.com.
    #7
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 2015033015 on ns1.alidns.com (139.224.142.115), ns1.alidns.com (139.224.142.125), ns2.alidns.com (139.224.142.126); 2026081813 on dns14.hichina.com (120.76.107.51), ns1.alidns.com (120.76.107.45), ns1.alidns.com (2408:4009:501::1); 2026082509 on dns14.hichina.com (139.224.142.121), dns14.hichina.com (120.76.107.41), dns14.hichina.com (2408:4009:501::22), ns2.alidns.com (139.224.142.116); 2026082616 on dns13.hichina.com (120.76.107.52), dns13.hichina.com (39.96.153.42), dns13.hichina.com (120.76.107.42), dns13.hichina.com (39.96.153.52), dns13.hichina.com (47.118.199.202), dns13.hichina.com (2408:4009:501::21), dns14.hichina.com (39.96.153.41), dns14.hichina.com (47.118.199.211), dns14.hichina.com (39.96.153.51), dns14.hichina.com (139.224.142.111), ns1.alidns.com (47.118.199.205), ns1.alidns.com (39.96.153.55), ns2.alidns.com (120.76.107.46), ns2.alidns.com (39.96.153.56), ns2.alidns.com (39.96.153.46), ns2.alidns.com (2408:4009:501::2); 2026082617 on dns13.hichina.com (47.118.199.212), ns1.alidns.com (39.96.153.45), ns1.alidns.com (120.76.107.55), ns2.alidns.com (47.118.199.206), ns2.alidns.com (120.76.107.56); 2026082709 on dns13.hichina.com (139.224.142.122), dns13.hichina.com (139.224.142.112); 2026082815 on ns1.alidns.com (47.118.199.215), ns2.alidns.com (47.118.199.216). 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 yunzhan365.com ›

Mail

fail

15 passed 5 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
  • !
    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
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mxbiz1.qq.com, mxbiz2.qq.com
    #11
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 103.86.78.3 (mxbiz1.qq.com), 103.86.78.2 (mxbiz1.qq.com), 43.154.252.16 (mxbiz2.qq.com), 43.154.252.202 (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 yunzhan365.com ›