128technology.com - dns.ninja

`128technology.com`

DNSSEC	⚠️ Not signed
A	44.224.71.252^{🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix}
		PTR	`ec2-44-224-71-252.us-west-2.compute.amazonaws.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`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c17::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bl-in-f27.1e100.net`
		A	142.251.111.27^{🇺🇸 Google142.251.111.0/24}
			PTR	`bk-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c00::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`ws-in-f26.1e100.net`
			PTR	`ws-in-x1a.1e100.net`
		A	173.194.76.27^{🇺🇸 Google173.194.76.0/24}
			PTR	`ws-in-f27.1e100.net`
TXT	`google-site-verification=Ryx7OxW9JS8LmGsD1xwnyMtG3XoEL5F5dUE-aeD9Ag0`
TXT	`v=DMARC1;p=reject;sp=reject;fo=1;rua=mailto:dmarc_rua@emaildefense.proofpoint...`
TXT	`atlassian-domain-verification=e1WmGF2gcUpZ5dkYBJoEOKUdPVln2dEvQ4SZU8v7S2G7U+h...`
TXT	`google-site-verification=HA91zcw4Qlc9HwUQ2O62iR6dOwygLMI8gELdT_5OzzI`
TXT	`google-site-verification=lAD3d4Yxs-gFdxGv5epMlzhlKR7aAv0alrNQvA87gqs`
TXT	`MS=ms46595271`
TXT	`atlassian-domain-verification=e1c-4btnZbGi6jD/ewRkzCKQlVURyn2OGGM6iYJHzv4JdjF...`
TXT	`google-site-verification=P73i-7EMhe3ha26nGtAJXAxF_8L1B5eTVexa62tU4Vg`
TXT	`v=spf1 include:_spf.google.com include:aspmx.pardot.com ~all`
TXT	`docusign=a53fe22a-c3bc-469a-96cc-f630aa9dcf02`
TXT	`pardot728423=17ceced700601cf3ca6fb8bcecd1246fa5482212c7fe2b82b6ed9923a16c20f8`
SOA	`cha08hpeibdns0a.ams.hpecore.net`ddi-hostmaster@groups.ext.hpe.com serial=20260421

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

📈 Tranco rank: #56,894

Subdomains

response.128technology.com

www.128technology.com

yum.128technology.com

Same first word

128technology.com

128technology.jp

DNS History

32 records (15 active, 17 former)

●NScha08hpeibdns0a.ams.hpecore.net2026-05-01 → 2026-06-08 · 3 obs

○ 2026-04-21 19:37:44
● 2026-05-01 09:49:54
● 2026-06-08 02:21:10

○NSdns1.registrar-servers.com2016-12-17 → 2017-09-06 · 4 obs

● 2016-12-17 13:42:02
● 2017-09-06 11:51:00
○ 2026-02-25 10:35:28
○ 2026-06-08 02:21:10

○NSdns2.registrar-servers.com2016-12-17 → 2017-09-06 · 4 obs

● 2016-12-17 13:42:02
● 2017-09-06 11:51:00
○ 2026-02-25 10:35:28
○ 2026-06-08 02:21:10

○NSextns01.juniper.net2026-02-25 → 2026-04-21 · 5 obs

○ 2017-09-06 11:51:00
● 2026-02-25 10:35:28
● 2026-04-21 19:37:44
○ 2026-05-01 09:49:54
○ 2026-06-08 02:21:10

●NSns1.hpe.com2026-05-01 → 2026-06-08 · 3 obs

○ 2026-04-21 19:37:44
● 2026-05-01 09:49:54
● 2026-06-08 02:21:10

○NSns18.ultradns2.com2026-02-25 → 2026-04-21 · 5 obs

○ 2017-09-06 11:51:00
● 2026-02-25 10:35:28
● 2026-04-21 19:37:44
○ 2026-05-01 09:49:54
○ 2026-06-08 02:21:10

○NSns18.ultradns2.org2026-02-25 → 2026-04-21 · 5 obs

○ 2017-09-06 11:51:00
● 2026-02-25 10:35:28
● 2026-04-21 19:37:44
○ 2026-05-01 09:49:54
○ 2026-06-08 02:21:10

●NSns2.hpe.com2026-05-01 → 2026-06-08 · 3 obs

○ 2026-04-21 19:37:44
● 2026-05-01 09:49:54
● 2026-06-08 02:21:10

●NSns3.hpe.com2026-05-01 → 2026-06-08 · 3 obs

