`why-monster.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	`ns65.domaincontrol.com` ⭐
		A	2603:5:2164::2b^{🇺🇸 GODADDY-DNS2603:5:2160::/44}
			PTR	`ns65.domaincontrol.com`
		A	97.74.102.43^{🇺🇸 GODADDY-DNS97.74.102.0/23}
			PTR	`ns65.domaincontrol.com`
NS	`ns66.domaincontrol.com`
		A	2603:5:2264::2b^{🇺🇸 GODADDY-DNS2603:5:2260::/44}
			PTR	`ns66.domaincontrol.com`
		A	173.201.70.43^{🇺🇸 GODADDY-DNS173.201.70.0/23}
			PTR	`ns66.domaincontrol.com`
SOA	`ns65.domaincontrol.com`dns@jomax.net 2026-03-21 #1

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

Same first word

why-monster.com

DNS History

7 records (4 active, 3 former)

●NSns65.domaincontrol.com2020-04-09 → 2026-03-26 · 2 obs

● 2020-04-09 01:33:36
● 2026-03-26 16:19:20

●NSns66.domaincontrol.com2020-04-09 → 2026-03-26 · 2 obs

● 2020-04-09 01:33:36
● 2026-03-26 16:19:20

○A15.197.142.1732026-03-26 → 2026-03-26 · 1 obs

○ 2026-03-26 16:19:20

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

○ 2020-04-09 01:33:36
● 2026-03-26 16:19:20

○A184.168.131.2412020-04-09 → 2020-04-09 · 2 obs

● 2020-04-09 01:33:36
○ 2026-03-26 16:19:20

○A3.33.152.1472026-03-26 → 2026-03-26 · 1 obs

○ 2026-03-26 16:19:20

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

○ 2020-04-09 01:33:36
● 2026-03-26 16:19:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
why-monster.com	ns66.domaincontrol.com, ns65.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.70.43

NS records: ns66.domaincontrol.com, ns65.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for why-monster.com (unsigned zone)

⏱️ Timing

Total: 108ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns66.domaincontrol.com, ns66.domaincontrol.com, ns65.domaincontrol.com...)

Analysis

IP Addresses

why-monster.com points to two IP numbers: 3.33.251.168 and 15.197.225.128.

Other host names, for instance at-pac.ca, brench.co.uk, goldcanyoncandle.com, amfaleroinsurance.com and cowboyshootouts.com share IP numbers with why-monster.com.

Name Servers

why-monster.com's delegation is to two name servers ns65.domaincontrol.com and ns66.domaincontrol.com.

why-monster.com shares the same name server configuration as other domains, such as milkglasskitchen.com, artofblack.com, thepressroom.com, agile4solutions.com and lakegreesonlodging.com.

why-monster.com shares name servers with other domains at least partially, for example pics2dvd.net.

Host names with two IP numbers: ns65.domaincontrol.com points to 2603:5:2164::2b and 97.74.102.43; ns66.domaincontrol.com points to 2603:5:2264::2b and 173.201.70.43

why-monster.com - robtex.com

why-monster.com

com