NSLIST.NET - threatstack.io

Search for IP or hostnames:

threatstack.io checked at 2025-10-01T09:02:53.954Z 357ms 71/71/71 100% R:16

`threatstack.io`

NS	`ns1.threatstack.io`
		A	2400:cb00:2049:1::a29f:be ^{🇺🇸 Cloudflare}
		A	162.159.0.190^Cloudflare
NS	`ns2.threatstack.io`
		A	2400:cb00:2049:1::a29f:1be ^{🇺🇸 Cloudflare}
		A	162.159.1.190^Cloudflare
MX	`mx1.hc5801-97.iphmx.com`
		A	68.232.154.38^{🇺🇸 HPS // Cisco Cloud Email Security (CES) / IronPort}
		A	139.138.58.65^{🇺🇸 HPS // Cisco Cloud Email Security (CES) / IronPort}
MX	`mx2.hc5801-97.iphmx.com`
		A	68.232.154.38^{🇺🇸 HPS // Cisco Cloud Email Security (CES) / IronPort}
		A	139.138.58.65^{🇺🇸 HPS // Cisco Cloud Email Security (CES) / IronPort}

`io`

	NS	`a0.nic.io`
	NS	`a2.nic.io`
	NS	`b0.nic.io`
	NS	`c0.nic.io`

Up

ns1.threatstack.io

ns2.threatstack.io

Starts with same word

threatstack.net

threatstack.com

threatstack.io

threatstack.co

Starts similarily

threatstack.com

threatstack.io

threatstack.co

theartstack.com

threatstack.net

AI analysis

threatstack.io is a parent of ns1.threatstack.io and ns2.threatstack.io.

threatstack.io is delegated to two name servers: ns1.threatstack.io and ns2.threatstack.io.

Host names with two IP numbers: ns1.threatstack.io points to: 2400:cb00:2049:1::a29f:be and 162.159.0.190; ns2.threatstack.io points to: 2400:cb00:2049:1::a29f:1be and 162.159.1.190.

threatstack.io is handled by two mail servers: mx1.hc5801-97.iphmx.com and mx2.hc5801-97.iphmx.com.

The mail server setup for threatstack.io matches that of other domains, for instance leaksignal.com, f5networks.net, acorus.net, acorus-networks.com and heyhack.com.

Host names with two IP numbers:

mx1.hc5801-97.iphmx.com points to 68.232.154.38 and 139.138.58.65.

mx2.hc5801-97.iphmx.com points to 68.232.154.38 and 139.138.58.65.

Host names pointing to 68.232.154.38: mx1.hc5801-97.iphmx.com and mx2.hc5801-97.iphmx.com.

Host names pointing to 139.138.58.65: mx1.hc5801-97.iphmx.com and mx2.hc5801-97.iphmx.com.

dbq