○ 2026-04-21 19:37:44
● 2026-05-01 09:49:54
● 2026-06-08 02:21:10

●NSns4.hpe.com2026-05-01 → 2026-06-08 · 3 obs

○ 2026-04-21 19:37:44
● 2026-05-01 09:49:54
● 2026-06-08 02:21:10

●NSns5.hpe.com2026-05-01 → 2026-06-08 · 3 obs

○ 2026-04-21 19:37:44
● 2026-05-01 09:49:54
● 2026-06-08 02:21:10

●NSns6.hpe.com2026-05-01 → 2026-06-08 · 3 obs

○ 2026-04-21 19:37:44
● 2026-05-01 09:49:54
● 2026-06-08 02:21:10

●NSns7.hpe.com2026-05-01 → 2026-06-08 · 3 obs

○ 2026-04-21 19:37:44
● 2026-05-01 09:49:54
● 2026-06-08 02:21:10

●NSns8.hpe.com2026-05-01 → 2026-06-08 · 3 obs

○ 2026-04-21 19:37:44
● 2026-05-01 09:49:54
● 2026-06-08 02:21:10

○NSpdns1.ultradns.net2026-02-25 → 2026-04-21 · 5 obs

○ 2017-09-06 11:51:00
● 2026-02-25 10:35:28
● 2026-04-21 19:37:44
○ 2026-05-01 09:49:54
○ 2026-06-08 02:21:10

○NSpdns2.ultradns.net2026-02-25 → 2026-04-21 · 5 obs

○ 2017-09-06 11:51:00
● 2026-02-25 10:35:28
● 2026-04-21 19:37:44
○ 2026-05-01 09:49:54
○ 2026-06-08 02:21:10

○NSpdns3.ultradns.org2026-02-25 → 2026-04-21 · 5 obs

○ 2017-09-06 11:51:00
● 2026-02-25 10:35:28
● 2026-04-21 19:37:44
○ 2026-05-01 09:49:54
○ 2026-06-08 02:21:10

○NSpdns4.ultradns.org2026-02-25 → 2026-04-21 · 5 obs

○ 2017-09-06 11:51:00
● 2026-02-25 10:35:28
● 2026-04-21 19:37:44
○ 2026-05-01 09:49:54
○ 2026-06-08 02:21:10

○NSpdns5.ultradns.info2026-02-25 → 2026-04-21 · 5 obs

○ 2017-09-06 11:51:00
● 2026-02-25 10:35:28
● 2026-04-21 19:37:44
○ 2026-05-01 09:49:54
○ 2026-06-08 02:21:10

○NSpdns6.ultradns.co.uk2026-02-25 → 2026-04-21 · 5 obs

○ 2017-09-06 11:51:00
● 2026-02-25 10:35:28
● 2026-04-21 19:37:44
○ 2026-05-01 09:49:54
○ 2026-06-08 02:21:10

○NSudns1.ultradns.net2026-02-25 → 2026-04-21 · 5 obs

○ 2017-09-06 11:51:00
● 2026-02-25 10:35:28
● 2026-04-21 19:37:44
○ 2026-05-01 09:49:54
○ 2026-06-08 02:21:10

○NSudns2.ultradns.net2026-02-25 → 2026-04-21 · 5 obs

○ 2017-09-06 11:51:00
● 2026-02-25 10:35:28
● 2026-04-21 19:37:44
○ 2026-05-01 09:49:54
○ 2026-06-08 02:21:10

●MXalt1.aspmx.l.google.com2016-12-17 → 2026-06-08 · 2 obs

● 2016-12-17 13:42:02
● 2026-06-08 02:21:10

●MXalt2.aspmx.l.google.com2016-12-17 → 2026-06-08 · 2 obs

● 2016-12-17 13:42:02
● 2026-06-08 02:21:10

●MXalt3.aspmx.l.google.com2017-09-06 → 2026-06-08 · 3 obs

○ 2016-12-17 13:42:02
● 2017-09-06 11:51:00
● 2026-06-08 02:21:10

●MXalt4.aspmx.l.google.com2017-09-06 → 2026-06-08 · 3 obs

○ 2016-12-17 13:42:02
● 2017-09-06 11:51:00
● 2026-06-08 02:21:10

●MXaspmx.l.google.com2016-12-17 → 2026-06-08 · 2 obs

● 2016-12-17 13:42:02
● 2026-06-08 02:21:10

