DNSWHOIS.INFO - t-f.pw

Search for IP or hostnames:

t-f.pw checked at 2025-09-07T01:27:25.539Z 152ms 139/139/139 100% R:12

`t-f.pw`

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	`max.ns.cloudflare.com`
		A	2606:4700:58::adf5:3b84 ^{🇺🇸 Cloudflare}
			PTR	`max.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c184 ^{🇨🇷 Cloudflare}
			PTR	`max.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2184 ^{🇺🇸 Cloudflare}
			PTR	`max.ns.cloudflare.com`
		A	108.162.193.132^{🇺🇸 Cloudflare}
			PTR	`max.ns.cloudflare.com`
		A	172.64.33.132^{🇺🇸 Cloudflare}
			PTR	`max.ns.cloudflare.com`
		A	173.245.59.132^{🇺🇸 Cloudflare}
			PTR	`max.ns.cloudflare.com`
NS	`vera.ns.cloudflare.com`
		A	2606:4700:50::adf5:3a93 ^{🇺🇸 Cloudflare}
			PTR	`vera.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c093 ^{🇨🇷 Cloudflare}
			PTR	`vera.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2093 ^{🇺🇸 Cloudflare}
			PTR	`vera.ns.cloudflare.com`
		A	108.162.192.147^{🇺🇸 Cloudflare}
			PTR	`vera.ns.cloudflare.com`
		A	172.64.32.147^{🇺🇸 Cloudflare}
			PTR	`vera.ns.cloudflare.com`
		A	173.245.58.147^{🇺🇸 Cloudflare}
			PTR	`vera.ns.cloudflare.com`

`pw`

	NS	`ns1.nic.pw`
	NS	`ns2.nic.pw`
	NS	`ns5.nic.pw`
	NS	`ns6.nic.pw`

Up
`www.t-f.pw`
`lampone.t-f.pw`

Starts with same word
`t-f.eu`
`t-f.pw`
`t-f.com.tw`
`t-f.jp`
`t-f.co.uk`
`t-f.ddns.net`
`t-f.co.jp`
`t-f.ru`
`t-f.de`

Starts similarily
`f-t.com`
`f-t.co.jp`
`f-t.pl`
`f-t.xyz`
`f-t.biz`
`f-t.cn`
`f-t.tw`
`f-t.win`
`t-f.pw`
`f-t.co.il`
`t-f.com.tw`
`t-f.jp`
`f-t.co.kr`
`f-t.net`
`t-f.co.uk`
`t-f.ddns.net`
`t-f.co.jp`
`f-t.de`
`t-f.ru`
`f-t.sakura.ne.jp`
`f-t.co`
`f-t.nl`
`t-f.de`
`f-t.ru`
`f-t.com.au`
`t-f.eu`
`f-t.jp`

AI analysis

The parent of www.t-f.pw and lampone.t-f.pw is t-f.pw.

Two name servers, max.ns.cloudflare.com and vera.ns.cloudflare.com, are delegated to t-f.pw.

The name server setup for t-f.pw is shared with several other domains such as olympusrail.com, soft-lux.com, loudcanvas.net, hermitagegolfclub.com, and demanko.com.

The domain t-f.pw shares name servers, at least partially, with other domains such as e-mnet.cn, aniasafelearning.it, australiancollege.edu.au, victorbordo.com, and layer8.io.

The name servers elisa.ns.cloudflare.com are frequently utilized in conjunction.

max.ns.cloudflare.com and vera.ns.cloudflare.com both point to six IP numbers each: 2606:4700:58::adf5:3b84, 2803:f800:50::6ca2:c184, 2a06:98c1:50::ac40:2184, 108.162.193.132, 172.64.33.132, 173.245.59.132 for max.ns.cloudflare.com and 2606:4700:50::adf5:3a93, 2803:f800:50::6ca2:c093, 2a06:98c1:50::ac40:2093, 108.162.192.147, 172.64.32.147, 173.245.58.147 for vera.ns.cloudflare.com.

Two mail servers, in1-smtp.messagingengine.com and in2-smtp.messagingengine.com, are responsible for handling t-f.pw.

Like domains pinky.elexer.com, mail.reavey05.net, viper.dk, rsol.ca, and xleml.com, t-f.pw also has the same mail server setup.

Some mail servers are at least partially shared by t-f.pw with other domains such as cal.io and yangmeyer.de.

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

dbq