comlockdown.com - dns.ninja

`comlockdown.com`

DNSSEC	⚠️ Not signed
A	2600:1803:10a::72^{🇺🇸 Tiggee2600:1803:10a::/48 route6 2600:1803:10a::/48}
		PTR	`systems.tiggee.net`
A	2600:1803:10b::8^{🇺🇸 Tiggee2600:1803:10b::/48 route6 2600:1803:10b::/48}
A	2600:1803:10c::8^{🇺🇸 Tiggee2600:1803:10c::/48 route6 2600:1803:10c::/48}
A	2600:1803:10d::40^{🇺🇸 Tiggee2600:1803:10d::/48 route6 2600:1803:10d::/48}
A	208.80.122.53^{🇺🇸 Tiggee208.80.122.0/24 route 208.80.122.0/24}
A	208.80.122.130^{🇺🇸 Tiggee208.80.122.0/24 route 208.80.122.0/24}
A	208.80.123.127^{🇺🇸 Tiggee208.80.123.0/24 route 208.80.123.0/24}
A	208.80.123.195^{🇺🇸 Tiggee208.80.123.0/24 route 208.80.123.0/24}
NS	`a1.verisigndns.com` ⭐
		A	2600:180a:1001::1^{🇺🇸 Tiggee2600:180a:1001::/48 Constellix anycast network}
			PTR	`ns11.constellix.com`
		A	96.45.80.1^{🇺🇸 Tiggee96.45.80.0/24 route 96.45.80.0/24}
			PTR	`ns11.constellix.com`
NS	`a2.verisigndns.com`
		A	2600:180b:2001::1^{🇺🇸 Tiggee2600:180b:2001::/48 Constellix anycast network}
			PTR	`ns21.constellix.com`
		A	46.31.236.1^{🇺🇸 Tiggee46.31.236.0/24 route 46.31.236.0/24}
			PTR	`ns21.constellix.com`
NS	`a3.verisigndns.com`
		A	2600:180c:3001::1^{🇺🇸 Tiggee2600:180c:3001::/48 Constellix anycast network}
			PTR	`ns31.constellix.com`
		A	43.247.170.1^{🇯🇵 Tiggee43.247.170.0/24 route 43.247.170.0/24}
			PTR	`ns31.constellix.com`
SOA	`a1.verisigndns.com`dns@constellix.com 2013-12-15 #16

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1784871802

Same first word

comlockdown.com

DNS History

17 records (11 active, 6 former)

●NSa1.verisigndns.com2026-03-14 → 2026-07-24 · 3 obs

○ 2017-10-03 15:19:04
● 2026-03-14 13:52:42
● 2026-07-24 06:10:50

●NSa2.verisigndns.com2026-03-14 → 2026-07-24 · 3 obs

○ 2017-10-03 15:19:04
● 2026-03-14 13:52:42
● 2026-07-24 06:10:50

●NSa3.verisigndns.com2026-03-14 → 2026-07-24 · 3 obs

○ 2017-10-03 15:19:04
● 2026-03-14 13:52:42
● 2026-07-24 06:10:50

○NSa4.nstld.com2015-07-12 → 2017-10-03 · 4 obs

● 2015-07-12 18:00:24
● 2017-10-03 15:19:04
○ 2026-03-14 13:52:42
○ 2026-07-24 06:10:50

○NSf4.nstld.com2015-07-12 → 2017-10-03 · 4 obs

● 2015-07-12 18:00:24
● 2017-10-03 15:19:04
○ 2026-03-14 13:52:42
○ 2026-07-24 06:10:50

○NSg4.nstld.com2015-07-12 → 2017-10-03 · 4 obs

● 2015-07-12 18:00:24
● 2017-10-03 15:19:04
○ 2026-03-14 13:52:42
○ 2026-07-24 06:10:50

○NSl4.nstld.com2015-07-12 → 2017-10-03 · 4 obs

● 2015-07-12 18:00:24
● 2017-10-03 15:19:04
○ 2026-03-14 13:52:42
○ 2026-07-24 06:10:50

○A165.160.13.202015-07-12 → 2017-10-03 · 4 obs

