`vigilantinternet.com`

DNSSEC	⚠️ Not signed
A	3.33.251.168^{🇺🇸 Amazon3.33.240.0/20}
		PTR	`aec037177372cc6cd.awsglobalaccelerator.com`
A	15.197.225.128^{🇺🇸 Amazon15.197.224.0/20}
NS	`ns21.domaincontrol.com` ⭐
		A	2603:5:2141::b^{🇺🇸 GODADDY-DNS2603:5:2140::/44}
			PTR	`ns21.domaincontrol.com`
		A	97.74.100.11^{🇺🇸 GODADDY-DNS97.74.100.0/23}
			PTR	`ns21.domaincontrol.com`
NS	`ns22.domaincontrol.com`
		A	2603:5:2241::b^{🇺🇸 GODADDY-DNS2603:5:2240::/44}
			PTR	`ns22.domaincontrol.com`
		A	173.201.68.11^{🇺🇸 GODADDY-DNS173.201.68.0/23}
			PTR	`ns22.domaincontrol.com`
SOA	`ns21.domaincontrol.com`dns@jomax.net 2025-08-08 #3

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

DNS History

11 records (4 active, 7 former)

○NSns1.nsresponse.com2016-09-15 → 2016-09-15 · 3 obs

○ 2016-03-28 14:54:10
● 2016-09-15 05:58:56
○ 2026-03-27 07:27:10

○NSns1.vigilantinternet.com2015-05-24 → 2016-03-28 · 4 obs

● 2015-05-24 07:20:34
● 2016-03-28 14:54:10
○ 2016-09-15 05:58:56
○ 2026-03-27 07:27:10

○NSns2.nsresponse.com2016-09-15 → 2016-09-15 · 3 obs

○ 2016-03-28 14:54:10
● 2016-09-15 05:58:56
○ 2026-03-27 07:27:10

○NSns2.vigilantinternet.com2015-05-24 → 2016-03-28 · 4 obs

● 2015-05-24 07:20:34
● 2016-03-28 14:54:10
○ 2016-09-15 05:58:56
○ 2026-03-27 07:27:10

●NSns21.domaincontrol.com2026-03-27 → 2026-03-27 · 2 obs

○ 2016-09-15 05:58:56
● 2026-03-27 07:27:10

●NSns22.domaincontrol.com2026-03-27 → 2026-03-27 · 2 obs

○ 2016-09-15 05:58:56
● 2026-03-27 07:27:10

○MXvigilantinternet.com2015-05-24 → 2016-09-15 · 3 obs

● 2015-05-24 07:20:34
● 2016-09-15 05:58:56
○ 2026-03-27 07:27:10

●A15.197.225.1282026-03-27 → 2026-03-27 · 2 obs

○ 2016-09-15 05:58:56
● 2026-03-27 07:27:10

○A204.93.177.1012016-09-15 → 2016-09-15 · 3 obs

○ 2016-03-28 14:54:10
● 2016-09-15 05:58:56
○ 2026-03-27 07:27:10

●A3.33.251.1682026-03-27 → 2026-03-27 · 2 obs

○ 2016-09-15 05:58:56
● 2026-03-27 07:27:10

○A74.81.66.1062015-05-24 → 2016-03-28 · 4 obs

● 2015-05-24 07:20:34
● 2016-03-28 14:54:10
○ 2016-09-15 05:58:56
○ 2026-03-27 07:27:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
vigilantinternet.com	ns21.domaincontrol.com, ns22.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.100.11

NS records: ns21.domaincontrol.com, ns22.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for vigilantinternet.com (unsigned zone)

⏱️ Timing

Total: 67ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`15.197.225.128, 3.33.251.168`
NS	2	`ns21.domaincontrol.com, ns22.domaincontrol.com`
SOA	1	`ns21.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns21.domaincontrol.com, ns21.domaincontrol.com, ns22.domaincontrol.com...)

Analysis

IP Addresses

vigilantinternet.com resolves to two IP numbers: 3.33.251.168 and 15.197.225.128.

other host names including constancepond.com, genomicsignature.net, smallerglass.com, mdheartdoc.org and columbusdjcompany.net share IP numbers with vigilantinternet.com.

Name Servers

vigilantinternet.com is delegated to two name servers ns21.domaincontrol.com and ns22.domaincontrol.com.

vigilantinternet.com shares the same name server setup as other domains, for instance visionon.tv, cubicalhomes.com, wdami.com, ecoshell.com.mx and pattysaggio.com.

Host names with two IP numbers:

The host name ns21.domaincontrol.com points to 2603:5:2141::b and 97.74.100.11; the host name ns22.domaincontrol.com points to 2603:5:2241::b and 173.201.68.11.

vigilantinternet.com - robtex.com