DNSWHOIS.INFO - kong.io

Search for IP or hostnames:

kong.io checked at 2025-09-06T17:51:30.194Z 174ms 156/156/156 100% R:14

`kong.io`

MX	`smtp.google.com`
		A	2a00:1450:400c:c06::1a ^{🇧🇪 Google}
			PTR	`wb-in-f26.1e100.net`
			PTR	`wb-in-x1a.1e100.net`
		A	2a00:1450:400c:c06::1b ^{🇧🇪 Google}
			PTR	`wb-in-f27.1e100.net`
			PTR	`wb-in-x1b.1e100.net`
		A	2a00:1450:400c:c0d::1a ^{🇧🇪 Google}
			PTR	`wf-in-f26.1e100.net`
		A	2a00:1450:400c:c0d::1b ^{🇧🇪 Google}
			PTR	`wf-in-f27.1e100.net`
		A	66.102.1.26^{🇺🇸 Google}
			PTR	`wb-in-f26.1e100.net`
		A	66.102.1.27^{🇺🇸 Google}
			PTR	`wb-in-f27.1e100.net`
		A	142.250.110.26^{🇺🇸 Google}
			PTR	`wf-in-f26.1e100.net`
		A	142.250.110.27^{🇺🇸 Google}
			PTR	`wf-in-f27.1e100.net`
		A	142.251.168.26^{🇺🇸 Google}
			PTR	`wh-in-f26.1e100.net`
NS	`felipe.ns.cloudflare.com`
		A	2606:4700:58::a29f:2c74 ^{🇺🇸 Cloudflare}
			PTR	`felipe.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c374 ^{🇨🇷 Cloudflare}
			PTR	`felipe.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2374 ^{🇺🇸 Cloudflare}
			PTR	`felipe.ns.cloudflare.com`
		A	108.162.195.116^{🇺🇸 Cloudflare}
			PTR	`felipe.ns.cloudflare.com`
		A	162.159.44.116^Cloudflare
			PTR	`felipe.ns.cloudflare.com`
		A	172.64.35.116^{🇺🇸 Cloudflare}
			PTR	`felipe.ns.cloudflare.com`
NS	`rachel.ns.cloudflare.com`
		A	2606:4700:50::adf5:3ad7 ^{🇺🇸 Cloudflare}
			PTR	`rachel.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0d7 ^{🇨🇷 Cloudflare}
			PTR	`rachel.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20d7 ^{🇺🇸 Cloudflare}
			PTR	`rachel.ns.cloudflare.com`
		A	108.162.192.215^{🇺🇸 Cloudflare}
			PTR	`rachel.ns.cloudflare.com`
		A	172.64.32.215^{🇺🇸 Cloudflare}
			PTR	`rachel.ns.cloudflare.com`
		A	173.245.58.215^{🇺🇸 Cloudflare}
			PTR	`rachel.ns.cloudflare.com`
A	2606:4700::6812:2d ^{🇺🇸 Cloudflare}
A	2606:4700::6812:12d ^{🇺🇸 Cloudflare}
A	104.18.0.45^Cloudflare
A	104.18.1.45^Cloudflare

`io`

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

Starts with same word
`kong.co.za`
`kong.com.tw`
`kong.holdings`
`kong.com`
`kong.dk`
`kong.media`
`kong.info`
`kong.taxi`
`kong.org.cn`
`kong.bet`
`kong.world`
`kong.net`
`kong.jp`
`kong.sk`
`kong.org`
`kong.cn`
`kong.re.kr`
`kong.eu`
`kong.agency`
`kong.net-freaks.com`
`kong.de`
`kong.ge`
`kong.at`
`kong.ie`
`kong.international`
`kong.tw`
`kong.co`
`kong.pro`
`kong.cat`
`kong.spb.ru`
`kong.cafe`
`kong.github.io`
`kong.be`
`kong.com.pl`
`kong.fr`
`kong.ca`
`kong.ch`
`kong.ru`
`kong.se`
`kong.la`
`kong.io`
`kong.hu`
`kong.me`
`kong.city`
`kong.com.br`
`kong.name`
`kong.toys`
`kong.wtf`
`kong.my`
`kong.email`
`kong.us`
`kong.nu`
`kong.it`

