CF1757208248939-tsm20250906182357

DNSWHOIS.INFO - perf.io

Search for IP or hostnames:

perf.io checked at 2025-09-07T01:24:08.924Z 217ms 67/67/67 100% R:16

`perf.io`

	NS	`ns2.openprovider.be`
			A	2400:cb00:2049:1::a29f:1b60 ^{🇺🇸 Cloudflare}
			A	162.159.27.96^Cloudflare
	NS	`ns3.openprovider.eu`
			A	2400:cb00:2049:1::a29f:3059 ^{🇺🇸 Cloudflare}
			A	162.159.48.89^Cloudflare
	NS	`ns1.openprovider.nl`
			A	2400:cb00:2049:1::a29f:1a0a ^{🇺🇸 Cloudflare}
			A	162.159.26.10^Cloudflare
	A	2a01:4f9:6a:2257::2 ^{🇩🇪 Hetzner}
	A	65.21.235.168^{🇫🇮 Hetzner}
			PTR	`static.168.235.21.65.clients.your-server.de`

`io`

	NS	`a0.nic.io`
	NS	`a2.nic.io`
	NS	`b0.nic.io`
	NS	`c0.nic.io`

Starts with same word
`perf.run`
`perf.solutions`
`perf.co`
`perf.pro`
`perf.bar`
`perf.us`
`perf.su`
`perf.eu`
`perf.de`
`perf.fr`
`perf.cz`
`perf.pl`
`perf.systems`
`perf.dk`
`perf.com`
`perf.io`
`perf.coop`
`perf.net`
`perf.nu`
`perf.guru`
`perf.email`
`perf.ru`
`perf.ly`
`perf.link`
`perf.cloud`
`perf.expert`

Starts similarily
`pref.mie.jp`
`perf.link`
`pref.co`
`ferp.eu`
`eprf.com.pk`
`pref.com.ua`
`rpef.com`
`pref.kochi.jp`
`fpre.jp`
`frep.ru`
`rfpe.com`
`perf.cloud`
`pref.yokohama`
`pref.gunma.jp`
`perf.expert`
`pref.toyama.jp`
`eprf.ru`
`pfre.net.au`
`pref.nara.jp`
`pref.akita.jp`
`prfe.ru`
`pref.saga.jp`
`eprf.cn`
`pref.niigata.jp`
`efpr.edu.rs`
`rfep.es`
`pref.kyoto.jp`
`efpr.us`
`frep.com`
`repf.org`
`pref.net`
`epfr.by`
`pref.miyazaki.jp`
`pref.miyagi.jp`
`pref.com`
`ferp.pl`
`perf.run`
`efpr.ru`
`frep.ch`
`repf.ro`
`perf.solutions`
`pref.yamanashi.jp`
`epfr.com`
`ferp.cn`
`rfep.ru`
`pfer.org`
`fpre.ru`
`epfr.nl`
`efpr.it`
`pref.aomori.jp`
`pref.hyogo.jp`
`erfp.ca`
`perf.co`
`repf.se`
`perf.pro`
`perf.bar`
`ferp.br`
`fpre.de`
`perf.us`
`perf.su`
`epfr.ru`
`refp.biz`
`pref.in`
`erfp.ru`
`pref.aichi.jp`
`pref.fukushima.jp`
`pref.kagoshima.jp`
`perf.eu`
`pref.gouv.fr`
`perf.de`
`perf.fr`
`pefr.net`
`pref.gifu.jp`
`eprf.eu`
`efrp.com`
`efpr.nl`
`ferp.in`
`eprf.de`
`erpf.org`
`fpre.com`
`perf.cz`
`perf.pl`
`pref.fr`
`pref.shimane.jp`
`pref.osaka.jp`
`pref.tokushima.jp`
`pfer.com`
`perf.systems`
`pref.shiga.jp`
`fpre.net`
`frep.cz`
`erfp.de`
`ferp.de`
`perf.dk`
`pfer.cn`
`pfre.org`
`pref.es`
`efpr.fr`
`pref.de`
`pref.ishikawa.jp`
`epfr.net`
`efpr.at`
`efrp.org`
`pref.yamagata.jp`
`pref.club`
`rpfe.com`
`ferp.it`
`pref.eu`
`erpf.info`
`pref.iwate.jp`
`perf.com`
`pref.tochigi.jp`
`pref.tottori.jp`
`refp.org`
`pref.hiroshima.jp`
`perf.io`
`frep.de`
`fper.ru`
`pref.oita.jp`
`pref.fukui.jp`
`perf.coop`

AI analysis

perf.io is configured to point to two IP addresses, namely 2a01:4f9:6a:2257::2 and 65.21.235.168.

IP numbers are shared between perf.io and other host names such as hpcexpert.eu, streamcomputing.eu, www.opencl.org, streamcomputing.net, and hpc.training.

Three name servers, ns2.openprovider.be, ns3.openprovider.eu, and ns1.openprovider.nl, are delegated to perf.io.

The name servers of perf.io are at least partially shared with other domains such as beursactie.nl, spirofil.eu, prominent-techniek.nl, conmar.nl, and propitius.nl.

ns2.openprovider.be, 2400:cb00:2049:1::a29f:1b60, and 162.159.27.96 are associated with each other. Similarly, ns3.openprovider.eu, 2400:cb00:2049:1::a29f:3059, and 162.159.48.89 are interconnected. Additionally, ns1.openprovider.nl, 2400:cb00:2049:1::a29f:1a0a, and 162.159.26.10 are linked together.

dbq

cTvwgRL CF johedugfp 2025-09-07