DNSWHOIS.INFO - idsignsystems.com

Search for IP or hostnames:

idsignsystems.com checked at 2025-09-06T11:00:01.327Z 581ms 139/139/139 100% R:11

`idsignsystems.com`

MX	`mx1-us1.ppe-hosted.com`
		A	67.231.154.162^{🇺🇸 Proofpoint}
			PTR	`mx1-us1.ppe-hosted.com`
		A	148.163.129.50^{🇺🇸 AS13916}
			PTR	`mx1-us1.ppe-hosted.com`
MX	`mx2-us1.ppe-hosted.com`
		A	67.231.154.163^{🇺🇸 Proofpoint}
			PTR	`mx2-us1.ppe-hosted.com`
		A	148.163.129.51^{🇺🇸 AS13916}
			PTR	`mx2-us1.ppe-hosted.com`
NS	`ns1.anchor.host`
		A	2600:180a:1001::1 ^{🇺🇸 Tiggee}
			PTR	`ns11.constellix.com`
		A	96.45.80.1^{🇺🇸 Tiggee}
			PTR	`ns11.constellix.com`
NS	`ns2.anchor.host`
		A	2600:180b:2001::1 ^{🇺🇸 Tiggee}
			PTR	`ns21.constellix.com`
		A	46.31.236.1^{🇺🇸 Tiggee}
			PTR	`ns21.constellix.com`
NS	`ns3.anchor.host`
		A	2600:180c:3001::1 ^{🇺🇸 Tiggee}
			PTR	`ns31.constellix.com`
		A	43.247.170.1^{🇯🇵 Tiggee}
			PTR	`ns31.constellix.com`
NS	`ns4.anchor.host`
		A	2600:180a:4001::1 ^{🇺🇸 Tiggee}
			PTR	`ns41.constellix.net`
		A	96.45.81.1^{🇺🇸 Tiggee}
			PTR	`ns41.constellix.net`
MX	`idsignsystems-com.mail.protection.outlook.com`
		A	2a01:111:f403:c801::1 ^{🇺🇸 Microsoft}
			PTR	`mail-sn1pr0501cu00101.inbound.protection.outlook.com`
		A	2a01:111:f403:f805:: ^{🇺🇸 Microsoft}
			PTR	`mail-mw2pr02cu00400.inbound.protection.outlook.com`
		A	2a01:111:f403:f901:: ^{🇺🇸 Microsoft}
			PTR	`mail-mn2pr04cu00200.inbound.protection.outlook.com`
		A	2a01:111:f403:f912:: ^{🇺🇸 Microsoft}
			PTR	`mail-cy5pr03cu00200.inbound.protection.outlook.com`
		A	52.101.9.26^{🇺🇸 Microsoft}
			PTR	`mail-bl0pr02cu00702.inbound.protection.outlook.com`
		A	52.101.11.2^{🇺🇸 Microsoft}
			PTR	`mail-sn1pr03cu00102.inbound.protection.outlook.com`
		A	52.101.41.24^{🇺🇸 Microsoft}
			PTR	`mail-sj0pr03cu01600.inbound.protection.outlook.com`
		A	52.101.194.13^{🇺🇸 Microsoft}
			PTR	`mail-ch0pr04cu00605.inbound.protection.outlook.com`
A	162.159.134.42^Cloudflare

`com`

	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`

Up
`mail.idsignsystems.com`

Starts with same word
`idsignsystems.com`

Starts similarily
`idsignsystems.com`

AI analysis

The parent of mail.idsignsystems.com is idsignsystems.com.

idsignsystems.com is associated with a single IP address: 162.159.134.42.

IP numbers are shared between idsignsystems.com and other host names such as tenfold-security.com, lions.tcnj.edu, drjenniferwalden.com, cos-mi.it, and teamtel.be.

Four name servers, ns1.anchor.host, ns2.anchor.host, ns3.anchor.host, and ns4.anchor.host, are assigned to idsignsystems.com.

The domain idsignsystems.com shares name servers, at least partially, with other domains such as leadershiplancaster.org, pitstopql.com, laralogan.us, ascendfab.com, and communityec.org.

ns1.anchor.host, ns2.anchor.host, ns3.anchor.host, and ns4.anchor.host all point to two IP numbers each: 2600:180a:1001::1 and 96.45.80.1, 2600:180b:2001::1 and 46.31.236.1, 2600:180c:3001::1 and 43.247.170.1, 2600:180a:4001::1 and 96.45.81.1 respectively.

Three mail servers, mx1-us1.ppe-hosted.com, mx2-us1.ppe-hosted.com, and idsignsystems-com.mail.protection.outlook.com, manage idsignsystems.com.

Some mail servers are at least partially shared between idsignsystems.com and other domains, such as tcwonline.com, gsrl.ca, ionicmail.com, burkese.com, and txwf.org.

mx1-us1.ppe-hosted.com, mx2-us1.ppe-hosted.com, and idsignsystems-com.mail.protection.outlook.com each point to multiple IP numbers. Specifically, mx1-us1.ppe-hosted.com points to 67.231.154.162 and 148.163.129.50, mx2-us1.ppe-hosted.com points to 67.231.154.163 and 148.163.129.51, and idsignsystems-com.mail.protection.outlook.com points to 2a01:111:f403:c801::1, 2a01:111:f403:f805::, 2a01:111:f403:f901::, 2a01:111:f403:f912::, 52.101.9.26, 52.101.11.2, 52.101.41.24, and 52.101.194.13.

dbq