WWW.ROBTEX.COM - routing.cafe

Search for IP or hostnames:

routing.cafe checked at 2025-09-11T09:18:06.977Z 414ms 194/194/194 100% R:22

`routing.cafe`

NS	`ns1.routing.cafe`
		A	2a14:14c0:1::^routing.cafe
			PTR	`core01.ams01.infra.routing.cafe`
		A	185.134.191.4^{🇸🇰 routing.cafe}
			PTR	`core01.ams01.infra.routing.cafe`
NS	`ns2.routing.cafe`
		A	2a14:14c0:2::^routing.cafe
			PTR	`edge01.ams02.infra.routing.cafe`
		A	185.134.191.8^{🇸🇰 routing.cafe}
			PTR	`edge01.ams02.infra.routing.cafe`
MX	`in1-smtp.messagingengine.com`
		A	103.168.172.216^{🇺🇸 FASTMAILPTYLTD-AS-AP}
			PTR	`phl-mx-01.messagingengine.com`
		A	103.168.172.217^{🇺🇸 FASTMAILPTYLTD-AS-AP}
			PTR	`phl-mx-02.messagingengine.com`
		A	103.168.172.218^{🇺🇸 FASTMAILPTYLTD-AS-AP}
			PTR	`phl-mx-03.messagingengine.com`
		A	103.168.172.219^{🇺🇸 FASTMAILPTYLTD-AS-AP}
			PTR	`phl-mx-04.messagingengine.com`
		A	103.168.172.220^{🇺🇸 FASTMAILPTYLTD-AS-AP}
			PTR	`phl-mx-05.messagingengine.com`
		A	103.168.172.221^{🇺🇸 FASTMAILPTYLTD-AS-AP}
			PTR	`phl-mx-06.messagingengine.com`
		A	103.168.172.222^{🇺🇸 FASTMAILPTYLTD-AS-AP}
			PTR	`phl-mx-07.messagingengine.com`
		A	103.168.172.223^{🇺🇸 FASTMAILPTYLTD-AS-AP}
			PTR	`phl-mx-08.messagingengine.com`
MX	`in2-smtp.messagingengine.com`
		A	202.12.124.216^{FASTMAILPTYLTD-AS-AP}
			PTR	`stl-mx-01.messagingengine.com`
		A	202.12.124.217^{FASTMAILPTYLTD-AS-AP}
			PTR	`stl-mx-02.messagingengine.com`
A	2a14:14c0:1::^routing.cafe
		PTR	`core01.ams01.infra.routing.cafe`
A	185.134.191.4^{🇸🇰 routing.cafe}
		PTR	`core01.ams01.infra.routing.cafe`

`cafe`

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

PTR for
`0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.c.4.1.4.1.a.2.ip6.arpa`
`0.24.26.94.in-addr.arpa`

Up
`ns2.routing.cafe`
`ns1.routing.cafe`

Starts with same word
`routing.cafe`
`routing.info`
`routing.fi`
`routing.rocks`
`routing.com.br`
`routing.co`
`routing.se`
`routing.academy`
`routing.us`
`routing.zone`
`routing.neustar`
`routing.me`
`routing.in`
`routing.center`
`routing.cl`
`routing.is`
`routing.expert`
`routing.pl`
`routing.ws`
`routing.dk`
`routing.solutions`
`routing.win`
`routing.be`
`routing.mx`
`routing.email`
`routing.co.uk`
`routing.cc`
`routing.net`
`routing.fail`
`routing.org`
`routing.ro`
`routing.hu`
`routing.name`
`routing.gr`
`routing.com`
`routing.sk`
`routing.ca`
`routing.company`
`routing.it`

Starts similarily
`touring.me`
`touring.mx`
`touring.com.pe`
`routing.ca`
`routing.company`
`nutrigo.pl`
`guitron.mx`
`nutrigo.cn`
`routing.it`
`touring.kz`
`touring.co.uk`
`gorunit.com`
`guritno.com`
`routing.cafe`
`oturing.com`
`routing.info`
`routing.fi`
`routing.rocks`
`routing.com.br`
`rongtui.com`
`ringout.net`
`touring.biz`
`touring.net`
`nutrigo.com.ar`
`routing.co`
`nutrigo.de`
`touring.pl`
`utoring.com`
`touring.be`
`routing.se`
`turingo.com`
`touring.com`
`routing.academy`
`touring.at`
`routing.us`
`touring.travel`
`routing.zone`
`intrugo.com`
`touring.no`
`touring.es`
`routing.neustar`
`routing.me`
`unitorg.ru`
`touring.lu`
`touring.in`
`touring.nl`
`utoring.ch`
`nutrigo.ro`
`routing.in`
`touring.cc`
`touring.ch`
`orgunit.com`
`touring.de`
`touring.si`
`ringout.fr`
`ruoting.com`
`routing.center`
`routing.cl`
`ruitong.com`
`routing.is`
`touring.pe`
`routing.expert`
`tingrou.net`
`touring.life`
`touring.bike`
`routing.pl`
`routing.ws`
`guitron.net`
`outgrin.com`
`routing.dk`
`touring.org`
`nutrigo.eu`
`touring.pt`
`routing.solutions`
`ringout.com`
`nutrigo.in`
`routing.win`
`touring.agency`
`orgnitu.com`
`routing.be`
`routing.mx`
`routing.email`
`nutrigo.ca`
`touring.co.in`
`tongrui.net`
`routing.co.uk`
`orgnitu.net`
`routing.cc`
`touring.us`
`guitron.com`
`touring.co.kr`
`routing.net`
`touring.co.nz`
`nurtigo.com`
`touring.ro`
`touring.sk`
`ruitong.com.cn`
`routing.fail`
`utoring.at`
`touring.dk`
`nutrigo.net`
`riotgun.com`
`turingo.eu`
`routing.org`
`touring.fi`
`routing.ro`
`touring.tv`
`routing.hu`
`ruoting.net`
`routing.name`
`rguinto.com`
`turnigo.com`
`routing.gr`
`nutrigo.com`
`touring.com.br`
`touring.se`
`nutrigo.co.za`
`touring.fr`
`routing.com`
`touring.by`
`routing.sk`

AI analysis

The parent of both ns2.routing.cafe and ns1.routing.cafe is routing.cafe.

routing.cafe is configured to point to two IP addresses: 2a14:14c0:1:: and 185.134.191.4.

The IP numbers of routing.cafe are also shared by other host names, specifically core01.ams01.infra.routing.cafe and ns1.routing.cafe.

Two name servers, ns1.routing.cafe and ns2.routing.cafe, are delegated by routing.cafe.

Other domains such as 24.26.94.in-addr.arpa and snek.lgbt use the same name server setup as routing.cafe.

ns1.routing.cafe and ns2.routing.cafe each point to two IP numbers: 2a14:14c0:1:: and 185.134.191.4, and 2a14:14c0:2:: and 185.134.191.8 respectively.

Two mail servers, in1-smtp.messagingengine.com and in2-smtp.messagingengine.com, handle routing.cafe.

Just like the domains carljm.net, mngeek.com, nathanbaxter.com, biesland.jules.nl, and xn--1xa.hoopycat.com, routing.cafe also has the same mail server setup.

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