whyreply.com - dns.ninja

`whyreply.com`

DNSSEC	⚠️ Not signed
A	2600:1f18:4ae:c605:dd5d:b838:5816:d7fb^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
A	2600:1f18:4ae:c606:78d4:4260:db4e:aeee^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
A	13.223.25.84^{🇺🇸 Amazon13.216.0.0/13 EC2 IAD prefix}
A	54.243.117.197^{🇺🇸 Amazon54.242.0.0/15 EC2 IAD prefix}
NS	`ns1.namebrightdns.com` ⭐
		A	2600:1f18:683a:ae1a:6900:d1bd:7672:d0ca^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1a:7bc2:638d:8ca6:fcc4^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1b:d57d:390a:64b4:d4f1^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	52.203.211.134^{🇺🇸 Amazon52.200.0.0/13 EC2 IAD prefix}
			PTR	`ec2-52-203-211-134.compute-1.amazonaws.com`
		A	52.204.81.90^{🇺🇸 Amazon52.200.0.0/13 EC2 IAD prefix}
			PTR	`ec2-52-204-81-90.compute-1.amazonaws.com`
NS	`nsg1.namebrightdns.com`
		A	2600:1f18:683a:ae1a:4a5c:f736:fa58:d85^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1a:7b03:f4b:4bfa:8287^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1a:b159:2be8:f48c:b374^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	13.221.131.54^{🇺🇸 Amazon13.216.0.0/13 EC2 IAD prefix}
			PTR	`ec2-13-221-131-54.compute-1.amazonaws.com`
		A	13.222.195.178^{🇺🇸 Amazon13.216.0.0/13 EC2 IAD prefix}
			PTR	`ec2-13-222-195-178.compute-1.amazonaws.com`
		A	54.175.130.15^{🇺🇸 Amazon54.174.0.0/15 EC2 IAD prefix}
			PTR	`ec2-54-175-130-15.compute-1.amazonaws.com`
NS	`nsg2.namebrightdns.com`
		A	2600:1f18:683a:ae1b:5b81:82bc:6de0:b02c^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1b:b942:bb73:2f59:d7af^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1b:da4a:4683:1131:8bce^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	3.80.109.14^{🇺🇸 Amazon3.80.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-80-109-14.compute-1.amazonaws.com`
		A	98.81.3.34^{🇺🇸 Amazon98.80.0.0/13 EC2 IAD Prefix}
			PTR	`ec2-98-81-3-34.compute-1.amazonaws.com`
		A	98.83.212.177^{🇺🇸 Amazon98.80.0.0/13 EC2 IAD Prefix}
			PTR	`ec2-98-83-212-177.compute-1.amazonaws.com`
TXT	`afternic-verification-G9G3tM8T8EwEizzPzjGJWF`
TXT	`v=spf1 -all`
SOA	`ns1.namebrightdns.com`dns@namebright.com 2026-07-01 #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=1782941341

WOT: SAFE (29/100)

Same first word

whyreply.com

DNS History

10 records (7 active, 3 former)

●NSns1.namebrightdns.com2026-03-30 → 2026-07-01 · 3 obs

○ 2020-02-18 19:58:14
● 2026-03-30 09:22:18
● 2026-07-01 21:34:34

○NSns71.domaincontrol.com2020-02-18 → 2020-02-18 · 3 obs

● 2020-02-18 19:58:14
○ 2026-03-30 09:22:18
○ 2026-07-01 21:34:34

○NSns72.domaincontrol.com2020-02-18 → 2020-02-18 · 3 obs

● 2020-02-18 19:58:14
○ 2026-03-30 09:22:18
○ 2026-07-01 21:34:34

●NSnsg1.namebrightdns.com2026-03-30 → 2026-07-01 · 3 obs

○ 2020-02-18 19:58:14
● 2026-03-30 09:22:18
● 2026-07-01 21:34:34

●NSnsg2.namebrightdns.com2026-03-30 → 2026-07-01 · 3 obs

○ 2020-02-18 19:58:14
● 2026-03-30 09:22:18
● 2026-07-01 21:34:34

●A13.223.25.842026-03-30 → 2026-07-01 · 3 obs

○ 2020-02-18 19:58:14
● 2026-03-30 09:22:18
● 2026-07-01 21:34:34

○A184.168.221.462020-02-18 → 2020-02-18 · 3 obs

● 2020-02-18 19:58:14
○ 2026-03-30 09:22:18
○ 2026-07-01 21:34:34

●A2600:1f18:4ae:c605:dd5d:b838:5816:d7fb2026-03-30 → 2026-07-01 · 3 obs

○ 2020-02-18 19:58:14
● 2026-03-30 09:22:18
● 2026-07-01 21:34:34

●A2600:1f18:4ae:c606:78d4:4260:db4e:aeee2026-03-30 → 2026-07-01 · 3 obs

○ 2020-02-18 19:58:14
● 2026-03-30 09:22:18
● 2026-07-01 21:34:34

●A54.243.117.1972026-03-30 → 2026-07-01 · 3 obs

○ 2020-02-18 19:58:14
● 2026-03-30 09:22:18
● 2026-07-01 21:34:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
whyreply.com	nsg1.namebrightdns.com, nsg2.namebrightdns.com	12 records

✅ Authoritative Response

Server:13.221.131.54

NS records: nsg1.namebrightdns.com, nsg2.namebrightdns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for whyreply.com (unsigned zone)

⏱️ Timing

Total: 294ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`13.223.25.84, 54.243.117.197`
AAAA	2	`2600:1f18:4ae:c605:dd5d:b838:5816:d7fb, 2600:1f18:4ae:c606:78d4:4260:db4e:aeee`
NS	2	`nsg1.namebrightdns.com, nsg2.namebrightdns.com`
TXT	2	`afternic-verification-G9G3tM8T8EwEizzPzj, v=spf1 -all`
SOA	1	`ns1.namebrightdns.com dns.namebright.com`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (nsg1.namebrightdns.com, nsg1.namebrightdns.com, nsg1.namebrightdns.com...)

Analysis

IP Addresses

whyreply.com has four IP addresses: 13.223.25.84, 54.243.117.197, 2600:1f18:4ae:c605:dd5d:b838:5816:d7fb and 2600:1f18:4ae:c606:78d4:4260:db4e:aeee.

newzb.com, casinogamesbet.com, yinyangtech.com and two other host names share IP numbers with whyreply.com.

Name Servers

whyreply.com is delegated to three name servers: ns1.namebrightdns.com, nsg1.namebrightdns.com and nsg2.namebrightdns.com.

whyreply.com shares at least some of its name servers with other domains, including boodao.com, higherled.com, koihomes.com and two others.

These name servers are frequently paired with the name servers ns2.namebrightdns.com, domain-for-sale.hugedomainsdns.com and forsale.hugedomainsdns.com.

Hostnames that resolve to 6 IP addresses:

nsg1.namebrightdns.com resolves to 13.221.131.54, 13.222.195.178, 54.175.130.15 and 3 other IP addresses.

nsg2.namebrightdns.com resolves to 3.80.109.14, 98.81.3.34, 98.83.212.177 and 3 other IP addresses.

Hostnames pointing to five IP numbers:

ns1.namebrightdns.com resolves to four IP addresses: 52.203.211.134, 52.204.81.90, 2600:1f18:683a:ae1a:6900:d1bd:7672:d0ca and two others.