cloudtechnologypartners.com - dns.ninja

`cloudtechnologypartners.com`

DNSSEC	⚠️ Not signed
A	16.230.112.216^{🇺🇸 AS216516.230.96.0/19 CyrusOne-Proxy for Customer}
		PTR	`hpe.is`
		PTR	`arun.ly`
		PTR	`remoteaccess.hpe.com`
		PTR	`z2z-hpecom-static-prd-01.it.hpe.com`
NS	`cha08hpeibdns0a.ams.hpecore.net` ⭐
		A	10.78.58.213
NS	`ns1.hpe.com`
		A	192.58.206.184^{🇺🇸 AS2165192.58.206.0/24 CyrusOne-Proxy for Customer}
			PTR	`ns5.hpe.com`
NS	`ns2.hpe.com`
		A	192.58.207.221^{🇺🇸 AS2165192.58.207.0/24 CyrusOne-Proxy for Customer}
			PTR	`ns6.hpe.com`
NS	`ns3.hpe.com`
		A	16.2.141.20^{🇨🇭 Hewlett-Packard-Enterprise-Maidstone16.2.140.0/22 HPE, Switzerland GVA01}
			PTR	`gva01hpeibdns0a.ext.hpecore.net`
NS	`ns4.hpe.com`
		A	16.2.138.125^{🇮🇳 HEWLETT-PACKARD-ENTERPRISE-APJ16.2.138.0/23 HPE, Bangalore, India (IEC) Airtel}
			PTR	`iec01hpeibdns0a.ext.hpecore.net`
NS	`ns5.hpe.com`
		A	192.58.206.184^{🇺🇸 AS2165192.58.206.0/24 CyrusOne-Proxy for Customer}
			PTR	`ns5.hpe.com`
NS	`ns6.hpe.com`
		A	192.58.207.221^{🇺🇸 AS2165192.58.207.0/24 CyrusOne-Proxy for Customer}
			PTR	`ns6.hpe.com`
NS	`ns7.hpe.com`
		A	16.2.141.21^{🇨🇭 Hewlett-Packard-Enterprise-Maidstone16.2.140.0/22 HPE, Switzerland GVA01}
			PTR	`gva01hpeibdns0b.ext.hpecore.net`
NS	`ns8.hpe.com`
		A	16.2.138.125^{🇮🇳 HEWLETT-PACKARD-ENTERPRISE-APJ16.2.138.0/23 HPE, Bangalore, India (IEC) Airtel}
			PTR	`iec01hpeibdns0a.ext.hpecore.net`
SOA	`cha08hpeibdns0a.ams.hpecore.net`ddi-hostmaster@groups.ext.hpe.com serial=20260409

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

Same first word

cloudtechnologypartners.net

cloudtechnologypartners.com

DNS History

20 records (10 active, 10 former)

○NScce02hpeibpe.ams.hpecore.net2019-09-20 → 2021-01-30 · 5 obs

○ 2017-04-20 14:06:40
● 2019-09-20 23:27:30
● 2021-01-30 16:55:06
○ 2026-07-05 01:31:18
○ 2026-07-05 01:31:20

●NScha08hpeibdns0a.ams.hpecore.net2026-07-05 → 2026-07-05 · 3 obs

○ 2021-01-30 16:55:06
● 2026-07-05 01:31:18
● 2026-07-05 01:31:20

●NSns1.hpe.com2019-09-20 → 2026-07-05 · 3 obs

○ 2017-04-20 14:06:40
● 2019-09-20 23:27:30
● 2026-07-05 01:31:20

●NSns2.hpe.com2019-09-20 → 2026-07-05 · 3 obs

○ 2017-04-20 14:06:40
● 2019-09-20 23:27:30
● 2026-07-05 01:31:20

○NSns29.domaincontrol.com2015-05-03 → 2017-04-20 · 4 obs

● 2015-05-03 21:33:52
● 2017-04-20 14:06:40
○ 2019-09-20 23:27:30
○ 2026-07-05 01:31:20

●NSns3.hpe.com2019-09-20 → 2026-07-05 · 3 obs

○ 2017-04-20 14:06:40
● 2019-09-20 23:27:30
● 2026-07-05 01:31:20

○NSns30.domaincontrol.com2015-05-03 → 2017-04-20 · 4 obs

● 2015-05-03 21:33:52
● 2017-04-20 14:06:40
○ 2019-09-20 23:27:30
○ 2026-07-05 01:31:20

●NSns4.hpe.com2019-09-20 → 2026-07-05 · 3 obs

○ 2017-04-20 14:06:40
● 2019-09-20 23:27:30
● 2026-07-05 01:31:20

●NSns5.hpe.com2019-09-20 → 2026-07-05 · 3 obs

○ 2017-04-20 14:06:40
● 2019-09-20 23:27:30
● 2026-07-05 01:31:20

●NSns6.hpe.com2019-09-20 → 2026-07-05 · 3 obs

○ 2017-04-20 14:06:40
● 2019-09-20 23:27:30
● 2026-07-05 01:31:20

