WWW.RTSAK.COM - ffix.me

Search for IP or hostnames:

ffix.me checked at 2025-09-07T19:45:44.466Z 278ms 143/143/143 100% R:15

`ffix.me`

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	`ivy.ns.cloudflare.com`
		A	2606:4700:50::adf5:3a78 ^{🇺🇸 Cloudflare}
			PTR	`ivy.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c078 ^{🇨🇷 Cloudflare}
			PTR	`ivy.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2078 ^{🇺🇸 Cloudflare}
			PTR	`ivy.ns.cloudflare.com`
		A	108.162.192.120^{🇺🇸 Cloudflare}
			PTR	`ivy.ns.cloudflare.com`
		A	172.64.32.120^{🇺🇸 Cloudflare}
			PTR	`ivy.ns.cloudflare.com`
		A	173.245.58.120^{🇺🇸 Cloudflare}
			PTR	`ivy.ns.cloudflare.com`
NS	`jack.ns.cloudflare.com`
		A	2606:4700:58::adf5:3b79 ^{🇺🇸 Cloudflare}
			PTR	`jack.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c179 ^{🇨🇷 Cloudflare}
			PTR	`jack.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2179 ^{🇺🇸 Cloudflare}
			PTR	`jack.ns.cloudflare.com`
		A	108.162.193.121^{🇺🇸 Cloudflare}
			PTR	`jack.ns.cloudflare.com`
		A	172.64.33.121^{🇺🇸 Cloudflare}
			PTR	`jack.ns.cloudflare.com`
		A	173.245.59.121^{🇺🇸 Cloudflare}
			PTR	`jack.ns.cloudflare.com`
A	2a01:4f9:c013:52e8::1 ^{🇩🇪 Hetzner}
A	65.108.95.151^{🇫🇮 Hetzner}
		PTR	`static.151.95.108.65.clients.your-server.de`

`me`

	NS	`a0.nic.me`
	NS	`a2.nic.me`
	NS	`b0.nic.me`
	NS	`b2.nic.me`
	NS	`c0.nic.me`

Starts with same word
`ffix.info`
`ffix.de`
`ffix.me`
`ffix.com`
`ffix.ru`
`ffix.cn`

Starts similarily
`ffxi.at`
`ffxi.ru`
`ffix.info`
`ffxi.de`
`ffix.de`
`ifxf.com`
`ffxi.info`
`fifx.cn`
`xiff.net`
`ffix.me`
`fifx.com`
`ffix.com`
`ffxi.org`
`ffxi.net`
`fixf.co`
`ffix.ru`
`ffix.cn`
`ffxi.com`
`ffxi.ws`

AI analysis

ffix.me is configured to point to two IP addresses: 2a01:4f9:c013:52e8::1 and 65.108.95.151.

Two name servers, ivy.ns.cloudflare.com and jack.ns.cloudflare.com, are delegated to ffix.me.

The name server setup of ffix.me is shared with other domains such as jonmoniaci.com, money-central.net, pilgrimageyoga.com, affiliated-business.com, and roodlicht.com.

The domain ffix.me partially shares name servers with other domains such as amarante.org, perimeter.systems, beingstuart.com, debreciner.hu, and edsdeal.com.

ivy.ns.cloudflare.com points to the following IP numbers: 2606:4700:50::adf5:3a78, 2803:f800:50::6ca2:c078, 2a06:98c1:50::ac40:2078, 108.162.192.120, 172.64.32.120, and 173.245.58.120, while jack.ns.cloudflare.com points to: 2606:4700:58::adf5:3b79, 2803:f800:50::6ca2:c179, 2a06:98c1:50::ac40:2179, 108.162.193.121, 172.64.33.121, and 173.245.59.121.

Two mail servers, in1-smtp.messagingengine.com and in2-smtp.messagingengine.com, manage ffix.me.

Just like the domains tdub.co, meshy.org, salking.co.uk, tallwireless.com, and hfsoftware.nl, ffix.me 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