`dmdangels.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:aa86:dc69:2f3:5dbe^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1b:3376:e04f:851f:406c^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1b:a510:c365:d06a:e73a^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	52.91.47.137^{🇺🇸 Amazon52.90.0.0/15 EC2 IAD prefix}
			PTR	`ec2-52-91-47-137.compute-1.amazonaws.com`
		A	54.92.199.119^{🇺🇸 Amazon54.92.128.0/17 EC2 IAD prefix}
			PTR	`ec2-54-92-199-119.compute-1.amazonaws.com`
		A	98.83.163.23^{🇺🇸 Amazon98.80.0.0/13 EC2 IAD Prefix}
			PTR	`ec2-98-83-163-23.compute-1.amazonaws.com`
NS	`nsg1.namebrightdns.com`
		A	2600:1f18:683a:ae1a:e5a9:8ee2:a408:496a^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1a:e842:8110:107c:b494^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1b:6b1c:bb29:2e34:d31d^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1b:a136:1971:9598:5d4a^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	13.221.125.168^{🇺🇸 Amazon13.216.0.0/13 EC2 IAD prefix}
			PTR	`ec2-13-221-125-168.compute-1.amazonaws.com`
		A	44.220.149.224^{🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix}
			PTR	`ec2-44-220-149-224.compute-1.amazonaws.com`
		A	54.90.222.89^{🇺🇸 Amazon54.90.0.0/15 EC2 IAD prefix}
			PTR	`ec2-54-90-222-89.compute-1.amazonaws.com`
		A	54.221.168.107^{🇺🇸 Amazon54.221.0.0/16 EC2 IAD prefix}
			PTR	`ec2-54-221-168-107.compute-1.amazonaws.com`
NS	`nsg2.namebrightdns.com`
		A	2600:1f18:683a:ae1a:5de3:627d:7177:d4b4^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1a:e1f7:fcf3:dce8:5758^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1b:130f:6e59:4e36:8c1e^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1b:9806:d504:f0e4:26c^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1b:eda8:cb11:b8f:c1fe^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	3.82.54.251^{🇺🇸 Amazon3.80.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-82-54-251.compute-1.amazonaws.com`
		A	3.85.217.230^{🇺🇸 Amazon3.80.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-85-217-230.compute-1.amazonaws.com`
		A	3.89.204.207^{🇺🇸 Amazon3.80.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-89-204-207.compute-1.amazonaws.com`
		A	54.145.228.233^{🇺🇸 Amazon54.144.0.0/14 EC2 IAD NAT prefix}
			PTR	`ec2-54-145-228-233.compute-1.amazonaws.com`
		A	98.93.89.251^{🇺🇸 Amazon98.88.0.0/13 EC2 IAD prefix}
			PTR	`ec2-98-93-89-251.compute-1.amazonaws.com`
TXT	`afternic-verification-G9G3tM8T8EwEizzPzjGJWF`
TXT	`v=spf1 -all`
SOA	`ns1.namebrightdns.com`dns@namebright.com 2026-03-24 #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=1774393017

Same first word

dmdangels.com

Similar names

msgladden.com

🔍 DNS Trace

📋 Delegation Chain

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

✅ Authoritative Response

Server:3.85.217.230

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for dmdangels.com (unsigned zone)

⏱️ Timing

Total: 208ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 18

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

Analysis

IP Addresses

dmdangels.com resolves to four IP numbers: 2600:1f18:4ae:c605:dd5d:b838:5816:d7fb, 2600:1f18:4ae:c606:78d4:4260:db4e:aeee, 13.223.25.84 and 54.243.117.197.

Other host names such as nutritionindustries.com, mx.cloudfyre.com, bjmzd.com, imgrace.com and umsonstladen.com share IPs with dmdangels.com.

Name Servers

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

dmdangels.com at least partially shares name servers with other domains, for instance saasd.com, chefgear.com, lovingdays.com, prepfrog.com and twoguys.com.