jylebao.com

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

Registration

info

.com generic · Cloud Yuqu LLC · expires 2028-04-13

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Cloud Yuqu LLC
Registered
13 April 2020
Last changed
28 April 2025
Expires
13 April 2028
Status
active
Registry nameservers
ns3.myhostadmin.net, ns4.myhostadmin.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-04-13 #3
    The registration is valid until 2028-04-13 (538 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

ns3.myhostadmin.net, ns4.myhostadmin.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns3.myhostadmin.net, ns4.myhostadmin.net
NS in the zone
ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net
NameserverAddressesNetwork (AS)Glue
ns1.myhostadmin.net (zone only)60.247.150.254 118.123.253.132 118.123.249.114 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.myhostadmin.net (zone only)61.172.183.73 211.149.230.100 240e:d9:c200:1::2AS4811 CHINANET-SHANGHAI-MAN - China Telecom (Group), 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-
ns3.myhostadmin.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.myhostadmin.net211.149.230.100 118.123.253.132 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-
ns5.myhostadmin.net (zone only)118.123.249.114 61.172.183.73 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-
ns6.myhostadmin.net (zone only)60.247.150.13 118.123.253.132 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

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns3.myhostadmin.net, ns4.myhostadmin.net.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: ns1.myhostadmin.net, ns2.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net. ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net report NS ns1.myhostadmin.net ns2.myhostadmin.net ns3.myhostadmin.net ns4.myhostadmin.net ns5.myhostadmin.net ns6.myhostadmin.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.
  • 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): 16 addresses; AS4811 (CHINANET-SHANGHAI-MAN - China Telecom (Group), CN): 3 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

19 of 19 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.myhostadmin.net 60.247.150.254NOERROR, 211 ms, authoritativenoyes / yesrefusedv1.1
ns1.myhostadmin.net 118.123.253.132NOERROR, 238 ms, authoritativenoyes / yesrefusedv1.1
ns1.myhostadmin.net 118.123.249.114NOERROR, 211 ms, authoritativenono / yesrefusedv1.1
ns1.myhostadmin.net 240e:d9:c200::2NOERROR, 233 ms, authoritativenono / yesrefusedv1.1
ns2.myhostadmin.net 61.172.183.73NOERROR, 235 ms, authoritativenono / norefusedv1.1
ns2.myhostadmin.net 211.149.230.100NOERROR, 230 ms, authoritativenono / yesrefusedv1.1
ns2.myhostadmin.net 240e:d9:c200:1::2NOERROR, 247 ms, authoritativenono / yesrefusedv1.1
ns3.myhostadmin.net 118.123.249.114NOERROR, 219 ms, authoritativenono / yesrefusedv1.1
ns3.myhostadmin.net 61.172.183.77NOERROR, 197 ms, authoritativenono / norefusedv1.1
ns3.myhostadmin.net 240e:d9:c200::2NOERROR, 239 ms, authoritativenono / yesrefusedv1.1
ns4.myhostadmin.net 211.149.230.100NOERROR, 231 ms, authoritativenono / yesrefusedv1.1
ns4.myhostadmin.net 118.123.253.132NOERROR, 222 ms, authoritativenoyes / yesrefusedv1.1
ns4.myhostadmin.net 240e:d9:c200:1::2NOERROR, 244 ms, authoritativenono / yesrefusedv1.1
ns5.myhostadmin.net 118.123.249.114NOERROR, 212 ms, authoritativenono / yesrefusedv1.1
ns5.myhostadmin.net 61.172.183.73NOERROR, 207 ms, authoritativenono / norefusedv1.1
ns5.myhostadmin.net 240e:d9:c200::2NOERROR, 249 ms, authoritativenono / yesrefusedv1.1
ns6.myhostadmin.net 60.247.150.13NOERROR, 217 ms, authoritativenoyes / yesrefusedv1.1
ns6.myhostadmin.net 118.123.253.132NOERROR, 230 ms, authoritativenoyes / yesrefusedv1.1
ns6.myhostadmin.net 240e:d9:c200:1::2NOERROR, 240 ms, authoritativenono / yesrefusedv1.1

