lisez.com

Checked 22 October 2026, 09:40 UTC · via 8.8.8.8
!Passed with warnings
23 passed 2 warnings 0 failed 6 info

Registration

info

.com generic · Namebay SAM · expires 2027-10-21

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Namebay SAM
Registered
21 October 2003
Last changed
5 October 2026
Expires
21 October 2027
Status
client transfer prohibited
Registry nameservers
dns1.namebay.com, dns2.namebay.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-10-21 #3
    The registration is valid until 2027-10-21 (364 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

dns1.namebay.com, dns2.namebay.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
dns1.namebay.com, dns2.namebay.com
NS in the zone
dns1.namebay.com, dns2.namebay.com
NameserverAddressesNetwork (AS)Glue
dns1.namebay.com62.141.38.216 185.65.56.133 2a01:c8:ff00:201::133 2001:4ba0:cafe:532::1AS24961 MYLOC-AS - WIIT AG, DE AS20756 NAMESHIELD - NAMESHIELD SAS, FR AS20756 NAMESHIELD - NAMESHIELD SAS, FR AS24961 MYLOC-AS - WIIT AG, DE185.65.56.133 2001:4ba0:cafe:532::1 2a01:c8:ff00:201::133 62.141.38.216
dns2.namebay.com91.134.185.34 185.65.56.134 2a01:c8:ff00:201::134 2001:41d0:203:ddee::34AS16276 OVH - OVH SAS, FR AS20756 NAMESHIELD - NAMESHIELD SAS, FR AS20756 NAMESHIELD - NAMESHIELD SAS, FR AS16276 OVH - OVH SAS, FR185.65.56.134 2001:41d0:203:ddee::34 2a01:c8:ff00:201::134 91.134.185.34

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns1.namebay.com, dns2.namebay.com.
    #6
  • ✓ 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.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 3 IPv4 /24s and 3 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS16276 (OVH - OVH SAS, FR): 2 addresses; AS20756 (NAMESHIELD - NAMESHIELD SAS, FR): 4 addresses; AS24961 (MYLOC-AS - WIIT AG, DE): 2 addresses.
  • 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

info

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.namebay.com 62.141.38.216NOERROR, 9 ms, authoritativenoyes / yesrefusednot currently available
dns1.namebay.com 185.65.56.133NOERROR, 15 ms, authoritativenoyes / yesrefusednot currently available
dns1.namebay.com 2a01:c8:ff00:201::133NOERROR, 15 ms, authoritativenoyes / yesrefusednot currently available
dns1.namebay.com 2001:4ba0:cafe:532::1NOERROR, 9 ms, authoritativenoyes / yesrefusednot currently available
dns2.namebay.com 91.134.185.34NOERROR, 16 ms, authoritativenoyes / yesrefusednot currently available
dns2.namebay.com 185.65.56.134NOERROR, 14 ms, authoritativenoyes / yesrefusednot currently available
dns2.namebay.com 2a01:c8:ff00:201::134NOERROR, 15 ms, authoritativenoyes / yesrefusednot currently available
dns2.namebay.com 2001:41d0:203:ddee::34NOERROR, 15 ms, authoritativenoyes / yesrefusednot currently available

Checks

  • ✓ All respond #14
    All 8 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: dns1.namebay.com: "not currently available"; dns2.namebay.com: "not currently available".
    #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

pass

serial 2025122216 · primary dns1.namebay.com

Found

Primary (MNAME)
dns1.namebay.com
Contact (RNAME)
admin.validname.com
Serial
2025122216
Refresh / retry
10800 s / 600 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
dns1.namebay.com (62.141.38.216)2025122216
dns1.namebay.com (185.65.56.133)2025122216
dns1.namebay.com (2a01:c8:ff00:201::133)2025122216
dns1.namebay.com (2001:4ba0:cafe:532::1)2025122216
dns2.namebay.com (91.134.185.34)2025122216
dns2.namebay.com (185.65.56.134)2025122216
dns2.namebay.com (2a01:c8:ff00:201::134)2025122216
dns2.namebay.com (2001:41d0:203:ddee::34)2025122216

Checks

  • ✓ Serial 2025122216 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 10m, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns1.namebay.com is one of the listed nameservers.
  • ✓ Contact admin@validname.com #25
    The SOA RNAME admin.validname.com means admin@validname.com.
  • ✓ Date-based serial #26
    The serial 2025122216 follows the YYYYMMDDnn convention (2025-12-22).

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

warn

14 records at the apex

Found

Read from
62.141.38.216:53
TypeValueTTL
SOAdns1.namebay.com. admin.validname.com. 2025122216 10800 600 1209600 360090
NSdns2.namebay.com.90
NSdns1.namebay.com.90
A3.162.38.12990
A3.162.38.7990
A3.162.38.3290
A3.162.38.4790
MX0 lisez-com.mail.protection.outlook.com.90
TXT"MS=ms71847667"90
TXT"O/Zvg7Y1Gz0gjMz92O9P29tDFAFvUDd8WqnQDpnJadF3i41b5FRbtED2n58gu8VvA0aniOyZshkBCdTE8UTi8g=="90
TXT"google-site-verification=hpeYux1EK5rrruYed00AzwSxRR-JKODpxbcVCG9uUH0"90
TXT"I0N4T38422"90
TXT"v=spf1 include:spf.protection.outlook.com include:spf.editis.com ip4:89.185.35.116/32 ip4:89.185.35.189/32 -all"90
TXT"lrw501hhx7r0m2c9hy0g6zgsh9czykjl"90

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m30s), MX (1m30s), NS (1m30s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1m30s; resolvers may use either.
    #32
  • ✓ 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