listal.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 · GoDaddy.com, LLC · expires 2027-03-14

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
GoDaddy.com, LLC
Registered
14 March 2004
Last changed
4 July 2025
Expires
14 March 2027
Status
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Registry nameservers
alaric.ns.cloudflare.com, destiny.ns.cloudflare.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-14 #3
    The registration is valid until 2027-03-14 (142 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

alaric.ns.cloudflare.com, destiny.ns.cloudflare.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
alaric.ns.cloudflare.com, destiny.ns.cloudflare.com
NS in the zone
alaric.ns.cloudflare.com, destiny.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
alaric.ns.cloudflare.com172.64.35.31 108.162.195.31 162.159.44.31 2a06:98c1:50::ac40:231f 2803:f800:50::6ca2:c31f 2606:4700:58::a29f:2c1fAS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US108.162.195.31 162.159.44.31 172.64.35.31 2606:4700:58::a29f:2c1f 2803:f800:50::6ca2:c31f 2a06:98c1:50::ac40:231f
destiny.ns.cloudflare.com162.159.38.76 108.162.194.76 172.64.34.76 2a06:98c1:50::ac40:224c 2803:f800:50::6ca2:c24c 2606:4700:50::a29f:264cAS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US108.162.194.76 162.159.38.76 172.64.34.76 2606:4700:50::a29f:264c 2803:f800:50::6ca2:c24c 2a06:98c1:50::ac40:224c

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: alaric.ns.cloudflare.com, destiny.ns.cloudflare.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 6 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 12 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

warn

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
alaric.ns.cloudflare.com 172.64.35.31NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
alaric.ns.cloudflare.com 108.162.195.31NOERROR, 19 ms, authoritativenoyes / yesrefused2026.10.2
alaric.ns.cloudflare.com 162.159.44.31NOERROR, 32 ms, authoritativenoyes / yesrefused2026.10.2
alaric.ns.cloudflare.com 2a06:98c1:50::ac40:231fNOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
alaric.ns.cloudflare.com 2803:f800:50::6ca2:c31fNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
alaric.ns.cloudflare.com 2606:4700:58::a29f:2c1fNOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
destiny.ns.cloudflare.com 162.159.38.76NOERROR, 32 ms, authoritativenoyes / yesrefused2026.10.2
destiny.ns.cloudflare.com 108.162.194.76NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
destiny.ns.cloudflare.com 172.64.34.76NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
destiny.ns.cloudflare.com 2a06:98c1:50::ac40:224cNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
destiny.ns.cloudflare.com 2803:f800:50::6ca2:c24cNOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
destiny.ns.cloudflare.com 2606:4700:50::a29f:264cNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2

Checks

  • ✓ All respond #14
    All 12 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: alaric.ns.cloudflare.com: "2026.10.2"; destiny.ns.cloudflare.com: "2026.10.2". Hide or replace the version string.
    #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 2418002727 · primary alaric.ns.cloudflare.com

Found

Primary (MNAME)
alaric.ns.cloudflare.com
Contact (RNAME)
dns.cloudflare.com
Serial
2418002727
Refresh / retry
10000 s / 2400 s
Expire
604800 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
alaric.ns.cloudflare.com (172.64.35.31)2418002727
alaric.ns.cloudflare.com (108.162.195.31)2418002727
alaric.ns.cloudflare.com (162.159.44.31)2418002727
alaric.ns.cloudflare.com (2a06:98c1:50::ac40:231f)2418002727
alaric.ns.cloudflare.com (2803:f800:50::6ca2:c31f)2418002727
alaric.ns.cloudflare.com (2606:4700:58::a29f:2c1f)2418002727
destiny.ns.cloudflare.com (162.159.38.76)2418002727
destiny.ns.cloudflare.com (108.162.194.76)2418002727
destiny.ns.cloudflare.com (172.64.34.76)2418002727
destiny.ns.cloudflare.com (2a06:98c1:50::ac40:224c)2418002727
destiny.ns.cloudflare.com (2803:f800:50::6ca2:c24c)2418002727
destiny.ns.cloudflare.com (2606:4700:50::a29f:264c)2418002727

Checks

  • ✓ Serial 2418002727 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h46m40s, retry 40m, expire 7d, negative TTL 30m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver alaric.ns.cloudflare.com is one of the listed nameservers.
  • ✓ Contact dns@cloudflare.com #25
    The SOA RNAME dns.cloudflare.com means dns@cloudflare.com.
  • ✓ Timestamp serial #26
    The serial 2418002727 is a Unix timestamp (2046-08-16 03:25 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

info

21 records at the apex

Found

Read from
172.64.35.31:53
TypeValueTTL
SOAalaric.ns.cloudflare.com. dns.cloudflare.com. 2418002727 10000 2400 604800 18001800
NSalaric.ns.cloudflare.com.86400
NSdestiny.ns.cloudflare.com.86400
A104.26.11.2300
A104.26.10.2300
A172.67.70.180300
AAAA2606:4700:20::ac43:46b4300
AAAA2606:4700:20::681a:b02300
AAAA2606:4700:20::681a:a02300
MX1 aspmx.l.google.com.300
MX10 aspmx2.googlemail.com.300
MX10 aspmx3.googlemail.com.300
MX10 aspmx4.googlemail.com.300
MX10 aspmx5.googlemail.com.300
MX5 alt1.aspmx.l.google.com.300
MX5 alt2.aspmx.l.google.com.300
TXT"_globalsign-domain-verification=0MASABCMT7yVCL_BjNdYaOH7wWJgsbs1vyYxvMFqWG"300
TXT"_globalsign-domain-verification=4129LfbXrgUKu-uqUnsnknqifRcc0Z9glVuKfpfvOb"300
TXT"google-site-verification=oKlRTMuYmXd6Qc1AD3pKVLlXrp3OhGi1mkmyRqSFS70"300
TXT"protonmail-verification=08988de27ae0e317bc22d60d0fcdd5d52432ab64"300
TXT"v=spf1 include:sendgrid.net include:authsmtp.com include:googlemail.com include:_spf.google.com include:aspmx.googlemail.com include:google.com ip4:104.156.51.246 ~all"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, AAAA 5m, MX 5m, NS 1d. The NS TTL at the parent is 2d and in the zone 1d; 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