CF1757279201154-tsm20250907181809

DNSWHOIS.INFO - ssh.tokyo

Search for IP or hostnames:

ssh.tokyo checked at 2025-09-07T21:06:41.136Z 261ms 103/103/103 100% R:11

`ssh.tokyo`

	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`
	NS	`ns1.messagingengine.com`
			A	162.159.24.178^Cloudflare
				PTR	`ns1.messagingengine.com`
	NS	`ns2.messagingengine.com`
			A	162.159.25.191^Cloudflare
				PTR	`ns2.messagingengine.com`
	A	103.168.172.37^{🇺🇸 Cloudflare London}
			PTR	`userweb.fastmail.com`
	A	103.168.172.52^{🇺🇸 Cloudflare London}
			PTR	`userweb.fastmail.com`

`tokyo`

	NS	`a.gmoregistry.net`
	NS	`b.gmoregistry.net`
	NS	`k.gmoregistry.net`
	NS	`l.gmoregistry.net`

Starts with same word
`ssh.kiev.ua`
`ssh.fi`
`ssh.network`
`ssh.vn`
`ssh.co.in`
`ssh.es`
`ssh.com`
`ssh.se`
`ssh.pl`
`ssh.cat`
`ssh.org`
`ssh.ink`
`ssh.tc`
`ssh.tokyo`
`ssh.engineering`
`ssh.edu`
`ssh.rocks`
`ssh.moe`
`ssh.cz`
`ssh.wtf`
`ssh.today`
`ssh.at`
`ssh.blue`
`ssh.org.sg`
`ssh.hu`
`ssh.guru`
`ssh.dz`
`ssh.in`
`ssh.chat`
`ssh.us`
`ssh.rs`
`ssh.dk`
`ssh.is`
`ssh.tw`
`ssh.it`
`ssh.info`
`ssh.run`
`ssh.net`
`ssh.ma`
`ssh.monster`
`ssh.be`
`ssh.contact`
`ssh.ch`
`ssh.su`
`ssh.to`
`ssh.yt`
`ssh.fail`
`ssh.web.id`
`ssh.ru`
`ssh.zone`
`ssh.lu`
`ssh.kz`
`ssh.biz`
`ssh.if.ua`
`ssh.me`
`ssh.bz`
`ssh.co.uk`
`ssh.no`
`ssh.co.kr`
`ssh.sh`
`ssh.im`
`ssh.cx`
`ssh.nu`
`ssh.tv`
`ssh.ninja`
`ssh.co`
`ssh.in.ua`
`ssh.fr`
`ssh.com.cn`
`ssh.gob.mx`
`ssh.lv`
`ssh.center`
`ssh.fo`
`ssh.de`
`ssh.io`
`ssh.nl`
`ssh.ac`
`ssh.tf`

Starts similarily
`shs.net`
`hss.cz`
`shs.k12.ny.us`
`ssh.hu`
`hss.fi`
`hss.ge`
`hss.sakura.ne.jp`
`shs.support`
`hss.edu.tw`
`hss.asia`
`shs.ch`
`hss.rs`
`shs.org`
`ssh.guru`
`ssh.dz`
`shs.net.tw`
`shs.me`
`ssh.in`
`hss.gb.net`
`ssh.chat`
`ssh.us`
`shs.pt`
`ssh.rs`
`ssh.dk`
`shs.fr`
`ssh.is`
`ssh.tw`
`shs.co.kr`
`ssh.it`
`shs.gov.hk`
`hss.be`
`hss.ee`
`ssh.info`
`ssh.run`
`ssh.net`
`shs.kiev.ua`
`hss.cl`
`hss.is`
`ssh.ma`
`ssh.monster`
`shs.ro`
`ssh.be`
`hss.center`
`ssh.contact`
`ssh.ch`
`hss.ro`
`hss.co`
`hss.no`
`ssh.su`
`shs.hu`
`shs.lu`
`ssh.to`
`shs.vn`
`ssh.yt`
`hss.im`
`shs.co.id`
`ssh.fail`
`hss.ie`
`shs.ca`
`hss.ru`
`ssh.web.id`
`ssh.ru`
`shs.li`
`hss.nl`
`ssh.zone`
`hss.eu`
`ssh.lu`
`ssh.kz`
`shs.cc`
`hss.jpn.com`
`shs.by`
`ssh.biz`
`ssh.if.ua`
`shs.at`
`hss.it`
`shs.nu`
`hss.systems`
`hss.de`
`ssh.me`
`hss.biz`
`hss.co.in`
`ssh.bz`
`shs.co.nz`
`hss.cn`
`ssh.co.uk`
`shs.eu`
`hss.lu`
`ssh.no`
`ssh.co.kr`
`ssh.sh`
`hss.co.uk`
`shs.no`
`ssh.im`
`shs.info`
`hss.io`
`hss.net`
`ssh.cx`
`hss.ca`
`shs.edu.tw`
`ssh.nu`
`hss.org.hk`
`ssh.tv`
`hss.com.au`
`ssh.ninja`
`ssh.co`

AI analysis

ssh.tokyo is configured to point to two IP addresses, namely 103.168.172.37 and 103.168.172.52.

IP numbers are shared between ssh.tokyo and other host names such as goeij.eu, polzleitner.net, animecon.org.uk, neilfoley.net, and xmds.net.

Two name servers, ns1.messagingengine.com and ns2.messagingengine.com, are the delegation for ssh.tokyo.

The name server setup of ssh.tokyo is shared with other domains such as foinet.org, writequit.org, kaluza.eu, shanessite.net, and ice9.ca.

ns1.messagingengine.com and ns2.messagingengine.com both point to individual IP numbers: 162.159.24.178 and 162.159.25.191 respectively.

Two mail servers, in1-smtp.messagingengine.com and in2-smtp.messagingengine.com, manage ssh.tokyo.

Just like other domains such as utku.io, overcast.fm, ns1.ph4te.net, mdiadvantage.net, and celfs.com, ssh.tokyo also has the same mail server setup.

in1-smtp.messagingengine.com points 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. Meanwhile, in2-smtp.messagingengine.com points to two IP numbers: 202.12.124.216 and 202.12.124.217.

dbq

ltzEBIQ CF johedugfp 2025-09-07