jirenjituan.com

Checked 22 October 2026, 09:24 UTC · via 8.8.8.8
✗Problems found
22 passed 4 warnings 1 failed 4 info

Registration

info

.com generic · Xiamen 35.com Information Co., Ltd. · expires 2028-06-05

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Xiamen 35.com Information Co., Ltd.
Registered
5 June 2018
Last changed
19 May 2025
Expires
5 June 2028
Status
client transfer prohibited
Registry nameservers
ns1.35.net, ns2.35.net, ns3.35.net, ns4.35.net
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2028-06-05 #3
    The registration is valid until 2028-06-05 (591 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

ns1.35.net, ns2.35.net, ns3.35.net, ns4.35.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.35.net, ns2.35.net, ns3.35.net, ns4.35.net
NS in the zone
ns1.35.net, ns2.35.net, ns3.35.net, ns4.35.net
NameserverAddressesNetwork (AS)Glue
ns1.35.net118.123.253.132 118.123.249.114 60.247.150.254 240e:d9:c200::2AS38283 CHINANET-SCIDC-AS-AP - CHINANET SiChuan Telecom Internet Data Center, CN AS38283 CHINANET-SCIDC-AS-AP - CHINANET SiChuan Telecom Internet Data Center, CN AS38283 CHINANET-SCIDC-AS-AP - CHINANET SiChuan Telecom Internet Data Center, CN AS38283 CHINANET-SCIDC-AS-AP - CHINANET SiChuan Telecom Internet Data Center, CN-
ns2.35.net211.149.230.100 61.172.183.73 240e:d9:c200:1::2AS38283 CHINANET-SCIDC-AS-AP - CHINANET SiChuan Telecom Internet Data Center, CN AS4811 CHINANET-SHANGHAI-MAN - China Telecom (Group), CN AS38283 CHINANET-SCIDC-AS-AP - CHINANET SiChuan Telecom Internet Data Center, CN-
ns3.35.net118.123.249.114 61.172.183.77 240e:d9:c200::2AS38283 CHINANET-SCIDC-AS-AP - CHINANET SiChuan Telecom Internet Data Center, CN AS4811 CHINANET-SHANGHAI-MAN - China Telecom (Group), CN AS38283 CHINANET-SCIDC-AS-AP - CHINANET SiChuan Telecom Internet Data Center, CN-
ns4.35.net118.123.253.132 211.149.230.100 240e:d9:c200:1::2AS38283 CHINANET-SCIDC-AS-AP - CHINANET SiChuan Telecom Internet Data Center, CN AS38283 CHINANET-SCIDC-AS-AP - CHINANET SiChuan Telecom Internet Data Center, CN AS38283 CHINANET-SCIDC-AS-AP - CHINANET SiChuan Telecom Internet Data Center, CN-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.35.net, ns2.35.net, ns3.35.net, ns4.35.net.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • i
    One address family in one network
    all IPv6 addresses are in 240e:d9:c200::/48, while the other address family is spread over several networks.
    #10
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS38283 (CHINANET-SCIDC-AS-AP - CHINANET SiChuan Telecom Internet Data Center, CN): 11 addresses; AS4811 (CHINANET-SHANGHAI-MAN - China Telecom (Group), CN): 2 addresses.
  • i
    All nameserver names under .net
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

fail

13 of 13 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.35.net 118.123.253.132NOERROR, 215 ms, authoritativenoyes / yesrefusedv1.1
ns1.35.net 118.123.249.114NOERROR, 214 ms, authoritativenono / yesrefusedv1.1
ns1.35.net 60.247.150.254NOERROR, 213 ms, authoritativenoyes / yesrefusedv1.1
ns1.35.net 240e:d9:c200::2NOERROR, 251 ms, authoritativenono / yesrefusedv1.1
ns2.35.net 211.149.230.100NOERROR, 220 ms, authoritativenono / yesrefusedv1.1
ns2.35.net 61.172.183.73NOERROR, 228 ms, authoritativenono / norefusedv1.1
ns2.35.net 240e:d9:c200:1::2NOERROR, 228 ms, authoritativenono / yesrefusedv1.1
ns3.35.net 118.123.249.114NOERROR, 232 ms, authoritativenono / yesrefusedv1.1
ns3.35.net 61.172.183.77NOERROR, 200 ms, authoritativenono / norefusedv1.1
ns3.35.net 240e:d9:c200::2NOERROR, 246 ms, authoritativenono / yesrefusedv1.1
ns4.35.net 118.123.253.132NOERROR, 233 ms, authoritativenoyes / yesrefusedv1.1
ns4.35.net 211.149.230.100NOERROR, 218 ms, authoritativenono / yesrefusedv1.1
ns4.35.net 240e:d9:c200:1::2NOERROR, 236 ms, authoritativenono / yesrefusedv1.1

Checks

  • ✓ All respond #14
    All 13 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.35.net: "v1.1"; ns2.35.net: "v1.1"; ns3.35.net: "v1.1"; ns4.35.net: "v1.1". Hide or replace the version string.
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns1.35.net (118.123.249.114): dial tcp 118.123.249.114:53: i/o timeout; ns1.35.net (240e:d9:c200::2): dial tcp [240e:d9:c200::2]:53: i/o timeout; ns2.35.net (211.149.230.100): dial tcp 211.149.230.100:53: i/o timeout; ns2.35.net (61.172.183.73): dial tcp 61.172.183.73:53: i/o timeout; ns2.35.net (240e:d9:c200:1::2): dial tcp [240e:d9:c200:1::2]:53: i/o timeout; ns3.35.net (118.123.249.114): dial tcp 118.123.249.114:53: i/o timeout; ns3.35.net (61.172.183.77): dial tcp 61.172.183.77:53: i/o timeout; ns3.35.net (240e:d9:c200::2): dial tcp [240e:d9:c200::2]:53: i/o timeout; ns4.35.net (211.149.230.100): dial tcp 211.149.230.100:53: i/o timeout; ns4.35.net (240e:d9:c200:1::2): dial tcp [240e:d9:c200:1::2]:53: i/o timeout.
    #19
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: ns2.35.net (61.172.183.73), ns3.35.net (61.172.183.77).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 2026042608 · primary ns1.35.net

Found

Primary (MNAME)
ns1.35.net
Contact (RNAME)
dnsconct.myhostadmin.net
Serial
2026042608
Refresh / retry
3600 s / 300 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.35.net (118.123.253.132)2026042608
ns1.35.net (118.123.249.114)2026042608
ns1.35.net (60.247.150.254)2026042608
ns1.35.net (240e:d9:c200::2)2026042608
ns2.35.net (211.149.230.100)2026042608
ns2.35.net (61.172.183.73)2026042607
ns2.35.net (240e:d9:c200:1::2)2026042607
ns3.35.net (118.123.249.114)2026042608
ns3.35.net (61.172.183.77)2026042607
ns3.35.net (240e:d9:c200::2)2026042608
ns4.35.net (118.123.253.132)2026042608
ns4.35.net (211.149.230.100)2026042608
ns4.35.net (240e:d9:c200:1::2)2026042607

Checks

  • !
    Serials differ
    The nameservers serve different versions of the zone: 2026042607 on ns2.35.net (61.172.183.73), ns2.35.net (240e:d9:c200:1::2), ns3.35.net (61.172.183.77), ns4.35.net (240e:d9:c200:1::2); 2026042608 on ns1.35.net (118.123.253.132), ns1.35.net (118.123.249.114), ns1.35.net (60.247.150.254), ns1.35.net (240e:d9:c200::2), ns2.35.net (211.149.230.100), ns3.35.net (118.123.249.114), ns3.35.net (240e:d9:c200::2), ns4.35.net (118.123.253.132), ns4.35.net (211.149.230.100). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 5m, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.35.net is one of the listed nameservers.
  • ✓ Contact dnsconct@myhostadmin.net #25
    The SOA RNAME dnsconct.myhostadmin.net means dnsconct@myhostadmin.net.
  • ✓ Date-based serial #26
    The serial 2026042608 follows the YYYYMMDDnn convention (2026-04-26).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    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

Records

info

8 records at the apex

Found

Read from
118.123.253.132:53
TypeValueTTL
NSns1.35.net.3600
NSns3.35.net.3600
NSns2.35.net.3600
NSns4.35.net.3600
A60.247.208.2001800
MX10 mxbiz2.qq.com.1800
MX5 mxbiz1.qq.com.1800
TXT"v=spf1 include:spf.exmail.qq.com ~all"1800

Checks

  • ✓ TTLs within range #32
    TTLs: A 30m, MX 30m, NS 1h. The NS TTL at the parent is 2d and in the zone 1h; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35