CF1762180594439-tsm20251102073205

MXLIST.NET - 195.232.173.in-addr.arpa

Search for IP or hostnames:

195.232.173.in-addr.arpa checked at 2025-11-03T14:36:34.423Z 218ms 84/84/84 100% R:12

195.232.173.in-addr.arpa

NSrdns1.serverhubdns.com
A23.231.52.92๐Ÿ‡บ๐Ÿ‡ธ Eonix N.A. Region
PTRrdns1.serverhubdns.com
NSrdns2.serverhubdns.com
A23.231.52.116๐Ÿ‡บ๐Ÿ‡ธ Eonix N.A. Region
PTRrdns2.serverhubdns.com
NSns3.he.net
A2001:470:300::2 ๐Ÿ‡บ๐Ÿ‡ธ HURRICANE
PTRns3.he.net
A216.218.132.2๐Ÿ‡บ๐Ÿ‡ธ HURRICANE
PTRns3.he.net
NSns2.afraid.org
A2001:1850:1:5:800::6b ๐Ÿ‡บ๐Ÿ‡ธ GigeNET
PTRns2.afraid.org
A69.65.50.223๐Ÿ‡บ๐Ÿ‡ธ GigeNET
PTRns2.afraid.org
MX195.232.173.in-addr.arpa
A173.232.195.1
A173.232.195.1

232.173.in-addr.arpa

NSrdns1.serverhubdns.com
NSrdns2.serverhubdns.com
MX232.173.in-addr.arpa
A173.232.0.0๐Ÿ‡บ๐Ÿ‡ธ Eonix N.A. Region

MX for

Up

Starts with same word

Starts similarily

AI analysis

195.232.173.in-addr.arpa is a parent of 189.195.232.173.in-addr.arpa and 137.195.232.173.in-addr.arpa.

For 195.232.173.in-addr.arpa, the mail server is 195.232.173.in-addr.arpa.

195.232.173.in-addr.arpa resolves to one IP number: 173.232.195.1.

195.232.173.in-addr.arpa is delegated to four name servers: rdns1.serverhubdns.com, rdns2.serverhubdns.com, ns3.he.net and ns2.afraid.org.

195.232.173.in-addr.arpa at least partially shares name servers with other domains, for instance stompy.net, led-downlight.com, 176.91.213.in-addr.arpa, 160.160.23.in-addr.arpa and magicmayhem.com.

These name servers are commonly used alongside ns2.he.net, ns4.he.net, ns5.he.net, ns1.he.net, ns1.afraid.org, ns3.afraid.org and ns4.afraid.org.

Host names with two IP numbers:

ns3.he.net points to 2001:470:300::2 and 216.218.132.2; ns2.afraid.org points to 2001:1850:1:5:800::6b and 69.65.50.223.

Host names with one IP number:

rdns1.serverhubdns.com points to 23.231.52.92; rdns2.serverhubdns.com points to 23.231.52.116.

195.232.173.in-addr.arpa is served by a single mail server, 195.232.173.in-addr.arpa.

195.232.173.in-addr.arpa resolves to IP 173.232.195.1.

Perform reverse DNS lookup as well as normal forward DNS. Check Autonomous System Numbers (ASNs) and BGP connections between Internet Service Providers.
dbq

sCKqHGa CF johedugfp 2025-11-03