NSLIST.NET - invoker.me

Search for IP or hostnames:

invoker.me checked at 2025-09-07T02:37:28.893Z 3763ms 145/145/145 100% R:16

`invoker.me`

MX	`mx1.feishu.cn`
		A	52.220.106.220^{🇸🇬 Amazon}
			PTR	`ec2-52-220-106-220.ap-southeast-1.compute.amazonaws.com`
MX	`mx2.feishu.cn`
		A	101.126.58.225^{🇨🇳 VOLCANO-ENGINE}
		A	122.14.229.0^{🇨🇳 UNICOM-CN}
MX	`mx3.feishu.cn`
		A	52.220.106.220^{🇸🇬 Amazon}
			PTR	`ec2-52-220-106-220.ap-southeast-1.compute.amazonaws.com`
		A	101.126.58.225^{🇨🇳 VOLCANO-ENGINE}
		A	122.14.229.0^{🇨🇳 UNICOM-CN}
NS	`amy.ns.cloudflare.com`
		A	2606:4700:50::adf5:3a65 ^{🇺🇸 Cloudflare}
			PTR	`amy.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c065 ^{🇨🇷 Cloudflare}
			PTR	`amy.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2065 ^{🇺🇸 Cloudflare}
			PTR	`amy.ns.cloudflare.com`
		A	108.162.192.101^{🇺🇸 Cloudflare}
			PTR	`amy.ns.cloudflare.com`
		A	172.64.32.101^{🇺🇸 Cloudflare}
			PTR	`amy.ns.cloudflare.com`
		A	173.245.58.101^{🇺🇸 Cloudflare}
			PTR	`amy.ns.cloudflare.com`
NS	`brad.ns.cloudflare.com`
		A	2606:4700:58::adf5:3b69 ^{🇺🇸 Cloudflare}
			PTR	`brad.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c169 ^{🇨🇷 Cloudflare}
			PTR	`brad.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2169 ^{🇺🇸 Cloudflare}
			PTR	`brad.ns.cloudflare.com`
		A	108.162.193.105^{🇺🇸 Cloudflare}
			PTR	`brad.ns.cloudflare.com`
		A	172.64.33.105^{🇺🇸 Cloudflare}
			PTR	`brad.ns.cloudflare.com`
		A	173.245.59.105^{🇺🇸 Cloudflare}
			PTR	`brad.ns.cloudflare.com`
A	2606:4700:3031::6815:1f9e ^{🇺🇸 Cloudflare}
A	2606:4700:3037::ac43:b23d ^{🇺🇸 Cloudflare}
A	104.21.31.158^Cloudflare
A	172.67.178.61^{🇺🇸 Cloudflare}

`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
`invoker.me`
`invoker.de`
`invoker.com`
`invoker.ca`
`invoker.dev`
`invoker.org`
`invoker.ru`

Starts similarily
`verikon.dk`
`kinevor.com`
`koniver.com`
`invoker.ca`
`korniev.com`
`invekor.com.tr`
`verikon.com.tr`
`revikon.eu`
`invoker.dev`
`verikon.com`
`kenviro.net`
`nekovri.nl`
`inkover.com`
`kinover.ru`
`kevinro.com`
`inverko.com`
`kirenov.com`
`veronik.at`
`nekovri.com`
`invoker.org`
`inverko.com.pe`
`norevik.com`
`revikon.de`
`evrikon.de`
`veronik.com`
`inverko.be`
`kernovi.bg`
`irvekon.cz`
`envirok.org`
`inkover.net`
`revikon.com`
`revikon.dk`
`invoker.ru`
`overink.de`
`evorink.com`
`rkovine.com`
`orviken.se`
`inverko.nl`
`invekor.net`
`evrikon.com`
`invoker.me`
`nevikor.com`
`overkin.ru`
`veroink.com`
`nekovri.org`
`kernovi.com`
`overink.com`
`verniko.com`
`irvekon.com`
`vinoker.com`
`nikerov.ru`
`overkin.com`
`krovnie.ru`
`kervion.com`
`invoker.de`
`renovik.com`
`verikon.no`
`kiveron.nl`
`invoker.com`

AI analysis

The DNS record invoker.me resolves to the following IP addresses: 2606:4700:3031::6815:1f9e, 2606:4700:3037::ac43:b23d, 104.21.31.158, and 172.67.178.61.

The IP numbers are shared by invoker.me with other host names such as hungrytiger.at, generalcouncil.com, imajbet.net, whiskeyandred.com, and www.sir.pt.

Two name servers, amy.ns.cloudflare.com and brad.ns.cloudflare.com, are delegated to invoker.me.

The name server setup for invoker.me is shared with other domains such as rtnik.com, painflame.com, 3p-ttp.org, stockt-shirtdesigns.com, and geekstate.org.

The name servers of invoker.me are at least partially shared with other domains such as linkz-im.com, billacholla.com, dkd.su, proyectocolor.com.ar, and ai-akai.pl.

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

There are two DNS records: amy.ns.cloudflare.com and brad.ns.cloudflare.com. amy.ns.cloudflare.com resolves to 2606:4700:50::adf5:3a65, 2803:f800:50::6ca2:c065, 2a06:98c1:50::ac40:2065, 108.162.192.101, 172.64.32.101, and 173.245.58.101, while brad.ns.cloudflare.com resolves to 2606:4700:58::adf5:3b69, 2803:f800:50::6ca2:c169, 2a06:98c1:50::ac40:2169, 108.162.193.105, 172.64.33.105, and 173.245.59.105.

Three mail servers, mx1.feishu.cn, mx2.feishu.cn, and mx3.feishu.cn, are responsible for handling invoker.me.

Other domains such as fpv.im, ehijoy.com, playwires.com, i-chip.cn, and andaseat.cn share at least some mail servers with invoker.me.

mx1.feishu.cn points to a single IP address: 52.220.106.220. mx2.feishu.cn, on the other hand, directs to two IP addresses: 101.126.58.225 and 122.14.229.0. Finally, mx3.feishu.cn resolves to three IP addresses: 52.220.106.220, 101.126.58.225, and 122.14.229.0.

dbq