CF1757120060132-tsm20250905231252

DNSWHOIS.INFO - relay.tel

Search for IP or hostnames:

relay.tel checked at 2025-09-06T00:54:20.100Z 183ms 106/106/106 100% R:12

`relay.tel`

	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`

`tel`

	NS	`anycast10.irondns.net`
	NS	`anycast23.irondns.net`
	NS	`anycast24.irondns.net`
	NS	`anycast9.irondns.net`

Starts with same word
`relay.gr`
`relay.kh.ua`
`relay.spb.su`
`relay.mx`
`relay.de`
`relay.nu`
`relay.to`
`relay.edu`
`relay.software`
`relay.delivery`
`relay.school`
`relay.nhs.uk`
`relay.ir`
`relay.dev`
`relay.co.ca`
`relay.nic.in`
`relay.tw`
`relay.com`
`relay.im`
`relay.su`
`relay.media`
`relay.lt`
`relay.org.tw`
`relay.fm`
`relay.ca`
`relay.kinghost.net`
`relay.kherson.ua`
`relay.do`
`relay.com.tw`
`relay.co.za`
`relay.ai`
`relay.co`
`relay.vc`
`relay.fi`
`relay.no`
`relay.es`
`relay.education`
`relay.tel`
`relay.email`
`relay.kharkov.ua`
`relay.academy`
`relay.video`
`relay.ro`
`relay.run`
`relay.spb.ru`
`relay.ie`
`relay.sumy.ua`
`relay.ks.ua`
`relay.net`
`relay.info`
`relay.net.ua`
`relay.expert`
`relay.us`
`relay.io`
`relay.ch`
`relay.graphics`
`relay.house`
`relay.km.ua`
`relay.nl`
`relay.com.br`
`relay.fr`
`relay.ac.lk`
`relay.company`
`relay.cz`
`relay.chat`
`relay.gy`
`relay.au`
`relay.at`
`relay.tv`
`relay.in`
`relay.lc`
`relay.dk`
`relay.team`
`relay.gl`
`relay.cv.ua`
`relay.org`
`relay.bz`

Starts similarily
`relya.com`
`ayrle.com`
`leary.cc`
`relay.do`
`eyral.com`
`yeral.com`
`relay.com.tw`
`relay.co.za`
`elyra.org`
`early.group`
`early.biz`
`relay.ai`
`leray.info`
`relay.co`
`ayrle.net`
`relay.vc`
`layer.cl`
`leray.biz`
`relay.fi`
`arley.co.uk`
`relay.no`
`leyar.com`
`relay.es`
`yeral.net`
`eylar.com`
`relay.education`
`elrya.com`
`leary.ru`
`lyrae.org`
`layer.co.uk`
`relay.tel`
`relay.email`
`layer.us`
`early.am`
`early.city`
`realy.nl`
`relay.kharkov.ua`
`early.co`
`relay.academy`
`early.academy`
`layer.guru`
`relay.video`
`alery.com`
`arely.de`
`layer.marketing`
`aleyr.com`
`layer.fr`
`leary.co.za`
`early.lc`
`yaler.co`
`relay.ro`
`relay.run`
`relay.spb.ru`
`alrey.com`
`relay.ie`
`relay.sumy.ua`
`layer.biz`
`relay.ks.ua`
`relay.net`
`ryale.com`
`layer.pro`
`relay.info`
`relay.net.ua`
`leary.email`
`elray.com`
`alery.fi`
`layer.ca`
`layer.ltd`
`layer.porn`
`eryla.org`
`relay.expert`
`layer.email`
`yaler.net`
`arely.cz`
`elray.de`
`relay.us`
`layer.gr`
`ylera.com`
`early.deals`
`arely.ro`
`layer.co.in`
`early.education`
`rayel.de`
`yelar.com`
`layer.team`
`elyar.co.uk`
`layer.com`
`leray.de`
`relay.io`
`relay.ch`
`relay.graphics`
`relay.house`
`lyrae.nl`
`early.be`
`layer.style`
`relay.km.ua`
`relay.nl`
`relay.com.br`
`layer.in`
`early.me`

AI analysis

relay.tel is configured to point to two IP addresses, namely 103.168.172.37 and 103.168.172.52.

IP numbers are shared between relay.tel and other host names such as coblog.tasha.co, andycheah.com, darkcloud.org, imap.fastmail.ca, and surfo.com.

Two name servers, ns1.messagingengine.com and ns2.messagingengine.com, are the delegation for relay.tel.

The name server setup of relay.tel is shared with other domains such as motemn.com, tobin.cc, 17n.me, brugts.net, and fates.org.

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 relay.tel.

Just like other domains such as hupix.net, icewindmud.org, whitetree.org, jentwo.org, and planetearthminecraft.fluctis.com, relay.tel also has the same mail server setup.

Other domains, such as rvmplatform.com, share at least some mail servers partially with relay.tel.

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

VmxoPYP CF johedugfp 2025-09-06