🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`componentdevelopments.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3030::6815:228^{🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::ac43:80b0^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.2.40^{Cloudflare104.21.0.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.128.176^{🇺🇸 Cloudflare172.67.128.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`amanda.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a3f^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`amanda.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c03f^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`amanda.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:203f^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`amanda.ns.cloudflare.com`
		A	108.162.192.63^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`amanda.ns.cloudflare.com`
		A	172.64.32.63^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`amanda.ns.cloudflare.com`
		A	173.245.58.63^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`amanda.ns.cloudflare.com`
NS	`gordon.ns.cloudflare.com`
		A	2606:4700:58::adf5:3baa^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`gordon.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c1aa^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`gordon.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:21aa^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`gordon.ns.cloudflare.com`
		A	108.162.193.170^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`gordon.ns.cloudflare.com`
		A	172.64.33.170^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`gordon.ns.cloudflare.com`
		A	173.245.59.170^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`gordon.ns.cloudflare.com`
MX	`uk1-smtp-mx1.titanhq.com` ⭐
		A	3.10.37.203^{🇬🇧 Amazon3.8.0.0/14 EC2 LHR prefix}
			PTR	`uk1-smtp2.titanhq.com`
		A	13.41.39.52^{🇬🇧 Amazon13.40.0.0/14 EC2 LHR Prefix}
			PTR	`uk1-smtp1.titanhq.com`
		A	18.132.0.23^{🇬🇧 Amazon18.132.0.0/14 EC2 LHR prefix}
			PTR	`uk1-smtp2.titanhq.com`
		A	18.169.71.187^{🇬🇧 Amazon18.168.0.0/14 EC2 LHR prefix}
			PTR	`uk1-smtp1.titanhq.com`
MX	`uk1-smtp-mx2.titanhq.com` ⭐
		A	3.10.37.203^{🇬🇧 Amazon3.8.0.0/14 EC2 LHR prefix}
			PTR	`uk1-smtp2.titanhq.com`
		A	13.41.39.52^{🇬🇧 Amazon13.40.0.0/14 EC2 LHR Prefix}
			PTR	`uk1-smtp1.titanhq.com`
		A	18.132.0.23^{🇬🇧 Amazon18.132.0.0/14 EC2 LHR prefix}
			PTR	`uk1-smtp2.titanhq.com`
		A	18.169.71.187^{🇬🇧 Amazon18.168.0.0/14 EC2 LHR prefix}
			PTR	`uk1-smtp1.titanhq.com`
TXT	`MS=ms59351140`
TXT	`v=spf1 ip4:88.99.70.50 include:relay.mailbaby.net +a +mx +ip4:78.129.241.116 ...`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.2.40, 172.67.128.176
		IPv6 hints	2606:4700:3030::6815:228, 2606:4700:3037::ac43:80b0
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=188, name=cloudflare-ech.com
SOA	`amanda.ns.cloudflare.com`dns@cloudflare.com serial=2413250882

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

Same first word

componentdevelopments.co.uk

componentdevelopments.com

componentdevelopments.uk

Previous names

Next names

DNS History

20 records (8 active, 12 former)

●NSamanda.ns.cloudflare.com2026-08-19 → 2026-09-04 · 3 obs

○ 2017-08-09 04:51:16
● 2026-08-19 10:29:48
● 2026-09-04 17:33:44

●NSgordon.ns.cloudflare.com2026-08-19 → 2026-09-04 · 3 obs

○ 2017-08-09 04:51:16
● 2026-08-19 10:29:48
● 2026-09-04 17:33:44

○NSns.mainnameserver.com2015-06-30 → 2017-08-09 · 4 obs

● 2015-06-30 12:27:24
● 2017-08-09 04:51:16
○ 2026-08-19 10:29:48
○ 2026-09-04 17:33:44

○NSns2.mainnameserver.com2015-06-30 → 2017-08-09 · 4 obs

● 2015-06-30 12:27:24
● 2017-08-09 04:51:16
○ 2026-08-19 10:29:48
○ 2026-09-04 17:33:44

○MXcluster-1uk-mailguard.abl-net.net2015-06-30 → 2016-04-28 · 4 obs

● 2015-06-30 12:27:24
● 2016-04-28 04:46:00
○ 2017-02-20 06:36:48
○ 2026-09-04 17:33:44

○MXcluster-2uk-mailguard.abl-net.net2015-06-30 → 2016-04-28 · 4 obs

● 2015-06-30 12:27:24
● 2016-04-28 04:46:00
○ 2017-02-20 06:36:48
○ 2026-09-04 17:33:44

○MXmail.componentdevelopments.com2017-02-20 → 2017-08-09 · 5 obs

○ 2016-04-28 04:46:00
● 2017-02-20 06:36:48
● 2017-08-09 04:51:16
○ 2026-08-19 10:29:48
○ 2026-09-04 17:33:44

○MXsmtp.componentdevelopments.com2017-02-20 → 2017-08-09 · 5 obs

○ 2016-04-28 04:46:00
● 2017-02-20 06:36:48
● 2017-08-09 04:51:16
○ 2026-08-19 10:29:48
○ 2026-09-04 17:33:44

●MXuk1-smtp-mx1.titanhq.com2026-08-19 → 2026-09-04 · 3 obs

○ 2017-08-09 04:51:16
● 2026-08-19 10:29:48
● 2026-09-04 17:33:44

●MXuk1-smtp-mx2.titanhq.com2026-08-19 → 2026-09-04 · 3 obs

