`lockonetheatre.com`

DNSSEC	⚠️ Not signed
NS	`ns1-35.azure-dns.com` ⭐
		A	2603:1061:0:10::23^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-35.azure-dns.com`
		A	150.171.10.35^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns1-35.azure-dns.com`
NS	`ns2-35.azure-dns.net`
		A	2620:1ec:8ec:10::23^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-35.azure-dns.net`
		A	150.171.16.35^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-35.azure-dns.net`
NS	`ns3-35.azure-dns.org`
		A	2a01:111:4000:10::23^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-35.azure-dns.org`
		A	13.107.222.35^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns3-35.azure-dns.org`
NS	`ns4-35.azure-dns.info`
		A	2620:1ec:bda:10::23^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-35.azure-dns.info`
		A	13.107.206.35^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns4-35.azure-dns.info`
TXT	`v=spf1 -all`
SOA	`ns1-35.azure-dns.com`azuredns-hostmaster@microsoft.com serial=1

`com`

	DNSSEC	⚠️ Not signed
	NS	`dns1.qti.com` ⚠️ Not in zone NS records

Same first word

lockonetheatre.com

DNS History

10 records (4 active, 6 former)

○NScorp337f.crown.com2015-06-26 → 2017-04-10 · 5 obs

○ 2008-03-19 21:28:20
● 2015-06-26 07:29:34
● 2017-04-10 04:28:10
○ 2026-03-06 16:25:40
○ 2026-04-04 23:24:24

○NSnames.crown.com2015-06-26 → 2017-04-10 · 5 obs

○ 2008-03-19 21:28:20
● 2015-06-26 07:29:34
● 2017-04-10 04:28:10
○ 2026-03-06 16:25:40
○ 2026-04-04 23:24:24

○NSnames2.crown.com2015-06-26 → 2017-04-10 · 5 obs

○ 2008-03-19 21:28:20
● 2015-06-26 07:29:34
● 2017-04-10 04:28:10
○ 2026-03-06 16:25:40
○ 2026-04-04 23:24:24

○NSnames3.crown.com2015-06-26 → 2017-04-10 · 5 obs

○ 2008-03-19 21:28:20
● 2015-06-26 07:29:34
● 2017-04-10 04:28:10
○ 2026-03-06 16:25:40
○ 2026-04-04 23:24:24

●NSns1-35.azure-dns.com2026-03-06 → 2026-04-04 · 3 obs

○ 2017-04-10 04:28:10
● 2026-03-06 16:25:40
● 2026-04-04 23:24:24

●NSns2-35.azure-dns.net2026-03-06 → 2026-04-04 · 3 obs

○ 2017-04-10 04:28:10
● 2026-03-06 16:25:40
● 2026-04-04 23:24:24

●NSns3-35.azure-dns.org2026-03-06 → 2026-04-04 · 3 obs

○ 2017-04-10 04:28:10
● 2026-03-06 16:25:40
● 2026-04-04 23:24:24

●NSns4-35.azure-dns.info2026-03-06 → 2026-04-04 · 3 obs

○ 2017-04-10 04:28:10
● 2026-03-06 16:25:40
● 2026-04-04 23:24:24

○A192.69.21.682015-06-26 → 2017-04-10 · 5 obs

○ 2008-03-19 21:28:20
● 2015-06-26 07:29:34
● 2017-04-10 04:28:10
○ 2026-03-06 16:25:40
○ 2026-04-04 23:24:24

○CNAMEwww.lockonetheater.com2008-03-19 → 2008-03-19 · 3 obs

● 2008-03-19 21:28:20
○ 2015-06-26 07:29:34
○ 2026-04-04 23:24:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
lockonetheatre.com	ns1-35.azure-dns.com, ns2-35.azure-dns.net, ns3-35.azure-dns.org, ns4-35.azure-dns.info	2 records

✅ Authoritative Response

Server:13.107.206.35

NS records: ns1-35.azure-dns.com, ns2-35.azure-dns.net, ns3-35.azure-dns.org, ns4-35.azure-dns.info

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for lockonetheatre.com (unsigned zone)

⏱️ Timing

Total: 283ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-35.azure-dns.com, ns2-35.azure-dns.net...`
TXT	1	`v=spf1 -all`
SOA	1	`ns1-35.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1-35.azure-dns.com, ns1-35.azure-dns.com)

Analysis

Name Servers

lockonetheatre.com is delegated to four name servers: ns1-35.azure-dns.com, ns4-35.azure-dns.info, ns2-35.azure-dns.net and ns3-35.azure-dns.org.

lockonetheatre.com at least partially shares name servers with other domains such as claudeict.pl, mobe3app.com, npaschoalotto.com.br, pikosblocks.com and zenaan-com.mail.protection.outlook.com.

Host names with two IP numbers:

ns1-35.azure-dns.com points to 2603:1061:0:10::23 and 150.171.10.35

ns4-35.azure-dns.info points to 2620:1ec:bda:10::23 and 13.107.206.35

ns2-35.azure-dns.net points to 2620:1ec:8ec:10::23 and 150.171.16.35

ns3-35.azure-dns.org points to 2a01:111:4000:10::23 and 13.107.222.35

lockonetheatre.com - robtex.com