`tacticalsecurityoperations.com`

DNSSEC	⚠️ Not signed
A	35.172.94.1^{🇺🇸 Amazon35.168.0.0/13 EC2 IAD prefix}
		PTR	`staticip.multiscreensite.com`
A	100.24.208.97^{🇺🇸 Amazon100.24.0.0/13 EC2 IAD prefix}
NS	`ns1.systemdns.com` ⭐
		A	2604:4000:0:d:216:40:47:90^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`ns1.systemdns.com`
		A	216.40.47.90^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`ns1.systemdns.com`
NS	`ns2.systemdns.com`
		A	2604:4000:2800:d:64:99:148:16^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`ns2.systemdns.com`
		A	64.98.148.16^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`ns2.systemdns.com`
NS	`ns3.systemdns.com`
		A	2604:4000:0:d:64:99:96:36^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`ns3.systemdns.com`
		A	64.99.96.36^{🇨🇦 TUCOWS64.99.96.0/24 -BRA-BLK2.7.2}
			PTR	`ns3.systemdns.com`
SOA	`ns1.systemdns.com`hostmaster@systemdns.com serial=1731702133

`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=1774515122

Same first word

tacticalsecurityoperations.com

DNS History

5 records (5 active, 0 former)

●NSns1.systemdns.com2026-02-28 → 2026-03-26 · 2 obs

● 2026-02-28 19:30:28
● 2026-03-26 08:59:22

●NSns2.systemdns.com2026-02-28 → 2026-03-26 · 2 obs

● 2026-02-28 19:30:28
● 2026-03-26 08:59:22

●NSns3.systemdns.com2026-02-28 → 2026-03-26 · 2 obs

● 2026-02-28 19:30:28
● 2026-03-26 08:59:22

●A100.24.208.972026-02-28 → 2026-03-26 · 2 obs

● 2026-02-28 19:30:28
● 2026-03-26 08:59:22

●A35.172.94.12026-02-28 → 2026-03-26 · 2 obs

● 2026-02-28 19:30:28
● 2026-03-26 08:59:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
tacticalsecurityoperations.com	ns1.systemdns.com, ns2.systemdns.com, ns3.systemdns.com	6 records

✅ Authoritative Response

Server:64.99.96.36

NS records: ns1.systemdns.com, ns2.systemdns.com, ns3.systemdns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for tacticalsecurityoperations.com (unsigned zone)

⏱️ Timing

Total: 223ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`35.172.94.1, 100.24.208.97`
NS	3	`ns1.systemdns.com, ns2.systemdns.com...`
SOA	1	`ns1.systemdns.com hostmaster.systemdns.c`

📌 Glue Records Collected

Total: 6

Out-of-bailiwick: 6 (ns1.systemdns.com, ns1.systemdns.com, ns2.systemdns.com...)

Analysis

IP Addresses

tacticalsecurityoperations.com points to two IP numbers: 35.172.94.1 and 100.24.208.97.

Other host names, for instance asaplocksmithsservices.com, hoyerbroswell.com, achupeta.pt, laffertylawoffice.com and lin-air.com share IP numbers with tacticalsecurityoperations.com.

Name Servers

The domain tacticalsecurityoperations.com is delegated to three name servers: ns1.systemdns.com, ns2.systemdns.com and ns3.systemdns.com.

tacticalsecurityoperations.com shares name servers with other domains at least partially, for instance obsdepot.com, ucmagency.org, maximevoidy.com, myebc.ca and thaifest.net.

Host names with two IP numbers:

ns1.systemdns.com points to 2604:4000:0:d:216:40:47:90 and 216.40.47.90

ns2.systemdns.com points to 2604:4000:2800:d:64:99:148:16 and 64.98.148.16

ns3.systemdns.com points to 2604:4000:0:d:64:99:96:36 and 64.99.96.36

tacticalsecurityoperations.com - robtex.com