ipangels.com - dns.ninja

`ipangels.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3035::ac43:c6c0^{🇺🇸 Cloudflare2606:4700:3035::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::6815:24be^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.36.190^{Cloudflare104.21.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.198.192^{🇺🇸 Cloudflare172.67.192.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`ns1.domainmanage.com` ⭐
		A	2400:cb00:2049:1::adf5:3b04^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	173.245.59.4^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.domainmanage.com`
		A	2400:cb00:2049:1::c629:df27^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	198.41.223.39^{Cloudflare198.41.223.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`cf-198-41-223-39.cloudflare.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.36.190, 172.67.198.192
		IPv6 hints	2606:4700:3035::ac43:c6c0, 2606:4700:3037::6815:24be
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=130, name=cloudflare-ech.com
SOA	`ns1.domainmanage.com`dns@cloudflare.com serial=2408076509

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

Same first word

ipangels.com

Similar names

DNS History

20 records (6 active, 14 former)

○NSbuy.internettraffic.com2015-11-27 → 2016-06-18 · 4 obs

● 2015-11-27 01:47:02
● 2016-06-18 17:56:14
○ 2017-02-03 18:37:38
○ 2026-08-01 22:32:54

○NSns1.afternic.com2026-06-28 → 2026-08-01 · 2 obs

○ 2026-06-28 04:57:30
○ 2026-08-01 22:32:54

●NSns1.domainmanage.com2026-06-28 → 2026-08-01 · 3 obs

○ 2017-02-03 18:37:38
● 2026-06-28 04:57:30
● 2026-08-01 22:32:54

○NSns1.uniregistrymarket.link2017-02-03 → 2017-02-03 · 4 obs

○ 2016-06-18 17:56:14
● 2017-02-03 18:37:38
○ 2026-06-28 04:57:30
○ 2026-08-01 22:32:54

○NSns2.afternic.com2026-06-28 → 2026-08-01 · 2 obs

○ 2026-06-28 04:57:30
○ 2026-08-01 22:32:54

●NSns2.domainmanage.com2026-06-28 → 2026-08-01 · 3 obs

○ 2017-02-03 18:37:38
● 2026-06-28 04:57:30
● 2026-08-01 22:32:54

○NSns2.uniregistrymarket.link2017-02-03 → 2017-02-03 · 4 obs

○ 2016-06-18 17:56:14
● 2017-02-03 18:37:38
○ 2026-06-28 04:57:30
○ 2026-08-01 22:32:54

○NSsell.internettraffic.com2015-11-27 → 2016-06-18 · 4 obs

● 2015-11-27 01:47:02
● 2016-06-18 17:56:14
○ 2017-02-03 18:37:38
○ 2026-08-01 22:32:54

●A104.21.36.1902026-07-09 → 2026-08-01 · 3 obs

○ 2026-06-28 04:57:30
● 2026-07-09 12:41:32
● 2026-08-01 22:32:54

○A13.248.169.482026-06-28 → 2026-08-01 · 2 obs

○ 2026-06-28 04:57:30
○ 2026-08-01 22:32:54

●A172.67.198.1922026-07-09 → 2026-08-01 · 3 obs

○ 2026-06-28 04:57:30
● 2026-07-09 12:41:32
● 2026-08-01 22:32:54

○A188.114.96.02026-06-28 → 2026-06-28 · 4 obs

○ 2017-02-03 18:37:38
● 2026-06-28 04:57:30
○ 2026-07-09 12:41:32
○ 2026-08-01 22:32:54

○A188.114.97.02026-06-28 → 2026-06-28 · 4 obs

○ 2017-02-03 18:37:38
● 2026-06-28 04:57:30
○ 2026-07-09 12:41:32
○ 2026-08-01 22:32:54

●A2606:4700:3035::ac43:c6c02026-07-09 → 2026-08-01 · 3 obs

○ 2026-06-28 04:57:30
● 2026-07-09 12:41:32
● 2026-08-01 22:32:54

●A2606:4700:3037::6815:24be2026-07-09 → 2026-08-01 · 3 obs

○ 2026-06-28 04:57:30
● 2026-07-09 12:41:32
● 2026-08-01 22:32:54

○A2a06:98c1:3120::2026-06-28 → 2026-06-28 · 4 obs

○ 2017-02-03 18:37:38
● 2026-06-28 04:57:30
○ 2026-07-09 12:41:32
○ 2026-08-01 22:32:54

○A2a06:98c1:3121::2026-06-28 → 2026-06-28 · 4 obs

○ 2017-02-03 18:37:38
● 2026-06-28 04:57:30
○ 2026-07-09 12:41:32
○ 2026-08-01 22:32:54

○A69.172.201.1532016-06-18 → 2017-02-03 · 5 obs

○ 2016-03-01 19:04:34
● 2016-06-18 17:56:14
● 2017-02-03 18:37:38
○ 2026-06-28 04:57:30
○ 2026-08-01 22:32:54

○A69.172.201.2082015-11-27 → 2016-03-01 · 4 obs

● 2015-11-27 01:47:02
● 2016-03-01 19:04:34
○ 2016-06-18 17:56:14
○ 2026-08-01 22:32:54

○A76.223.54.1462026-06-28 → 2026-08-01 · 2 obs

○ 2026-06-28 04:57:30
○ 2026-08-01 22:32:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
ipangels.com	ns1.domainmanage.com, ns2.domainmanage.com	2 records

✅ Authoritative Response

Server:173.245.59.4

NS records: ns1.domainmanage.com, ns2.domainmanage.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ipangels.com (unsigned zone)

⏱️ Timing

Total: 116ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.36.190, 172.67.198.192`
AAAA	2	`2606:4700:3037::6815:24be, 2606:4700:3035::ac43:c6c0`
NS	2	`ns1.domainmanage.com, ns2.domainmanage.com`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`ns1.domainmanage.com dns.cloudflare.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.domainmanage.com, ns2.domainmanage.com)

Analysis

IP Addresses

ipangels.com has four IP addresses: 104.21.36.190, 172.67.198.192, 2606:4700:3035::ac43:c6c0 and 2606:4700:3037::6815:24be.

Additional host names — terraemc.net, www.dominicanrepublicnews.net, mail.hbtrqc.com and two others — share IP numbers with ipangels.com.

Name Servers

ipangels.com is served by two delegated name servers, ns1.domainmanage.com and ns2.domainmanage.com.

ipangels.com shares its name server setup with other domains, including videoforlawyers.com, goldfarbs.com, expressinstallations.com and two others.

Each of the two host names carries two IP addresses: ns1.domainmanage.com points to 173.245.59.4 and 2400:cb00:2049:1::adf5:3b04, and ns2.domainmanage.com points to 198.41.223.39 and 2400:cb00:2049:1::c629:df27.