DNSWHOIS.INFO - imperative.systems

Search for IP or hostnames:

imperative.systems checked at 2025-11-05T10:40:35.105Z 253ms 131/131/131 100% R:13

`imperative.systems`

NS	`ns-351.awsdns-43.com`
		A	2600:9000:5301:5f00::1 ^{🇺🇸 Amazon}
			PTR	`ns-351.awsdns-43.com`
		A	205.251.193.95^{🇺🇸 Amazon}
			PTR	`ns-351.awsdns-43.com`
NS	`ns-542.awsdns-03.net`
		A	2600:9000:5302:1e00::1 ^{🇺🇸 Amazon}
			PTR	`ns-542.awsdns-03.net`
		A	205.251.194.30^{🇺🇸 Amazon}
			PTR	`ns-542.awsdns-03.net`
NS	`ns-1123.awsdns-12.org`
		A	2600:9000:5304:6300::1 ^{🇺🇸 Amazon}
			PTR	`ns-1123.awsdns-12.org`
		A	205.251.196.99^{🇺🇸 Amazon}
			PTR	`ns-1123.awsdns-12.org`
NS	`ns-1971.awsdns-54.co.uk`
		A	2600:9000:5307:b300::1 ^{🇺🇸 Amazon}
			PTR	`ns-1971.awsdns-54.co.uk`
		A	205.251.199.179^{🇺🇸 Amazon}
			PTR	`ns-1971.awsdns-54.co.uk`
MX	`imperative-systems.mail.protection.outlook.com`
		A	2a01:111:f403:c942:: ^{🇨🇦 Microsoft}
			PTR	`mail-yt5pr01cu00100.inbound.protection.outlook.com`
		A	2a01:111:f403:c942::2 ^{🇨🇦 Microsoft}
			PTR	`mail-yt3pr01cu00602.inbound.protection.outlook.com`
		A	2a01:111:f403:c942::3 ^{🇨🇦 Microsoft}
			PTR	`mail-yt6pr01cu00103.inbound.protection.outlook.com`
		A	2a01:111:f403:c944::1 ^{🇨🇦 Microsoft}
			PTR	`mail-yqzpr01cu01001.inbound.protection.outlook.com`
		A	52.101.190.0^{🇨🇦 Microsoft}
			PTR	`mail-yt5pr01cu00100.inbound.protection.outlook.com`
		A	52.101.190.2^{🇨🇦 Microsoft}
			PTR	`mail-yt3pr01cu00602.inbound.protection.outlook.com`
		A	52.101.190.3^{🇨🇦 Microsoft}
			PTR	`mail-yt6pr01cu00103.inbound.protection.outlook.com`
		A	52.101.192.1^{🇨🇦 Microsoft}
			PTR	`mail-yqzpr01cu01001.inbound.protection.outlook.com`
A	3.171.61.84^{🇺🇸 Amazon}
		PTR	`server-3-171-61-84.iad61.r.cloudfront.net`
A	3.171.61.92^{🇺🇸 Amazon}
		PTR	`server-3-171-61-92.iad61.r.cloudfront.net`
A	3.171.61.111^{🇺🇸 Amazon}
		PTR	`server-3-171-61-111.iad61.r.cloudfront.net`
A	3.171.61.117^{🇺🇸 Amazon}
		PTR	`server-3-171-61-117.iad61.r.cloudfront.net`

`systems`

	NS	`v0n0.nic.systems`
	NS	`v0n1.nic.systems`
	NS	`v0n2.nic.systems`
	NS	`v0n3.nic.systems`
	NS	`v2n0.nic.systems`
	NS	`v2n1.nic.systems`

Starts with same word

imperative.com.au

imperative.it

imperative.com

imperative.eu

imperative.in

imperative.company

imperative.de

imperative.net

imperative.systems

imperative.tv

Starts similarily

maperitive.net

imperative.it

imperative.com

imperative.eu

imperative.in

imperative.company

imperative.de

imperative.net

imperative.systems

imperative.tv

imperative.com.au

AI analysis

imperative.systems maps to four IP numbers: 3.171.61.84, 3.171.61.92, 3.171.61.111 and 3.171.61.117.

Other host names, for instance bloomen.net, innovations.co.nz, chesed-verachamim.co.il, d3116ivuxys4ep.cloudfront.net and sakkakeihan.amebaownd.com share IP numbers with imperative.systems.

imperative.systems's delegation is handled by four name servers: ns-351.awsdns-43.com, ns-542.awsdns-03.net, ns-1123.awsdns-12.org and ns-1971.awsdns-54.co.uk.

imperative.systems partially shares name servers with other domains; examples include d10paeq0uutuc0.cloudfront.net, maconomy.fr, runcfs.com, anticacapital.com and qsrsoft.com.

These name servers are commonly used with ns-815.awsdns-37.net, ns-1438.awsdns-51.org, ns-1541.awsdns-00.co.uk, ns-214.awsdns-26.com, ns-772.awsdns-32.net and ns-1554.awsdns-02.co.uk.

Host names with two IPs:

ns-351.awsdns-43.com points to 2600:9000:5301:5f00::1 and 205.251.193.95

ns-542.awsdns-03.net points to 2600:9000:5302:1e00::1 and 205.251.194.30

ns-1123.awsdns-12.org points to 2600:9000:5304:6300::1 and 205.251.196.99

ns-1971.awsdns-54.co.uk points to 2600:9000:5307:b300::1 and 205.251.199.179

imperative.systems is handled by a single mail server, imperative-systems.mail.protection.outlook.com.

Hostname imperative-systems.mail.protection.outlook.com points to eight IP numbers: 2a01:111:f403:c942::, 2a01:111:f403:c942::2, 2a01:111:f403:c942::3, 2a01:111:f403:c944::1, 52.101.190.0, 52.101.190.2, 52.101.190.3 and 52.101.192.1.

dbq