`owlmonitoring.com`

DNSSEC	⚠️ Not signed
A	3.33.130.190^{🇺🇸 Amazon3.33.128.0/20}
		PTR	`a2aa9ff50de748dbe.awsglobalaccelerator.com`
A	15.197.148.33^{🇺🇸 Amazon15.197.144.0/20}
NS	`ns59.domaincontrol.com` ⭐
		A	2603:5:2143::1f^{🇺🇸 GODADDY-DNS2603:5:2140::/44}
			PTR	`mns01.domaincontrol.com`
		A	97.74.100.31^{🇺🇸 GODADDY-DNS97.74.100.0/23}
			PTR	`ns59.domaincontrol.com`
NS	`ns60.domaincontrol.com`
		A	2603:5:2243::1f^{🇺🇸 GODADDY-DNS2603:5:2240::/44}
			PTR	`mns02.domaincontrol.com`
		A	173.201.68.31^{🇺🇸 GODADDY-DNS173.201.68.0/23}
			PTR	`ns60.domaincontrol.com`
SOA	`ns59.domaincontrol.com`dns@jomax.net 2023-09-20 #0

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

Same first word

owlmonitoring.com

DNS History

10 records (4 active, 6 former)

○NSns1.dns-h.com2017-09-28 → 2017-09-28 · 3 obs

● 2017-09-28 05:26:22
○ 2026-04-03 11:56:00
○ 2026-04-25 22:01:24

○NSns1.host-h.net2017-09-28 → 2017-09-28 · 3 obs

● 2017-09-28 05:26:22
○ 2026-04-03 11:56:00
○ 2026-04-25 22:01:24

○NSns2.dns-h.com2017-09-28 → 2017-09-28 · 3 obs

● 2017-09-28 05:26:22
○ 2026-04-03 11:56:00
○ 2026-04-25 22:01:24

○NSns2.host-h.net2017-09-28 → 2017-09-28 · 3 obs

● 2017-09-28 05:26:22
○ 2026-04-03 11:56:00
○ 2026-04-25 22:01:24

●NSns59.domaincontrol.com2026-04-03 → 2026-04-25 · 3 obs

○ 2017-09-28 05:26:22
● 2026-04-03 11:56:00
● 2026-04-25 22:01:24

●NSns60.domaincontrol.com2026-04-03 → 2026-04-25 · 3 obs

○ 2017-09-28 05:26:22
● 2026-04-03 11:56:00
● 2026-04-25 22:01:24

○MXmail.owlmonitoring.com2017-09-28 → 2017-09-28 · 3 obs

● 2017-09-28 05:26:22
○ 2026-04-03 11:56:00
○ 2026-04-25 22:01:24

○A129.232.136.232017-09-28 → 2017-09-28 · 3 obs

● 2017-09-28 05:26:22
○ 2026-04-03 11:56:00
○ 2026-04-25 22:01:24

●A15.197.148.332026-04-03 → 2026-04-25 · 3 obs

○ 2017-09-28 05:26:22
● 2026-04-03 11:56:00
● 2026-04-25 22:01:24

●A3.33.130.1902026-04-03 → 2026-04-25 · 3 obs

○ 2017-09-28 05:26:22
● 2026-04-03 11:56:00
● 2026-04-25 22:01:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	j.gtld-servers.net, c.gtld-servers.net, h.gtld-servers.net, g.gtld-servers.net...	-
owlmonitoring.com	ns59.domaincontrol.com, ns60.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.68.31

NS records: ns59.domaincontrol.com, ns60.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for owlmonitoring.com (unsigned zone)

⏱️ Timing

Total: 693ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`3.33.130.190, 15.197.148.33`
NS	2	`ns59.domaincontrol.com, ns60.domaincontrol.com`
SOA	1	`ns59.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns59.domaincontrol.com, ns59.domaincontrol.com, ns60.domaincontrol.com...)

Analysis

IP Addresses

owlmonitoring.com points to two IP numbers: 3.33.130.190 and 15.197.148.33.

Other host names, for instance gnarlygator.com, nightlifesandiego.com, llapp.net, bicyclepub.com and bunkerbuild.com share IP numbers with owlmonitoring.com.

Name Servers

owlmonitoring.com's delegation is to two name servers ns59.domaincontrol.com and ns60.domaincontrol.com.

owlmonitoring.com shares the same name server configuration as other domains, such as camcbd.com, spicyberry.com, arc-ad.org, wangbaohe.com and bufeteramirezcr.com.

owlmonitoring.com shares name servers with other domains at least partially, for example recuberdds.com.

Host names with two IP numbers: ns59.domaincontrol.com points to 2603:5:2143::1f and 97.74.100.31; ns60.domaincontrol.com points to 2603:5:2243::1f and 173.201.68.31

owlmonitoring.com - robtex.com