WWW.RTSAK.COM - steven.ai

Search for IP or hostnames:

steven.ai checked at 2025-09-07T06:54:52.548Z 230ms 137/137/137 100% R:14

`steven.ai`

NS	`ns-cloud-c1.googledomains.com`
		A	2001:4860:4802:32::6c ^{🇺🇸 Google}
			PTR	`ns-cloud-c1.googledomains.com`
		A	216.239.32.108^{🇺🇸 Google}
			PTR	`ns-cloud-c1.googledomains.com`
NS	`ns-cloud-c2.googledomains.com`
		A	2001:4860:4802:34::6c ^{🇺🇸 Google}
			PTR	`ns-cloud-c2.googledomains.com`
		A	216.239.34.108^{🇺🇸 Google}
			PTR	`ns-cloud-c2.googledomains.com`
NS	`ns-cloud-c3.googledomains.com`
		A	2001:4860:4802:36::6c ^{🇺🇸 Google}
			PTR	`ns-cloud-c3.googledomains.com`
		A	216.239.36.108^{🇺🇸 Google}
			PTR	`ns-cloud-c3.googledomains.com`
NS	`ns-cloud-c4.googledomains.com`
		A	2001:4860:4802:38::6c ^{🇺🇸 Google}
			PTR	`ns-cloud-c4.googledomains.com`
		A	216.239.38.108^{🇺🇸 Google}
			PTR	`ns-cloud-c4.googledomains.com`
MX	`in1-smtp.messagingengine.com`
		A	103.168.172.216^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-01.messagingengine.com`
		A	103.168.172.217^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-02.messagingengine.com`
		A	103.168.172.218^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-03.messagingengine.com`
		A	103.168.172.219^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-04.messagingengine.com`
		A	103.168.172.220^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-05.messagingengine.com`
		A	103.168.172.221^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-06.messagingengine.com`
		A	103.168.172.222^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-07.messagingengine.com`
		A	103.168.172.223^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-08.messagingengine.com`
MX	`in2-smtp.messagingengine.com`
		A	202.12.124.216^AS5716
			PTR	`stl-mx-01.messagingengine.com`
		A	202.12.124.217^AS5716
			PTR	`stl-mx-02.messagingengine.com`
A	2400:6180:0:d0::e78:c001 ^{🇸🇬 DigitalOcean}
		PTR	`p1-do-sgp1.hau.li`
A	188.166.253.226^{🇸🇬 DigitalOcean}
		PTR	`p1-do-sgp1.hau.li`

`ai`

	NS	`v0n0.nic.ai`
	NS	`v0n1.nic.ai`
	NS	`v0n2.nic.ai`
	NS	`v0n3.nic.ai`
	NS	`v2n0.nic.ai`
	NS	`v2n1.nic.ai`

Starts with same word
`steven.ca`
`steven.us`
`steven.com`
`steven.network`
`steven.land`
`steven.solar`
`steven.io`
`steven.com.my`
`steven.moe`
`steven.co`
`steven.cool`
`steven.li`
`steven.it`
`steven.cc`
`steven.lu`
`steven.ai`
`steven.de`
`steven.co.nz`
`steven.no`
`steven.in`
`steven.mx`
`steven.eu`
`steven.ma`
`steven.su`
`steven.net`
`steven.pro`
`steven.cz`
`steven.tc`
`steven.ch`
`steven.at`
`steven.bio`
`steven.digital`

Starts similarily
`events.name`
`events.mk`
`ventes.co`
`nevest.com`
`vesten.com`
`steven.com`
`events.pm`
`events.solutions`
`envest.net`
`steven.network`
`evnets.net`
`events.my`
`events.org.il`
`steven.land`
`events.ph`
`steven.solar`
`events.com.fj`
`events.ie`
`events.co.at`
`events.mobi`
`vesent.com`
`sevent.at`
`steven.io`
`events.com`
`evsnet.com`
`steven.com.my`
`sevent.eu`
`steven.moe`
`events.ai`
`svenet.de`
`svente.com`
`envest.me`
`ventes.net`
`events.kz`
`events.ch`
`events.solar`
`events.cat`
`events.events`
`sevnet.com`
`sevent.net`
`vsenet.ru`
`sevent.tk`
`vesnet.org`
`tveens.com`
`steven.co`
`vsenet.org`
`sevent.fi`
`events.co.il`
`steven.cool`
`svente.lt`
`events.team`
`svente.de`
`ventes.si`
`events.com.mt`
`events.ac`
`tevens.com`
`vesten.be`
`events.gr`
`events.sh`
`steven.li`
`steven.it`
`steven.cc`
`sevent.com`
`events.us`
`venest.com`
`nevets.net`
`events.ooo`
`sevent.es`
`events.la`
`steven.lu`
`sevent.in`
`steven.ai`
`events.biz`
`netves.com`
`events.exchange`
`sentev.com`
`vetnes.com`
`tvseen.ws`
`events.life`
`envest.cn`
`events.no`
`envest.co`
`steven.de`
`events.sandvikcoromant`
`events.ma`
`events.at`
`vesnet.de`
`steven.co.nz`
`steven.no`
`ventes.rs`
`vesnet.no`
`envest.info`
`events.gov.ge`
`events.in.ua`
`events.lk`
`envest.de`
`nsteve.com`
`nevest.de`
`svenet.dk`
`tensev.com`

AI analysis

steven.ai is configured to point to two IP addresses, namely 2400:6180:0:d0::e78:c001 and 188.166.253.226.

IP numbers are shared between steven.ai and other host names such as rearmed.org, haulien.com, hau.li, stevensaric.com, and p1-do-sgp1.hau.li.

Four name servers, ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, and ns-cloud-c4.googledomains.com, are delegated to steven.ai.

The name servers of steven.ai are at least partially shared with other domains such as howdysam.com, tatay.technology, cliosilks.com, sealmess.com, and patrizi.biz.

The name servers ns-127.awsdns-15.com, ns-664.awsdns-19.net, ns-1424.awsdns-50.org, and ns-1660.awsdns-15.co.uk are typically utilized in conjunction.

ns-cloud-c1.googledomains.com, 2001:4860:4802:32::6c, and 216.239.32.108 are associated in DNS.

ns-cloud-c2.googledomains.com, 2001:4860:4802:34::6c, and 216.239.34.108 are also connected in DNS.

ns-cloud-c3.googledomains.com, 2001:4860:4802:36::6c, and 216.239.36.108 point to each other in DNS.

ns-cloud-c4.googledomains.com, 2001:4860:4802:38::6c, and 216.239.38.108 are linked through DNS as well.

Two mail servers, in1-smtp.messagingengine.com and in2-smtp.messagingengine.com, manage steven.ai.

Just like other domains such as osd.se, creditrank.co, guelink.de, croteaugroup.com, and borgstrom.se, steven.ai also has the same mail server setup.

Some mail servers are at least partially shared by steven.ai with other domains such as amouage.io and toad.qma.com.au.

in1-smtp.messagingengine.com is assigned to the following eight IP numbers: 103.168.172.216, 103.168.172.217, 103.168.172.218, 103.168.172.219, 103.168.172.220, 103.168.172.221, 103.168.172.222, and 103.168.172.223. in2-smtp.messagingengine.com, on the other hand, resolves to two IP numbers: 202.12.124.216 and 202.12.124.217.

dbq