Checks

  • ✓ All respond #14
    All 19 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.myhostadmin.net: "v1.1"; ns2.myhostadmin.net: "v1.1"; ns3.myhostadmin.net: "v1.1"; ns4.myhostadmin.net: "v1.1"; ns5.myhostadmin.net: "v1.1"; ns6.myhostadmin.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.myhostadmin.net (118.123.249.114): dial tcp 118.123.249.114:53: i/o timeout; ns1.myhostadmin.net (240e:d9:c200::2): dial tcp [240e:d9:c200::2]:53: i/o timeout; ns2.myhostadmin.net (61.172.183.73): dial tcp 61.172.183.73:53: i/o timeout; ns2.myhostadmin.net (211.149.230.100): dial tcp 211.149.230.100:53: i/o timeout; ns2.myhostadmin.net (240e:d9:c200:1::2): dial tcp [240e:d9:c200:1::2]:53: i/o timeout; ns3.myhostadmin.net (118.123.249.114): dial tcp 118.123.249.114:53: i/o timeout; ns3.myhostadmin.net (61.172.183.77): dial tcp 61.172.183.77:53: i/o timeout; ns3.myhostadmin.net (240e:d9:c200::2): dial tcp [240e:d9:c200::2]:53: i/o timeout; ns4.myhostadmin.net (211.149.230.100): dial tcp 211.149.230.100:53: i/o timeout; ns4.myhostadmin.net (240e:d9:c200:1::2): dial tcp [240e:d9:c200:1::2]:53: i/o timeout; ns5.myhostadmin.net (118.123.249.114): dial tcp 118.123.249.114:53: i/o timeout; ns5.myhostadmin.net (61.172.183.73): dial tcp 61.172.183.73:53: i/o timeout; ns5.myhostadmin.net (240e:d9:c200::2): dial tcp [240e:d9:c200::2]:53: i/o timeout; ns6.myhostadmin.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.myhostadmin.net (61.172.183.73), ns3.myhostadmin.net (61.172.183.77), ns5.myhostadmin.net (61.172.183.73).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2020051206 · primary ns1.myhostadmin.net

Found

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

Serial per nameserver

NameserverSerial
ns1.myhostadmin.net (60.247.150.254)2020051206
ns1.myhostadmin.net (118.123.253.132)2020051206
ns1.myhostadmin.net (118.123.249.114)2020051206
ns1.myhostadmin.net (240e:d9:c200::2)2020051206
ns2.myhostadmin.net (61.172.183.73)2020051206
ns2.myhostadmin.net (211.149.230.100)2020051206
ns2.myhostadmin.net (240e:d9:c200:1::2)2020051206
ns3.myhostadmin.net (118.123.249.114)2020051206
ns3.myhostadmin.net (61.172.183.77)2020051206
ns3.myhostadmin.net (240e:d9:c200::2)2020051206
ns4.myhostadmin.net (211.149.230.100)2020051206
ns4.myhostadmin.net (118.123.253.132)2020051206
ns4.myhostadmin.net (240e:d9:c200:1::2)2020051206
ns5.myhostadmin.net (118.123.249.114)2020051206
ns5.myhostadmin.net (61.172.183.73)2020051206
ns5.myhostadmin.net (240e:d9:c200::2)2020051206
ns6.myhostadmin.net (60.247.150.13)2020051206
ns6.myhostadmin.net (118.123.253.132)2020051206
ns6.myhostadmin.net (240e:d9:c200:1::2)2020051206

Checks

  • ✓ Serial 2020051206 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 12h, retry 5m, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.myhostadmin.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 2020051206 follows the YYYYMMDDnn convention (2020-05-12).

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
60.247.150.254:53
TypeValueTTL
SOAns1.myhostadmin.net. dnsconct.myhostadmin.net. 2020051206 43200 300 1209600 3600500
NSns1.myhostadmin.net.3600
NSns4.myhostadmin.net.3600
NSns3.myhostadmin.net.3600
NSns2.myhostadmin.net.3600
NSns5.myhostadmin.net.3600
NSns6.myhostadmin.net.3600
A211.149.249.27900

Checks

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