bjcxzlfw.com

Checked 22 October 2026, 08:00 UTC · via 8.8.8.8
✗Problems found
20 passed 3 warnings 2 failed 6 info

Registration

info

.com generic · Dynadot Inc · expires 2027-06-02

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Dynadot Inc
Registered
2 June 2023
Last changed
14 July 2026
Expires
2 June 2027
Status
active
Registry nameservers
ns1.363.hk, ns2.363.hk, ns3.363.hk, ns4.363.hk, ns5.363.hk, ns6.363.hk
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-06-02 #3
    The registration is valid until 2027-06-02 (222 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

info

ns1.363.hk, ns2.363.hk, ns3.363.hk, ns4.363.hk, ns5.363.hk, ns6.363.hk

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.363.hk, ns2.363.hk, ns3.363.hk, ns4.363.hk, ns5.363.hk, ns6.363.hk
NS in the zone
ns1.363.hk, ns2.363.hk, ns3.363.hk, ns4.363.hk, ns5.363.hk, ns6.363.hk
NameserverAddressesNetwork (AS)Glue
ns1.363.hk60.247.150.254 118.123.249.114 118.123.253.132 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.363.hk211.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.363.hk61.172.183.77 118.123.249.114 240e:d9:c200::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-
ns4.363.hk211.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.363.hk61.172.183.73 118.123.249.114 240e:d9:c200::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-
ns6.363.hk118.123.253.132 60.247.150.13 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

  • ✓ 6 nameservers #6
    Delegated to ns1.363.hk, ns2.363.hk, ns3.363.hk, ns4.363.hk, ns5.363.hk, ns6.363.hk.
  • ✓ 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): 16 addresses; AS4811 (CHINANET-SHANGHAI-MAN - China Telecom (Group), CN): 3 addresses.
  • i
    All nameserver names under .hk
    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

16 of 19 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.363.hk 60.247.150.254NOERROR, 213 ms, authoritativenoyes / yesrefusedv1.1
ns1.363.hk 118.123.249.114NOERROR, 220 ms, authoritativenono / yesrefusedv1.1
ns1.363.hk 118.123.253.132NOERROR, 228 ms, authoritativenoyes / yesrefusedv1.1
ns1.363.hk 240e:d9:c200::2no responsenono / no--
ns2.363.hk 211.149.230.100NOERROR, 217 ms, authoritativenono / yesrefusedv1.1
ns2.363.hk 61.172.183.73no responsenono / no--
ns2.363.hk 240e:d9:c200:1::2NOERROR, 237 ms, authoritativenono / yesrefusedv1.1
ns3.363.hk 61.172.183.77NOERROR, 241 ms, authoritativenono / norefusedv1.1
ns3.363.hk 118.123.249.114NOERROR, 228 ms, authoritativenono / yesrefusedv1.1
ns3.363.hk 240e:d9:c200::2NOERROR, 240 ms, authoritativenono / yesrefusedv1.1
ns4.363.hk 211.149.230.100NOERROR, 225 ms, authoritativenono / yesrefusedv1.1
ns4.363.hk 118.123.253.132NOERROR, 243 ms, authoritativenoyes / yesrefusedv1.1
ns4.363.hk 240e:d9:c200:1::2NOERROR, 228 ms, authoritativenono / yesrefusedv1.1
ns5.363.hk 61.172.183.73NOERROR, 198 ms, authoritativenono / norefusedv1.1
ns5.363.hk 118.123.249.114NOERROR, 214 ms, authoritativenono / yesrefusedv1.1
ns5.363.hk 240e:d9:c200::2NOERROR, 234 ms, authoritativenono / yesrefusedv1.1
ns6.363.hk 118.123.253.132no responsenono / no--
ns6.363.hk 60.247.150.13NOERROR, 210 ms, authoritativenoyes / yesrefusedv1.1
ns6.363.hk 240e:d9:c200:1::2NOERROR, 242 ms, authoritativenono / yesrefusedv1.1

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns1.363.hk (240e:d9:c200::2): read udp [2a01:4f8:1c1c:eebf::1]:50836->[240e:d9:c200::2]:53: i/o timeout; ns2.363.hk (61.172.183.73): read udp 46.225.38.91:44798->61.172.183.73:53: i/o timeout; ns6.363.hk (118.123.253.132): read udp 46.225.38.91:49051->118.123.253.132: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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.363.hk: "v1.1"; ns2.363.hk: "v1.1"; ns3.363.hk: "v1.1"; ns4.363.hk: "v1.1"; ns5.363.hk: "v1.1"; ns6.363.hk: "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.363.hk (118.123.249.114): dial tcp 118.123.249.114:53: i/o timeout; ns2.363.hk (211.149.230.100): dial tcp 211.149.230.100:53: i/o timeout; ns2.363.hk (240e:d9:c200:1::2): dial tcp [240e:d9:c200:1::2]:53: i/o timeout; ns3.363.hk (61.172.183.77): dial tcp 61.172.183.77:53: i/o timeout; ns3.363.hk (118.123.249.114): dial tcp 118.123.249.114:53: i/o timeout; ns3.363.hk (240e:d9:c200::2): dial tcp [240e:d9:c200::2]:53: i/o timeout; ns4.363.hk (211.149.230.100): dial tcp 211.149.230.100:53: i/o timeout; ns4.363.hk (240e:d9:c200:1::2): dial tcp [240e:d9:c200:1::2]:53: i/o timeout; ns5.363.hk (61.172.183.73): dial tcp 61.172.183.73:53: i/o timeout; ns5.363.hk (118.123.249.114): dial tcp 118.123.249.114:53: i/o timeout; ns5.363.hk (240e:d9:c200::2): dial tcp [240e:d9:c200::2]:53: i/o timeout; ns6.363.hk (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: ns3.363.hk (61.172.183.77), ns5.363.hk (61.172.183.73).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2026082809 · primary ns1.363.hk

Found

Primary (MNAME)
ns1.363.hk
Contact (RNAME)
dnsconct.363.hk
Serial
2026082809
Refresh / retry
3600 s / 300 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

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

Checks

  • ✓ Serial 2026082809 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 5m, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.363.hk is one of the listed nameservers.
  • ✓ Contact dnsconct@363.hk #25
    The SOA RNAME dnsconct.363.hk means dnsconct@363.hk.
  • ✓ Date-based serial #26
    The serial 2026082809 follows the YYYYMMDDnn convention (2026-08-28).

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.363.hk. dnsconct.363.hk. 2026082809 3600 300 1209600 36003600
NSns2.363.hk.3600
NSns4.363.hk.3600
NSns1.363.hk.3600
NSns5.363.hk.3600
NSns6.363.hk.3600
NSns3.363.hk.3600
A38.55.45.129900

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.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • 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