devicecomponents.com - dns.ninja

`devicecomponents.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3032::6815:4765^{🇺🇸 Cloudflare2606:4700:3032::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3033::ac43:9061^{🇺🇸 Cloudflare2606:4700:3033::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.71.101^{Cloudflare104.21.64.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.144.97^{🇺🇸 Cloudflare172.67.144.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.71.101, 172.67.144.97
		IPv6 hints	2606:4700:3032::6815:4765, 2606:4700:3033::ac43:9061
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=155, name=cloudflare-ech.com
SOA	`ns1.domainmanage.com`dns@cloudflare.com serial=2408077912

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

Same first word

devicecomponents.com

DNS History

16 records (6 active, 10 former)

○NSbuy.internettraffic.com2015-08-17 → 2016-07-23 · 4 obs

● 2015-08-17 19:30:26
● 2016-07-23 18:55:04
○ 2017-03-26 11:31:22
○ 2026-07-30 05:15:04

○NSns1.afternic.com2026-03-26 → 2026-04-07 · 4 obs

○ 2017-03-26 11:31:22
● 2026-03-26 23:18:08
● 2026-04-07 03:10:00
○ 2026-07-30 05:15:04

●NSns1.domainmanage.com2026-07-30 → 2026-07-30 · 2 obs

○ 2026-04-07 03:10:00
● 2026-07-30 05:15:04

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

○ 2016-07-23 18:55:04
● 2017-03-26 11:31:22
○ 2026-03-26 23:18:08
○ 2026-07-30 05:15:04

○NSns2.afternic.com2026-03-26 → 2026-04-07 · 4 obs

○ 2017-03-26 11:31:22
● 2026-03-26 23:18:08
● 2026-04-07 03:10:00
○ 2026-07-30 05:15:04

●NSns2.domainmanage.com2026-07-30 → 2026-07-30 · 2 obs

○ 2026-04-07 03:10:00
● 2026-07-30 05:15:04

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

○ 2016-07-23 18:55:04
● 2017-03-26 11:31:22
○ 2026-03-26 23:18:08
○ 2026-07-30 05:15:04

○NSsell.internettraffic.com2015-08-17 → 2016-07-23 · 4 obs

● 2015-08-17 19:30:26
● 2016-07-23 18:55:04
○ 2017-03-26 11:31:22
○ 2026-07-30 05:15:04

●A104.21.71.1012026-07-30 → 2026-07-30 · 2 obs

○ 2026-04-07 03:10:00
● 2026-07-30 05:15:04

○A13.248.169.482026-03-26 → 2026-04-07 · 4 obs

○ 2017-03-26 11:31:22
● 2026-03-26 23:18:08
● 2026-04-07 03:10:00
○ 2026-07-30 05:15:04

●A172.67.144.972026-07-30 → 2026-07-30 · 2 obs

○ 2026-04-07 03:10:00
● 2026-07-30 05:15:04

●A2606:4700:3032::6815:47652026-07-30 → 2026-07-30 · 2 obs

○ 2026-04-07 03:10:00
● 2026-07-30 05:15:04

●A2606:4700:3033::ac43:90612026-07-30 → 2026-07-30 · 2 obs

○ 2026-04-07 03:10:00
● 2026-07-30 05:15:04

○A69.172.201.1532016-07-23 → 2017-03-26 · 5 obs

○ 2016-03-27 02:20:02
● 2016-07-23 18:55:04
● 2017-03-26 11:31:22
○ 2026-03-26 23:18:08
○ 2026-07-30 05:15:04

○A69.172.201.2082015-08-17 → 2016-03-27 · 4 obs

● 2015-08-17 19:30:26
● 2016-03-27 02:20:02
○ 2016-07-23 18:55:04
○ 2026-07-30 05:15:04

○A76.223.54.1462026-03-26 → 2026-04-07 · 4 obs

○ 2017-03-26 11:31:22
● 2026-03-26 23:18:08
● 2026-04-07 03:10:00
○ 2026-07-30 05:15:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	f.gtld-servers.net, g.gtld-servers.net, c.gtld-servers.net, i.gtld-servers.net...	-
devicecomponents.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 devicecomponents.com (unsigned zone)

⏱️ Timing

Total: 215ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.71.101, 172.67.144.97`
AAAA	2	`2606:4700:3033::ac43:9061, 2606:4700:3032::6815:4765`
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

devicecomponents.com resolves to four IP addresses: 104.21.71.101, 172.67.144.97, 2606:4700:3032::6815:4765 and 2606:4700:3033::ac43:9061.

Two other host names, along with lytherionvas.com, coldgames.fun and pessarylayer.click, also share IP numbers with devicecomponents.com.

Name Servers

devicecomponents.com has two authoritative name servers — ns1.domainmanage.com and ns2.domainmanage.com.

devicecomponents.com shares its NS records with other domains, for example ipselection.com, ipangels.com, burw.com and two others.

Both ns1.domainmanage.com and ns2.domainmanage.com have two IP addresses each. ns1.domainmanage.com resolves to 173.245.59.4 and 2400:cb00:2049:1::adf5:3b04; ns2.domainmanage.com resolves to 198.41.223.39 and 2400:cb00:2049:1::c629:df27.