lanzoui.com

Checked 22 October 2026, 09:34 UTC · via 8.8.8.8
✗Problems found
19 passed 2 warnings 2 failed 8 info

Registration

info

.com generic · Alibaba Cloud Computing (Beijing) Co., Ltd. · expires 2027-03-28

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Alibaba Cloud Computing (Beijing) Co., Ltd.
Registered
28 March 2018
Last changed
23 June 2026
Expires
28 March 2027
Status
active
Registry nameservers
ns1.dns.com, ns2.dns.com
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-03-28 #3
    The registration is valid until 2027-03-28 (157 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

ns1.dns.com, ns2.dns.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.dns.com, ns2.dns.com
NS in the zone
ns1.dns.com, ns2.dns.com
NameserverAddressesNetwork (AS)Glue
ns1.dns.com154.86.21.128 177.2.31.128 2001:df2:f080:2::1:1AS140227 HKCICL-AS-AP - Hong Kong Communications International Co., Limited, HK AS140227 HKCICL-AS-AP - Hong Kong Communications International Co., Limited, HK AS140227 HKCICL-AS-AP - Hong Kong Communications International Co., Limited, HK154.23.191.128 154.86.21.128 2001:df2:f080:2::1:1
ns2.dns.com154.23.191.129 177.2.31.129 2001:df2:f080:2::1:2AS140227 HKCICL-AS-AP - Hong Kong Communications International Co., Limited, HK AS140227 HKCICL-AS-AP - Hong Kong Communications International Co., Limited, HK AS140227 HKCICL-AS-AP - Hong Kong Communications International Co., Limited, HK154.23.191.129 154.86.21.129 2001:df2:f080:2::1:2

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.dns.com, ns2.dns.com.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: ns1.dns.com (glue 154.23.191.128, 154.86.21.128, 2001:df2:f080:2::1:1, zone 154.86.21.128, 177.2.31.128, 2001:df2:f080:2::1:1); ns2.dns.com (glue 154.23.191.129, 154.86.21.129, 2001:df2:f080:2::1:2, zone 154.23.191.129, 177.2.31.129, 2001:df2:f080:2::1:2). Update the glue at your registrar.
    #8
  • ✓ 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 2001:df2:f080::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS140227 (HKCICL-AS-AP - Hong Kong Communications International Co., Limited, HK): 6 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 .com
    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

3 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.dns.com 154.86.21.128NOERROR, 200 ms, authoritativenoyes / yesrefused-
ns1.dns.com 177.2.31.128NOERROR, 160 ms, authoritativenoyes / yesrefused-
ns1.dns.com 2001:df2:f080:2::1:1no responsenono / no--
ns2.dns.com 154.23.191.129no responsenono / no--
ns2.dns.com 177.2.31.129NOERROR, 162 ms, authoritativenoyes / yesrefused-
ns2.dns.com 2001:df2:f080:2::1:2no responsenono / no--

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns1.dns.com (2001:df2:f080:2::1:1): read udp [2a01:4f8:1c1c:eebf::1]:37469->[2001:df2:f080:2::1:1]:53: i/o timeout; ns2.dns.com (154.23.191.129): read udp 46.225.38.91:35833->154.23.191.129:53: i/o timeout; ns2.dns.com (2001:df2:f080:2::1:2): read udp [2a01:4f8:1c1c:eebf::1]:43123->[2001:df2:f080:2::1:2]: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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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

pass

serial 1790369050 · primary ns1.dns.com

Found

Primary (MNAME)
ns1.dns.com
Contact (RNAME)
admin.dns.com
Serial
1790369050
Refresh / retry
3600 s / 300 s
Expire
1209600 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
ns1.dns.com (154.86.21.128)1790369050
ns1.dns.com (177.2.31.128)1790369050
ns2.dns.com (177.2.31.129)1790369050

Checks

  • ✓ Serial 1790369050 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 5m, expire 14d, negative TTL 30m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.dns.com is one of the listed nameservers.
  • ✓ Contact admin@dns.com #25
    The SOA RNAME admin.dns.com means admin@dns.com.
  • ✓ Timestamp serial #26
    The serial 1790369050 is a Unix timestamp (2026-09-25 20:44 UTC).

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

fail

4 records at the apex

Found

Read from
154.86.21.128:53
TypeValueTTL
SOAns1.dns.com. admin.dns.com. 1790369050 3600 300 1209600 1800600
NSns1.dns.com.86400
NSns2.dns.com.86400
TXT"_globalsign-domain-verification=Pqu9xHv-p7H8z1zTcrJFtrafVHnFAsHkeSnjYLgzeM"600

Checks

  • ✓ TTLs within range #32
    TTLs: NS 1d. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.
  • ✗
    CNAME at the apex
    The zone apex is a CNAME to lanzoui.com.a1.initba.com. A CNAME can't coexist with the SOA and NS records (RFC 1034); use your provider's ALIAS/flattening feature instead.
    #33
  • 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