CF1757548677640-tsm20250910161120

DNSWHOIS.INFO - 4.2.200.in-addr.arpa

Search for IP or hostnames:

4.2.200.in-addr.arpa checked at 2025-09-10T23:57:57.626Z 374ms 61/61/61 100% R:12

4.2.200.in-addr.arpa

NSns1-36.azure-dns.com
A2603:1061:0:10::24 🇺🇸 Microsoft
PTRns1-36.azure-dns.com
A150.171.10.36🇺🇸 Microsoft
PTRns1-36.azure-dns.com
NSns4-36.azure-dns.info
A2620:1ec:bda:10::24 🇺🇸 Microsoft
PTRns4-36.azure-dns.info
A13.107.206.36🇺🇸 Microsoft
PTRns4-36.azure-dns.info
NSns2-36.azure-dns.net
A2620:1ec:8ec:10::24 🇺🇸 Microsoft
PTRns2-36.azure-dns.net
A150.171.16.36🇺🇸 Microsoft
PTRns2-36.azure-dns.net
NSns3-36.azure-dns.org
A2a01:111:4000:10::24 🇬🇧 Microsoft
PTRns3-36.azure-dns.org
A13.107.222.36🇺🇸 Microsoft
PTRns3-36.azure-dns.org

2.200.in-addr.arpa

AI analysis

Four name servers, ns1-36.azure-dns.com, ns4-36.azure-dns.info, ns2-36.azure-dns.net, and ns3-36.azure-dns.org, are delegated to 4.2.200.in-addr.arpa.

The name servers of 4.2.200.in-addr.arpa are at least partially shared with other domains such as obsidian.net, 59.232.109.in-addr.arpa, mrandmrscow.com, seo.lu, and upnrhm.gov.in.

ns1-36.azure-dns.com, 2603:1061:0:10::24, and 150.171.10.36 are associated in DNS.

ns4-36.azure-dns.info, 2620:1ec:bda:10::24, and 13.107.206.36 are also connected in DNS.

ns2-36.azure-dns.net, 2620:1ec:8ec:10::24, and 150.171.16.36 point to each other in DNS.

ns3-36.azure-dns.org, 2a01:111:4000:10::24, and 13.107.222.36 are linked through DNS as well.

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

RmICCDd CF johedugfp 2025-09-10