SurfaceMap › x › xinnet.com

xinnet.com

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

Domain & DNS

fail

20 passed 5 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns17.xincache.com (125.94.59.210): read udp 46.225.38.91:58129->125.94.59.210:53: i/o timeout; ns17.xincache.com (2402:4e00:1470:2::e): read udp [2a01:4f8:1c1c:eebf::1]:33347->[2402:4e00:1470:2::e]: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: ns17.xincache.com, ns18.xincache.com; only in the zone: ns11.xincache.com, ns12.xincache.com. ns11.xincache.com, ns12.xincache.com, ns17.xincache.com, ns18.xincache.com report NS ns11.xincache.com ns12.xincache.com.
    #7
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns17.xincache.com (glue 1.12.0.4, 112.80.181.45, 117.89.178.173, 129.211.176.209, 2402:4e00:1470:2::e, 36.155.149.180, zone 117.89.178.173, 1.12.0.4, 129.211.176.209, 125.94.59.210, 112.80.181.45, 36.155.149.180, 2402:4e00:1730::e, 2402:4e00:1470:2::e); ns18.xincache.com (glue 1.12.0.1, 112.80.181.111, 117.89.178.184, 129.211.176.239, 2402:4e00:111:fff::c, 36.155.149.176, zone 36.155.149.176, 1.12.0.1, 163.177.5.23, 112.80.181.111, 129.211.176.239, 117.89.178.184, 2402:4e00:111:fff::c). 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: ns11.xincache.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; ns12.xincache.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; ns17.xincache.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; ns18.xincache.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

Recent checks

✗

Full report

Domain & DNS report for xinnet.com ›

Mail

fail

17 passed 6 warn 1 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 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: mxc.global-mail.cn, mxu.global-mail.cn
    #11
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 101.36.121.182 (mxc.global-mail.cn). 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 xinnet.com ›