●NSns7.hpe.com2019-09-20 → 2026-07-05 · 3 obs

○ 2017-04-20 14:06:40
● 2019-09-20 23:27:30
● 2026-07-05 01:31:20

●NSns8.hpe.com2019-09-20 → 2026-07-05 · 3 obs

○ 2017-04-20 14:06:40
● 2019-09-20 23:27:30
● 2026-07-05 01:31:20

○MXmailstore1.secureserver.net2015-05-03 → 2017-04-20 · 4 obs

● 2015-05-03 21:33:52
● 2017-04-20 14:06:40
○ 2019-09-20 23:27:30
○ 2026-07-05 01:31:20

○MXsmtp.secureserver.net2015-05-03 → 2017-04-20 · 4 obs

● 2015-05-03 21:33:52
● 2017-04-20 14:06:40
○ 2019-09-20 23:27:30
○ 2026-07-05 01:31:20

○A15.233.128.622019-09-20 → 2021-01-30 · 5 obs

○ 2017-04-20 14:06:40
● 2019-09-20 23:27:30
● 2021-01-30 16:55:06
○ 2026-07-05 01:31:18
○ 2026-07-05 01:31:20

○A15.233.160.632019-09-20 → 2021-01-30 · 5 obs

○ 2017-04-20 14:06:40
● 2019-09-20 23:27:30
● 2021-01-30 16:55:06
○ 2026-07-05 01:31:18
○ 2026-07-05 01:31:20

○A15.241.148.1192019-09-20 → 2021-01-30 · 5 obs

○ 2017-04-20 14:06:40
● 2019-09-20 23:27:30
● 2021-01-30 16:55:06
○ 2026-07-05 01:31:18
○ 2026-07-05 01:31:20

○A15.241.20.952019-09-20 → 2021-01-30 · 5 obs

○ 2017-04-20 14:06:40
● 2019-09-20 23:27:30
● 2021-01-30 16:55:06
○ 2026-07-05 01:31:18
○ 2026-07-05 01:31:20

●A16.230.112.2162026-07-05 → 2026-07-05 · 3 obs

○ 2021-01-30 16:55:06
● 2026-07-05 01:31:18
● 2026-07-05 01:31:20

○A184.168.221.312015-05-03 → 2017-04-20 · 4 obs

● 2015-05-03 21:33:52
● 2017-04-20 14:06:40
○ 2019-09-20 23:27:30
○ 2026-07-05 01:31:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
cloudtechnologypartners.com	ns3.hpe.com, ns1.hpe.com, ns2.hpe.com, ns4.hpe.com...	8 records

✅ Authoritative Response

Server:16.2.141.20

NS records: ns3.hpe.com, ns1.hpe.com, ns2.hpe.com, ns4.hpe.com, ns5.hpe.com, ns6.hpe.com, ns8.hpe.com, ns7.hpe.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for cloudtechnologypartners.com (unsigned zone)

⏱️ Timing

Total: 3419ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`16.230.112.216`
NS	8	`ns7.hpe.com, ns4.hpe.com...`
SOA	1	`cha08hpeibdns0a.ams.hpecore.net ddi-host`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns3.hpe.com, ns1.hpe.com, ns2.hpe.com...)

Analysis

IP Addresses

cloudtechnologypartners.com has exactly one IP address — 16.230.112.216.

nimblecloudvolumes.fr, hewlettpackard.ai, rvc-servers.cz plus two other host names have IP numbers in common with cloudtechnologypartners.com.

Name Servers

cloudtechnologypartners.com is served by 9 authoritative name servers — among them ns1.hpe.com, ns2.hpe.com, ns3.hpe.com and 6 others.

The name servers of cloudtechnologypartners.com overlap at least partially with those of other domains — among them hewlettpackardcustomerservice.com, hpe-iran.com, hpetowerservers.com and two more.

These name servers commonly appear in delegations together with ns4.hpe.com, ns5.hpe.com, ns6.hpe.com and 3 other.

Host names resolving to a single IP address:

The hostname ns1.hpe.com resolves to 192.58.206.184.

The hostname ns2.hpe.com resolves to 192.58.207.221.

The hostname ns3.hpe.com resolves to 16.2.141.20.

The hostname ns4.hpe.com resolves to 16.2.138.125.

The hostname ns5.hpe.com resolves to 192.58.206.184.

The hostname ns6.hpe.com resolves to 192.58.207.221.

The hostname ns7.hpe.com resolves to 16.2.141.21.

The hostname ns8.hpe.com resolves to 16.2.138.125.

The hostname cha08hpeibdns0a.ams.hpecore.net resolves to 10.78.58.213.

ns1.hpe.com along with ns5.hpe.com each resolve to 192.58.206.184 IP addresses.

ns2.hpe.com along with ns6.hpe.com each resolve to 192.58.207.221 IP addresses.

ns4.hpe.com along with ns8.hpe.com each resolve to 16.2.138.125 IP addresses.