CF1760749984564-tsm20251017082432

MXLIST.NET - tph.network

Search for IP or hostnames:

tph.network checked at 2025-10-18T01:13:04.548Z 188ms 61/61/61 100% R:13

tph.network

NSns1-06.azure-dns.com
A2603:1061:0:700::6 🇺🇸 Microsoft
PTRns1-06.azure-dns.com
A13.107.236.6🇺🇸 Microsoft
PTRns1-06.azure-dns.com
NSns4-06.azure-dns.info
A2620:1ec:bda:700::6 🇺🇸 Microsoft
PTRns4-06.azure-dns.info
A208.84.5.6🇺🇸 Microsoft
PTRns4-06.azure-dns.info
NSns2-06.azure-dns.net
A2620:1ec:8ec:700::6 🇺🇸 Microsoft
PTRns2-06.azure-dns.net
A150.171.21.6🇺🇸 Microsoft
PTRns2-06.azure-dns.net
NSns3-06.azure-dns.org
A2a01:111:4000:700::6 🇬🇧 Microsoft
PTRns3-06.azure-dns.org
A204.14.183.6🇺🇸 Microsoft
PTRns3-06.azure-dns.org

network

NSv0n0.nic.network
NSv0n1.nic.network
NSv0n2.nic.network
NSv0n3.nic.network
NSv2n0.nic.network
NSv2n1.nic.network

Starts with same word

Starts similarily

AI analysis

tph.network is delegated to four name servers: ns1-06.azure-dns.com, ns4-06.azure-dns.info, ns2-06.azure-dns.net and ns3-06.azure-dns.org.

At least part of the name servers for tph.network are shared with other domains, for instance 227.29.134.in-addr.arpa, stormid.net, caminomedical.org, hydro-contracting.co.uk and omegawatches.com.

Host names with two IP numbers:

ns1-06.azure-dns.com points to: 2603:1061:0:700::6 and 13.107.236.6

ns4-06.azure-dns.info points to: 2620:1ec:bda:700::6 and 208.84.5.6

ns2-06.azure-dns.net points to: 2620:1ec:8ec:700::6 and 150.171.21.6

ns3-06.azure-dns.org points to: 2a01:111:4000:700::6 and 204.14.183.6

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

pLtXIVo CF johedugfp 2025-10-18