legoland.com

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

Registration

info

.com generic · CSC Corporate Domains, Inc. · expires 2027-08-03

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
CSC Corporate Domains, Inc.
Registered
4 August 1998
Last changed
30 July 2026
Expires
3 August 2027
Status
client transfer prohibited
Registry nameservers
ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info
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-08-03 #3
    The registration is valid until 2027-08-03 (284 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

ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info
NS in the zone
ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info
NameserverAddressesNetwork (AS)Glue
ns1-05.azure-dns.com13.107.236.5 2603:1061:0:700::5AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US13.107.236.5 2603:1061:0:700::5
ns2-05.azure-dns.net150.171.21.5 2620:1ec:8ec:700::5AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns3-05.azure-dns.org204.14.183.5 2a01:111:4000:700::5AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns4-05.azure-dns.info208.84.5.5 2620:1ec:bda:700::5AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info.
  • ✓ 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 4 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 8 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 4 TLDs #12
    Nameserver names use the TLDs .com, .info, .net, .org.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1-05.azure-dns.com 13.107.236.5NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1-05.azure-dns.com 2603:1061:0:700::5NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-05.azure-dns.net 150.171.21.5NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-05.azure-dns.net 2620:1ec:8ec:700::5NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns3-05.azure-dns.org 204.14.183.5NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-05.azure-dns.org 2a01:111:4000:700::5NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns4-05.azure-dns.info 208.84.5.5NOERROR, 4 ms, authoritativenoyes / yesrefusedKnot DNS 3.1.2.1770717641.d6b376aff
ns4-05.azure-dns.info 2620:1ec:bda:700::5NOERROR, 4 ms, authoritativenoyes / yesrefused-

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns4-05.azure-dns.info: "Knot DNS 3.1.2.1770717641.d6b376aff". 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 1 · primary ns1-05.azure-dns.com

Found

Primary (MNAME)
ns1-05.azure-dns.com
Contact (RNAME)
azuredns-hostmaster.microsoft.com
Serial
1
Refresh / retry
3600 s / 300 s
Expire
2419200 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1-05.azure-dns.com (13.107.236.5)1
ns1-05.azure-dns.com (2603:1061:0:700::5)1
ns2-05.azure-dns.net (150.171.21.5)1
ns2-05.azure-dns.net (2620:1ec:8ec:700::5)1
ns3-05.azure-dns.org (204.14.183.5)1
ns3-05.azure-dns.org (2a01:111:4000:700::5)1
ns4-05.azure-dns.info (208.84.5.5)1
ns4-05.azure-dns.info (2620:1ec:bda:700::5)1

Checks

  • ✓ Serial 1 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 5m, expire 28d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1-05.azure-dns.com is one of the listed nameservers.
  • ✓ Contact azuredns-hostmaster@microsoft.com #25
    The SOA RNAME azuredns-hostmaster.microsoft.com means azuredns-hostmaster@microsoft.com.
  • ✓ Counter serial #26
    The serial 1 is a plain counter.

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

32 records at the apex

Found

Read from
13.107.236.5:53
TypeValueTTL
SOAns1-05.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 3003600
NSns1-05.azure-dns.com.172800
NSns2-05.azure-dns.net.172800
NSns3-05.azure-dns.org.172800
NSns4-05.azure-dns.info.172800
A150.171.109.10160
MX10 legoland-com.mail.protection.outlook.com.86400
TXT"amazonses:JkqQyhfzK/4kvcdREVkTRVY4NmyD5YDcLWVQUrlSRQ4="600
TXT"onetrust-domain-verification=0b893a9057f84569bbdd03aef805dc95"600
TXT"JoKrGMSj5Z5EklV6uyEG87ii/Ad+qEYOTsqIXLviAnckUbOzvxiJwGTEG1X3bQNc3h89+ZrT+zwu8Y4TyNZhvA=="600
TXT"iaHRJcLkGzSIIfGfhoImCbLh9bemUYlnCLE/F0c1Db8="600
TXT"MS=ms37823095"600
TXT"v=spf1 include:_spf.legoland_com._d.easydmarc.pro ~all"600
TXT"google-site-verification=Wlekg1woWZeCntnghVWbF21haCHQPhjqrgkMbVBzUq4"600
TXT"54NabhfHZVkceM4BxpVatVQti2KaqH03hSnzkT+S24Y="600
TXT"smartsheet-site-validation=YkX2FMmVXWnMO3mw0rG7OHCJPOl6-682"600
TXT"df97114f52204b539a3cb23f22499ad7"600
TXT"atlassian-domain-verification=Ha5FCASvmo9J/oQ9k1CGd46zCsRnofH5M3UCR/vw48kQEiMVkadD/n/UsQbN3usZ"600
TXT"google-site-verification=vj8JU3c72k1n4cqPbNMsLw20ekP89Gw93qiUDiaoJuM"600
TXT"adobe-idp-site-verification=a2cae57293211ec2e5ea618a061c780316b1e956371bbe4b832a5df87ba9e71d"600
TXT"zscaler-verification-165568482-10182025-atZ8Ot"600
TXT"docusign=5c3c83ad-0ef5-4c47-a940-02aa39209381"600
TXT"ibmid=be093d40-9181-4c8e-b23b-2d0ee92f5836"600
CAA0 issue "sectigo.com"300
CAA0 issue "digicert.com"300
CAA0 iodef "mailto:ssl@lego.com"300
CAA0 issue "globalsign.com"300
CAA0 issue "letsencrypt.org"300
CAA0 issue "amazon.com"300
CAA0 issue "amazontrust.com"300
CAA0 issue "awstrust.com"300
CAA0 issue "amazonaws.com"300

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change.
    #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
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: sectigo.com, digicert.com, globalsign.com, letsencrypt.org, amazon.com, amazontrust.com, awstrust.com, amazonaws.com.