IPLIST.NET - whynetworks.com

Search for IP or hostnames:

whynetworks.com checked at 2025-10-10T03:12:25.897Z 154ms 86/86/86 100% R:13

`whynetworks.com`

NS	`ns0.directnic.com`
		A	2602:fc8e:0:688f:9::41 ^{🇺🇸 THEPRODUCERS}
		A	104.143.9.41^{🇺🇸 THEPRODUCERS}
NS	`ns1.directnic.com`
		A	2600:3c01::f03c:94ff:fe81:e767 ^{🇺🇸 Linode AS63949}
		A	23.239.4.33^{🇺🇸 Linode AS63949}
			PTR	`dnic-ns1.directnic.net`
NS	`ns2.directnic.com`
		A	2602:fc8e:0:688f:9::42 ^{🇺🇸 THEPRODUCERS}
		A	104.143.9.42^{🇺🇸 THEPRODUCERS}
NS	`ns3.directnic.com`
		A	2600:3c00::f03c:94ff:fe81:b947 ^{🇺🇸 Linode AS63949}
		A	45.33.11.85^{🇺🇸 Linode AS63949}
			PTR	`dnic-ns3.directnic.net`
MX	`df4791fbf6a64e8dfec0553c98fe3b.pamx1.hotmail.com`
		A	52.101.10.9^{🇺🇸 Microsoft}
		A	52.101.41.27^{🇺🇸 Microsoft}
		A	52.101.42.7^{🇺🇸 Microsoft}
		A	52.101.124.116^{🇯🇵 Microsoft}

whynetworks.com

whynetworks.com

whynetworks.com at least partially shares name servers with other domains, for instance xonux.com, usedprecor.com, spidercyclecity.com, pvasolutions.net and kareerpartners.org.

Host names with two IP numbers: ns0.directnic.com points to 2602:fc8e:0:688f:9::41 and 104.143.9.41; ns1.directnic.com points to 2600:3c01::f03c:94ff:fe81:e767 and 23.239.4.33; ns2.directnic.com points to 2602:fc8e:0:688f:9::42 and 104.143.9.42; ns3.directnic.com points to 2600:3c00::f03c:94ff:fe81:b947 and 45.33.11.85.

whynetworks.com is handled by a single mail server, df4791fbf6a64e8dfec0553c98fe3b.pamx1.hotmail.com.

dbq