legendsofamerica.com

Checked 22 October 2026, 09:34 UTC · via 8.8.8.8
!Passed with warnings
21 passed 5 warnings 0 failed 5 info

Registration

info

.com generic · eNom, LLC · expires 2031-06-27

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
eNom, LLC
Registered
27 June 2003
Last changed
27 May 2026
Expires
27 June 2031
Status
client transfer prohibited
Registry nameservers
ns1.legendsofamerica.com, ns2.legendsofamerica.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 2031-06-27 #3
    The registration is valid until 2031-06-27 (1709 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

warn

ns1.legendsofamerica.com, ns2.legendsofamerica.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.legendsofamerica.com, ns2.legendsofamerica.com
NS in the zone
ns1.legendsofamerica.com, ns2.legendsofamerica.com
NameserverAddressesNetwork (AS)Glue
ns1.legendsofamerica.com172.233.221.139AS63949 AKAMAI-LINODE-AP - Akamai Connected Cloud, SG172.233.221.139
ns2.legendsofamerica.com172.233.221.139AS63949 AKAMAI-LINODE-AP - Akamai Connected Cloud, SG172.233.221.139

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.legendsofamerica.com, ns2.legendsofamerica.com.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns1.legendsofamerica.com, ns2.legendsofamerica.com.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • !
    Nameservers in one network
    all IPv4 addresses are in 172.233.221.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS63949 (AKAMAI-LINODE-AP - Akamai Connected Cloud, SG): 2 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.legendsofamerica.com 172.233.221.139NOERROR, 116 ms, authoritativenoyes / yesrefused9.11.36-RedHat-9.11.36-16.el8_10.14
ns2.legendsofamerica.com 172.233.221.139NOERROR, 109 ms, authoritativenoyes / yesrefused9.11.36-RedHat-9.11.36-16.el8_10.14

Checks

  • ✓ All respond #14
    All 2 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.legendsofamerica.com: "9.11.36-RedHat-9.11.36-16.el8_10.14"; ns2.legendsofamerica.com: "9.11.36-RedHat-9.11.36-16.el8_10.14". 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

warn

serial 2026092505 · primary ns1.legendsofamerica.com

Found

Primary (MNAME)
ns1.legendsofamerica.com
Contact (RNAME)
root.server.legendsofamerica.com
Serial
2026092505
Refresh / retry
3600 s / 3600 s
Expire
1209600 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
ns1.legendsofamerica.com (172.233.221.139)2026092505
ns2.legendsofamerica.com (172.233.221.139)2026092505

Checks

  • ✓ Serial 2026092505 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 14d, negative TTL 30m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.legendsofamerica.com is one of the listed nameservers.
  • ✓ Contact root@server.legendsofamerica.com #25
    The SOA RNAME root.server.legendsofamerica.com means root@server.legendsofamerica.com.
  • ✓ Date-based serial #26
    The serial 2026092505 follows the YYYYMMDDnn convention (2026-09-25).

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

7 records at the apex

Found

Read from
172.233.221.139:53
TypeValueTTL
SOAns1.legendsofamerica.com. root.server.legendsofamerica.com. 2026092505 3600 3600 1209600 18003600
NSns2.legendsofamerica.com.3600
NSns1.legendsofamerica.com.3600
A172.233.221.1393600
MX0 mail.legendsofamerica.com.86400
TXT"google-site-verification=en5RD0XDhDdU6O4y2S2r4mjz4cKSZnfh0ehi0WeQYJE"3600
TXT"v=spf1 a mx ip4:172.233.221.139 ip6:2600:3c06:0:0:f03c:93ff:fe8a:eac5 include:_spf.getresponse.com -all"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 1d, 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