yjsry.com

Checked 22 October 2026, 11:40 UTC · via 8.8.8.8
✗Problems found
18 passed 4 warnings 1 failed 8 info

Registration

info

.com generic · Guangdong JinWanBang Technology Investment Co., Ltd. · expires 2027-05-23

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Guangdong JinWanBang Technology Investment Co., Ltd.
Registered
23 May 2022
Last changed
25 May 2026
Expires
23 May 2027
Status
active
Registry nameservers
ns10.ns365.net, ns9.ns365.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 2027-05-23 #3
    The registration is valid until 2027-05-23 (212 days).
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns10.ns365.net, ns9.ns365.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns10.ns365.net, ns9.ns365.net
NS in the zone
ns10.ns365.net, ns11.ns365.net, ns12.ns365.net, ns9.ns365.net
NameserverAddressesNetwork (AS)Glue
ns10.ns365.net124.173.109.204AS134764 CT-FoShan-IDC - CHINANET Guangdong province network, CN-
ns11.ns365.net (zone only)124.173.109.204AS134764 CT-FoShan-IDC - CHINANET Guangdong province network, CN-
ns12.ns365.net (zone only)124.173.109.204AS134764 CT-FoShan-IDC - CHINANET Guangdong province network, CN-
ns9.ns365.net124.173.109.205AS134764 CT-FoShan-IDC - CHINANET Guangdong province network, CN-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns10.ns365.net, ns9.ns365.net.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: ns11.ns365.net, ns12.ns365.net. ns11.ns365.net, ns12.ns365.net report NS ns10.ns365.net ns11.ns365.net ns12.ns365.net ns9.ns365.net.
    #7
  • ✓ 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.
  • !
    Nameservers in one network
    all IPv4 addresses are in 124.173.109.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS134764 (CT-FoShan-IDC - CHINANET Guangdong province network, CN): 4 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

fail

3 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns10.ns365.net 124.173.109.204no responsenono / no--
ns11.ns365.net 124.173.109.204NOERROR, 194 ms, authoritativenoyes / yesrefusedwww.gzidc.com
ns12.ns365.net 124.173.109.204NOERROR, 201 ms, authoritativenoyes / yesrefused-
ns9.ns365.net 124.173.109.205NOERROR, 194 ms, authoritativenoyes / yesrefusedwww.gzidc.com

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns10.ns365.net (124.173.109.204): read udp 46.225.38.91:54580->124.173.109.204:53: i/o timeout.
    #14
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns11.ns365.net: "www.gzidc.com"; ns9.ns365.net: "www.gzidc.com".
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

info

serial 2022052316 · primary main.ns365.net

Found

Primary (MNAME)
main.ns365.net
Contact (RNAME)
root.main.ns365.net
Serial
2022052316
Refresh / retry
10800 s / 2000 s
Expire
604800 s
Negative TTL
43200 s

Serial per nameserver

NameserverSerial
ns11.ns365.net (124.173.109.204)2022052316
ns12.ns365.net (124.173.109.204)2022052316
ns9.ns365.net (124.173.109.205)2022052316

Checks

  • ✓ Serial 2022052316 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 33m20s, expire 7d, negative TTL 12h.
  • i
    Hidden master
    The primary nameserver main.ns365.net is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact root@main.ns365.net #25
    The SOA RNAME root.main.ns365.net means root@main.ns365.net.
  • ✓ Date-based serial #26
    The serial 2022052316 follows the YYYYMMDDnn convention (2022-05-23).

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

6 records at the apex

Found

Read from
124.173.109.204:53
TypeValueTTL
SOAmain.ns365.net. root.main.ns365.net. 2022052316 10800 2000 604800 432003600
NSns12.ns365.net.3600
NSns10.ns365.net.3600
NSns11.ns365.net.3600
NSns9.ns365.net.3600
A8.148.221.1183600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, 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