○ 2017-08-09 04:51:16
● 2026-08-19 10:29:48
● 2026-09-04 17:33:44

●A104.21.2.402026-09-03 → 2026-09-04 · 3 obs

○ 2026-08-19 10:29:48
● 2026-09-03 12:32:34
● 2026-09-04 17:33:44

●A172.67.128.1762026-09-03 → 2026-09-04 · 3 obs

○ 2026-08-19 10:29:48
● 2026-09-03 12:32:34
● 2026-09-04 17:33:44

○A185.38.36.1672016-02-09 → 2017-08-09 · 5 obs

○ 2015-11-15 06:21:22
● 2016-02-09 14:13:08
● 2017-08-09 04:51:16
○ 2026-08-19 10:29:48
○ 2026-09-04 17:33:44

○A188.114.96.02026-08-19 → 2026-08-19 · 4 obs

○ 2017-08-09 04:51:16
● 2026-08-19 10:29:48
○ 2026-09-03 12:32:34
○ 2026-09-04 17:33:44

○A188.114.97.02026-08-19 → 2026-08-19 · 4 obs

○ 2017-08-09 04:51:16
● 2026-08-19 10:29:48
○ 2026-09-03 12:32:34
○ 2026-09-04 17:33:44

○A217.199.187.682015-06-30 → 2015-11-15 · 4 obs

● 2015-06-30 12:27:24
● 2015-11-15 06:21:22
○ 2016-02-09 14:13:08
○ 2026-09-04 17:33:44

●A2606:4700:3030::6815:2282026-09-03 → 2026-09-04 · 3 obs

○ 2026-08-19 10:29:48
● 2026-09-03 12:32:34
● 2026-09-04 17:33:44

●A2606:4700:3037::ac43:80b02026-09-03 → 2026-09-04 · 3 obs

○ 2026-08-19 10:29:48
● 2026-09-03 12:32:34
● 2026-09-04 17:33:44

○A2a06:98c1:3120::2026-08-19 → 2026-08-19 · 4 obs

○ 2017-08-09 04:51:16
● 2026-08-19 10:29:48
○ 2026-09-03 12:32:34
○ 2026-09-04 17:33:44

○A2a06:98c1:3121::2026-08-19 → 2026-08-19 · 4 obs

○ 2017-08-09 04:51:16
● 2026-08-19 10:29:48
○ 2026-09-03 12:32:34
○ 2026-09-04 17:33:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
componentdevelopments.com	amanda.ns.cloudflare.com, gordon.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.193.170

NS records: amanda.ns.cloudflare.com, gordon.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for componentdevelopments.com (unsigned zone)

⏱️ Timing

Total: 600ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.128.176, 104.21.2.40`
AAAA	2	`2606:4700:3037::ac43:80b0, 2606:4700:3030::6815:228`
NS	2	`amanda.ns.cloudflare.com, gordon.ns.cloudflare.com`
MX	2	`uk1-smtp-mx1.titanhq.com (pri: 10), uk1-smtp-mx2.titanhq.com (pri: 10)`
TXT	2	`MS=ms59351140, v=spf1 ip4:88.99.70.50 include:relay.mai`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`amanda.ns.cloudflare.com dns.cloudflare.`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (amanda.ns.cloudflare.com, amanda.ns.cloudflare.com, amanda.ns.cloudflare.com...)

Analysis

IP Addresses

componentdevelopments.com points to the four IP addresses 104.21.2.40, 172.67.128.176, 2606:4700:3030::6815:228 and 2606:4700:3037::ac43:80b0.

Two other host names, along with atomiclabs.cc, dswdrivers.com.dswdrivers.com and lirkimfan.life, also share IP numbers with componentdevelopments.com.

Name Servers

componentdevelopments.com has two authoritative name servers — amanda.ns.cloudflare.com and gordon.ns.cloudflare.com.

componentdevelopments.com shares its NS records with other domains, for example bbntransportes.com, tecnico-amp.pages.dev, thammyvanity.vn and two others.

There is at least partial name server overlap between componentdevelopments.com and other domains — goaldifferential.com, merlin.onl, brefuvsi.pages.dev and two more among them.

These name servers frequently co-occur with the name servers diva.ns.cloudflare.com and aspen.ns.cloudflare.com.

DNS names with 6 IP addresses:

amanda.ns.cloudflare.com points to 108.162.192.63, 172.64.32.63, 173.245.58.63 and 3 other IP addresses.

gordon.ns.cloudflare.com points to 108.162.193.170, 172.64.33.170, 173.245.59.170 and 3 other IP addresses.

Mail Servers

componentdevelopments.com is served by two mail servers, uk1-smtp-mx1.titanhq.com and uk1-smtp-mx2.titanhq.com.

Among the domains sharing a mail server setup with componentdevelopments.com are tcn.ltd.uk, thecourtyardislington.org, rb1.co.uk and two others.

There is at least a partial MX overlap between componentdevelopments.com and other domains, including dragonpass.com, abraflex.co.uk, davidgamecollege.com and two others.

The hosts uk1-smtp-mx1.titanhq.com and uk1-smtp-mx2.titanhq.com each point to four IP addresses: uk1-smtp-mx1.titanhq.com resolves to 3.10.37.203, 13.41.39.52, 18.132.0.23 and 18.169.71.187 and uk1-smtp-mx2.titanhq.com directs to 3.10.37.203, 13.41.39.52, 18.132.0.23 and 18.169.71.187.