`defensesector.us`

DNSSEC	⚠️ Not signed
NS	`ns1-08.azuregov-dns.us` ⚠️ Not in zone NS records
		A	2001:489a:4000::8^{🇺🇸 AS80702001:489a:4000::/35 Microsoft V6}
			PTR	`ns1-08.azuregov-dns.us`
		A	195.134.224.8^{🇫🇮 AS8070195.134.224.0/19 Microsoft Federal}
			PTR	`ns1-08.azuregov-dns.us`
NS	`ns2-08.azuregov-dns.us` ⚠️ Not in zone NS records
		A	2001:489a:4002::8^{🇺🇸 AS80702001:489a:4000::/35 Microsoft V6}
			PTR	`ns2-08.azuregov-dns.us`
		A	195.134.226.8^{🇫🇮 AS8070195.134.224.0/19 Microsoft Federal}
			PTR	`ns2-08.azuregov-dns.us`
NS	`ns3-08.azuregov-dns.us` ⚠️ Not in zone NS records
		A	2001:489a:4004::8^{🇺🇸 AS80702001:489a:4000::/35 Microsoft V6}
			PTR	`ns3-08.azuregov-dns.us`
		A	204.13.120.8^{🇺🇸 AS8070204.13.120.0/21 Microsoft}
			PTR	`ns3-08.azuregov-dns.us`
NS	`ns4-08.azuregov-dns.us` ⚠️ Not in zone NS records
		A	2001:489a:4006::8^{🇺🇸 AS80702001:489a:4000::/35 Microsoft V6}
			PTR	`ns4-08.azuregov-dns.use`
		A	204.13.122.8^{🇺🇸 AS8070204.13.120.0/21 Microsoft}
			PTR	`ns4-08.azuregov-dns.us`

`us`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.cctld.us` ⭐
	NS	`b.cctld.us`
	NS	`f.cctld.us`
	NS	`k.cctld.us`
	NS	`m.cctld.us`
	NS	`n.cctld.us`
	NS	`w.cctld.us`
	NS	`x.cctld.us`
	NS	`y.cctld.us`
	SOA	`a.cctld.us`admin@tldns.godaddy serial=1776053301

Same first word

defensesector.us

DNS History

4 records (4 active, 0 former)

●NSns1-08.azuregov-dns.us2026-02-28 → 2026-04-13 · 2 obs

● 2026-02-28 11:29:22
● 2026-04-13 04:21:50

●NSns2-08.azuregov-dns.us2026-02-28 → 2026-04-13 · 2 obs

● 2026-02-28 11:29:22
● 2026-04-13 04:21:50

●NSns3-08.azuregov-dns.us2026-02-28 → 2026-04-13 · 2 obs

● 2026-02-28 11:29:22
● 2026-04-13 04:21:50

●NSns4-08.azuregov-dns.us2026-02-28 → 2026-04-13 · 2 obs

● 2026-02-28 11:29:22
● 2026-04-13 04:21:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
us	m.cctld.us, k.cctld.us, b.cctld.us, x.cctld.us...	-
defensesector.us	ns2-08.azuregov-dns.us, ns4-08.azuregov-dns.us, ns1-08.azuregov-dns.us, ns3-08.azuregov-dns.us	-

✅ Authoritative Response

Server:204.13.120.8

NS records: ns2-08.azuregov-dns.us, ns4-08.azuregov-dns.us, ns1-08.azuregov-dns.us, ns3-08.azuregov-dns.us

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for defensesector.us (unsigned zone)

⏱️ Timing

Total: 923ms | Queries: -

📄 Records

Type	Count	Sample Data

Analysis

Name Servers

defensesector.us is delegated to four name servers: ns1-08.azuregov-dns.us, ns2-08.azuregov-dns.us, ns3-08.azuregov-dns.us and ns4-08.azuregov-dns.us.

defensesector.us at least partially shares name servers with other domains, for instance avinc.com, radhsv.com, m1.usgovvirginia.azure-gov-dev.app.snowflake.com, quartzsonata.cloud and seniorplcusa.com.

Host names with two IP numbers:

Host name ns1-08.azuregov-dns.us points to: 2001:489a:4000::8 and 195.134.224.8.

Host name ns2-08.azuregov-dns.us points to: 2001:489a:4002::8 and 195.134.226.8.

Host name ns3-08.azuregov-dns.us points to: 2001:489a:4004::8 and 204.13.120.8.

Host name ns4-08.azuregov-dns.us points to: 2001:489a:4006::8 and 204.13.122.8.

defensesector.us - robtex.com