Starts similarily
`kong.toys`
`onkg.com`
`kong.wtf`
`nokg.com`
`ngok.org`
`kong.my`
`okng.com`
`kong.email`
`kong.us`
`kong.nu`
`kong.it`
`knog.cl`
`gokn.org`
`gonk.cn`
`kong.co.za`
`kong.com.tw`
`kogn.org`
`kong.holdings`
`ngok.elasticbeanstalk.com`
`knog.ru`
`gkon.com.au`
`gnok.com`
`gnok.net`
`kong.com`
`knog.de`
`kong.dk`
`kong.media`
`gnok.cn`
`kong.info`
`okgn.ca`
`kong.taxi`
`gkon.ru`
`knog.dk`
`knog.nl`
`kong.org.cn`
`gkon.in`
`kong.bet`
`gonk.dk`
`gkno.cn`
`knog.cn`
`gonk.de`
`ngok.jp`
`nokg.ru`
`gokn.cn`
`kong.world`
`kong.net`
`kong.jp`
`gonk.at`
`kong.sk`
`ogkn.ru`
`gonk.net`
`nogk.cn`
`ngko.com`
`okgn.com`
`gkon.dk`
`gkon.se`
`kong.org`
`kong.cn`
`gonk.co.uk`
`gkon.pl`
`ngok.com.ua`
`kngo.de`
`kong.re.kr`
`ngok.co.jp`
`kong.eu`
`kong.agency`
`okng.net`
`gonk.jp`
`kong.net-freaks.com`
`nogk.ru`
`nogk.gr`
`kong.de`
`kong.ge`
`knog.sk`
`kong.at`
`kong.ie`
`kong.international`
`gokn.com`
`nogk.org`
`kong.tw`
`gkno.com`
`kong.co`
`gnok.ru`
`ogkn.com`
`kong.pro`
`ngok.ru`
`gkon.de`
`kngo.com`
`gonk.se`
`knog.org`
`kgon.com`
`nogk.com`
`kngo.co`
`gonk.it`
`kong.cat`
`knog.com`
`gonk.com`
`ngok.cn`
`gonk.ru`
`kngo.org`
`kong.spb.ru`
`ogkn.cn`
`kong.cafe`
`kngo.ru`
`okng.org`
`kong.github.io`
`gonk.nl`
`kngo.net`
`kong.be`
`kogn.ru`
`kong.com.pl`
`kong.fr`
`kong.ca`
`kong.ch`
`kong.ru`
`kong.se`
`kgon.net`
`knog.pl`
`kogn.com`
`gkon.com`
`kong.la`
`knog.com.au`
`kong.io`
`kong.hu`
`kong.me`
`kong.city`
`kong.com.br`
`kong.name`

AI analysis

The DNS record kong.io resolves to the following IP addresses: 2606:4700::6812:2d, 2606:4700::6812:12d, 104.18.0.45, and 104.18.1.45.

The IP numbers are shared by kong.io with other host names such as hostopia.com.au, doctorunite.com, www.torontoairport.ca, crockettlibrary.com, and jobs.claeysengels.be.

Two name servers, felipe.ns.cloudflare.com and rachel.ns.cloudflare.com, are delegated to kong.io.

The name server setup for kong.io is shared with other domains such as ayudalegal.com.ar, kodemax.com, xn--80ajghcscort2dvb.xn--p1ai, lasromeas.com, and dinil.net.

The name servers of kong.io are at least partially shared with other domains such as granitestatesolar.com, fishaf.com, jingxichehang.com, agrisera.com, and latam.com.

There are two DNS records: felipe.ns.cloudflare.com and rachel.ns.cloudflare.com. felipe.ns.cloudflare.com resolves to 2606:4700:58::a29f:2c74, 2803:f800:50::6ca2:c374, 2a06:98c1:50::ac40:2374, 108.162.195.116, 162.159.44.116, and 172.64.35.116, while rachel.ns.cloudflare.com resolves to 2606:4700:50::adf5:3ad7, 2803:f800:50::6ca2:c0d7, 2a06:98c1:50::ac40:20d7, 108.162.192.215, 172.64.32.215, and 173.245.58.215.

The mail server, smtp.google.com, manages kong.io.

Just like the domains onrisegroup.com, fraudconference.co.uk, warlock.com, jcpoba.com, and fineform.info, kong.io also has the same mail server setup.

Other domains such as bordt.com, roguescove.org, rotation-sued-leipzig.de, acerepair.pro, and dungrani.com share at least some mail servers with kong.io.

The mail servers alt1.aspmx.l.google.com are frequently utilized in conjunction.

smtp.google.com is associated with the following nine IP addresses: 2a00:1450:400c:c06::1a, 2a00:1450:400c:c06::1b, 2a00:1450:400c:c0d::1a, 2a00:1450:400c:c0d::1b, 66.102.1.26, 66.102.1.27, 142.250.110.26, 142.250.110.27, and 142.251.168.26.

dbq