● 2015-07-12 18:00:24
● 2017-10-03 15:19:04
○ 2026-03-14 13:52:42
○ 2026-07-24 06:10:50

○A165.160.15.202015-07-12 → 2017-10-03 · 4 obs

● 2015-07-12 18:00:24
● 2017-10-03 15:19:04
○ 2026-03-14 13:52:42
○ 2026-07-24 06:10:50

●A208.80.122.1302026-03-14 → 2026-07-24 · 3 obs

○ 2017-10-03 15:19:04
● 2026-03-14 13:52:42
● 2026-07-24 06:10:50

●A208.80.122.532026-03-14 → 2026-07-24 · 3 obs

○ 2017-10-03 15:19:04
● 2026-03-14 13:52:42
● 2026-07-24 06:10:50

●A208.80.123.1272026-03-14 → 2026-07-24 · 3 obs

○ 2017-10-03 15:19:04
● 2026-03-14 13:52:42
● 2026-07-24 06:10:50

●A208.80.123.1952026-03-14 → 2026-07-24 · 3 obs

○ 2017-10-03 15:19:04
● 2026-03-14 13:52:42
● 2026-07-24 06:10:50

●A2600:1803:10a::722026-03-14 → 2026-07-24 · 3 obs

○ 2017-10-03 15:19:04
● 2026-03-14 13:52:42
● 2026-07-24 06:10:50

●A2600:1803:10b::82026-03-14 → 2026-07-24 · 3 obs

○ 2017-10-03 15:19:04
● 2026-03-14 13:52:42
● 2026-07-24 06:10:50

●A2600:1803:10c::82026-03-14 → 2026-07-24 · 3 obs

○ 2017-10-03 15:19:04
● 2026-03-14 13:52:42
● 2026-07-24 06:10:50

●A2600:1803:10d::402026-03-14 → 2026-07-24 · 3 obs

○ 2017-10-03 15:19:04
● 2026-03-14 13:52:42
● 2026-07-24 06:10:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	j.gtld-servers.net, g.gtld-servers.net, a.gtld-servers.net, e.gtld-servers.net...	-
comlockdown.com	a1.verisigndns.com, a2.verisigndns.com, a3.verisigndns.com	6 records

✅ Authoritative Response

Server:96.45.80.1

NS records: a1.verisigndns.com, a2.verisigndns.com, a3.verisigndns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for comlockdown.com (unsigned zone)

⏱️ Timing

Total: 195ms | Queries: -

📄 Records

Type	Count	Sample Data
A	4	`208.80.123.195, 208.80.122.53...`
AAAA	4	`2600:1803:10c::8, 2600:1803:10d::40...`
NS	3	`a1.verisigndns.com, a2.verisigndns.com...`
SOA	1	`a1.verisigndns.com dns.constellix.com`

📌 Glue Records Collected

Total: 6

Out-of-bailiwick: 6 (a1.verisigndns.com, a1.verisigndns.com, a2.verisigndns.com...)

Analysis

IP Addresses

comlockdown.com resolves to 8 IP numbers: 208.80.122.53, 208.80.122.130, 208.80.123.127 and 5 other.

Additional host names — verisign.co.uz, mcenvironmental.com, verisignseal.co.in and two others — share IP numbers with comlockdown.com.

Name Servers

comlockdown.com is served by three name servers: a1.verisigndns.com, a2.verisigndns.com and a3.verisigndns.com.

There is at least partial name server overlap between comlockdown.com and other domains — franklinbnk.com, skybettingandgaming.tv, verisigninc.nl and two more among them.

These name servers are frequently paired with the name servers edns123.ultradns.biz, edns123.ultradns.com, edns123.ultradns.net and two others.

The hostnames a1.verisigndns.com, a2.verisigndns.com and a3.verisigndns.com each direct to two IP addresses — a1.verisigndns.com to 96.45.80.1 and 2600:180a:1001::1, a2.verisigndns.com to 46.31.236.1 and 2600:180b:2001::1, and a3.verisigndns.com to 43.247.170.1 and 2600:180c:3001::1.