○MXaspmx2.googlemail.com2016-12-17 → 2016-12-17 · 3 obs

● 2016-12-17 13:42:02
○ 2017-09-06 11:51:00
○ 2026-06-08 02:21:10

○MXaspmx3.googlemail.com2016-12-17 → 2016-12-17 · 3 obs

● 2016-12-17 13:42:02
○ 2017-09-06 11:51:00
○ 2026-06-08 02:21:10

○A162.255.119.2492016-12-17 → 2016-12-17 · 3 obs

● 2016-12-17 13:42:02
○ 2017-09-06 11:51:00
○ 2026-06-08 02:21:10

○A35.185.239.1522017-09-06 → 2017-09-06 · 4 obs

○ 2016-12-17 13:42:02
● 2017-09-06 11:51:00
○ 2026-02-25 10:35:28
○ 2026-06-08 02:21:10

●A44.224.71.2522026-02-25 → 2026-06-08 · 3 obs

○ 2017-09-06 11:51:00
● 2026-02-25 10:35:28
● 2026-06-08 02:21:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
128technology.com	ns3.hpe.com, ns1.hpe.com, ns2.hpe.com, ns4.hpe.com...	8 records

✅ Authoritative Response

Server:192.58.207.221

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 128technology.com (unsigned zone)

⏱️ Timing

Total: 723ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`44.224.71.252`
NS	8	`ns6.hpe.com, ns8.hpe.com...`
MX	5	`alt3.aspmx.l.google.com (pri: 10), alt4.aspmx.l.google.com (pri: 10)...`
TXT	11	`MS=ms46595271, atlassian-domain-verification=e1c-4btnZb...`
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

Hierarchy

response.128technology.com, www.128technology.com and yum.128technology.com are all subdomains of 128technology.com.

IP Addresses

128technology.com has exactly one IP address — 44.224.71.252.

metafabric.net, rss.juniper.net, www.netscreen.com plus two other host names have IP numbers in common with 128technology.com.

Name Servers

128technology.com has 9 name servers handling its delegation — ns1.hpe.com, ns2.hpe.com, ns3.hpe.com and six others.

The name servers of 128technology.com overlap at least partially with those of other domains — among them hpecloud.eu, hpeappup.com, hpe.lt and two more.

It is common to see these name servers paired with name servers ns4.hpe.com, ns5.hpe.com and ns6.hpe.com plus three others.

Host names with one IP number:

ns1.hpe.com points to 192.58.206.184.

ns2.hpe.com points to 192.58.207.221.

ns3.hpe.com points to 16.2.141.20.

ns4.hpe.com points to 16.2.138.125.

ns5.hpe.com points to 192.58.206.184.

ns6.hpe.com points to 192.58.207.221.

ns7.hpe.com points to 16.2.141.21.

ns8.hpe.com points to 16.2.138.125.

cha08hpeibdns0a.ams.hpecore.net points to 10.78.58.213.

ns1.hpe.com and ns5.hpe.com are host names that each point to 192.58.206.184 IP addresses.

ns2.hpe.com and ns6.hpe.com are host names that each point to 192.58.207.221 IP addresses.

ns4.hpe.com and ns8.hpe.com are host names that each point to 16.2.138.125 IP addresses.

Mail Servers

Mail for 128technology.com is routed through 5 mail servers, including aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

At least some of the mail servers used by 128technology.com are shared with other domains: ns500754.ns500754.ns500754.ns500671.ns500705.ns500704.ns500671.ns500291.ns500291.ns500131.lustychickser.com, ns500671.ns500671.ns500731.ns500742.ns500731.ns500704.ns500731.ns500688.ns500705.ns500705.ns500291.ns500649.ns500291.ns500291.ns500131.lustychickser.com, ns500754.ns500754.ns500754.ns500754.ns500742.ns500671.ns500704.ns500671.ns500671.ns500671.ns500649.ns500649.lustychickser.com and two others among them.

It is common for these mail servers to be used in conjunction with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com and aspmx3.googlemail.com, plus three others.

Host names pointing to two IP addresses:

aspmx.l.google.com points to 142.251.111.27 and 2607:f8b0:4004:c17::1b.

alt1.aspmx.l.google.com points to 108.177.123.26 and 2800:3f0:4003:c0f::1b.

alt2.aspmx.l.google.com points to 172.253.116.27 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com points to 192.178.223.26 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com points to 173.194.76.27 and 2a00:1450:400c:c00::1a.