CF1757292410051-tsm20250907181809

NSLIST.NET - tcp.network

Search for IP or hostnames:

tcp.network checked at 2025-09-08T00:46:50.035Z 115ms 57/57/57 100% R:12

tcp.network

NSns39.domaincontrol.com
A2603:5:21d1::14 🇺🇸 GODADDY-DNS
PTRns39.domaincontrol.com
A97.74.109.20🇺🇸 GODADDY-DNS
PTRns39.domaincontrol.com
NSns40.domaincontrol.com
A2603:5:22d1::14 🇺🇸 GODADDY-DNS
PTRns40.domaincontrol.com
A173.201.77.20🇺🇸 GODADDY-DNS
PTRns40.domaincontrol.com
A3.33.251.168🇺🇸 Amazon
PTRaec037177372cc6cd.awsglobalaccelerator.com
A15.197.225.128🇺🇸 Amazon
PTRaec037177372cc6cd.awsglobalaccelerator.com

network

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

AI analysis

tcp.network is configured to point to two IP addresses: 3.33.251.168 and 15.197.225.128.

IP numbers are shared between tcp.network and other host names such as bradtobin.com, chestercountyseptic.com, shadowfactory.io, texparis.com, and bcrings.com.

Two name servers, ns39.domaincontrol.com and ns40.domaincontrol.com, have been delegated to tcp.network.

The name server setup of tcp.network is identical to that of other domains such as sweaterjacketorcoat.com, goarmysof.com, sidandshuby.com, 4223shelterbay.com, and passivesolar.tips.

ns39.domaincontrol.com and ns40.domaincontrol.com both point to two IP numbers each: 2603:5:21d1::14, 97.74.109.20 for ns39.domaincontrol.com and 2603:5:22d1::14, 173.201.77.20 for ns40.domaincontrol.com.

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

wLPXGdp CF johedugfp 2025-09-08