CF1763777503152-tsm20251116095642

NSLIST.NET - transit.systems

Search for IP or hostnames:

transit.systems checked at 2025-11-22T02:11:43.090Z 609ms 57/57/57 100% R:9 allDone:true timedOut:false

transit.systems

NSlaunch1.spaceship.net
A2400:cb00:2049:1::a29f:1a26 🇺🇸 Cloudflare
A162.159.26.38 Cloudflare
NSlaunch2.spaceship.net
A2400:cb00:2049:1::a29f:1b20 🇺🇸 Cloudflare
A162.159.27.32 Cloudflare
A44.232.173.249🇺🇸 Amazon
PTRec2-44-232-173-249.us-west-2.compute.amazonaws.com
A52.40.42.113🇺🇸 Amazon
PTRec2-52-40-42-113.us-west-2.compute.amazonaws.com

systems

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

Starts with same word

Starts similarily

AI analysis

The entity transit.systems points to two IP numbers: 44.232.173.249 and 52.40.42.113.

For instance, other host names mobilemarket.com, insight-ai.com, uqrp.com, normalroasting.com and lhhz.com share IP numbers with transit.systems.

transit.systems is delegated to two name servers: launch1.spaceship.net and launch2.spaceship.net.

transit.systems uses the same name server setup as other domains such as bostonpartybus.info, mouse.asia, petnplay.com, tiendavirtual.co and dipped.xyz.

Host names with two IP numbers:

launch1.spaceship.net points to 2400:cb00:2049:1::a29f:1a26 and 162.159.26.38; launch2.spaceship.net points to 2400:cb00:2049:1::a29f:1b20 and 162.159.27.32.

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