DNSWHOIS.INFO - nektar.ai

Search for IP or hostnames:

nektar.ai checked at 2025-09-09T15:09:39.142Z 246ms 143/143/143 100% R:13

`nektar.ai`

NS	`ns-340.awsdns-42.com`
		A	2600:9000:5301:5400::1 ^{🇺🇸 Amazon}
			PTR	`ns-340.awsdns-42.com`
		A	205.251.193.84^{🇺🇸 Amazon}
			PTR	`ns-340.awsdns-42.com`
NS	`ns-989.awsdns-59.net`
		A	2600:9000:5303:dd00::1 ^{🇺🇸 Amazon}
			PTR	`ns-989.awsdns-59.net`
		A	205.251.195.221^{🇺🇸 Amazon}
			PTR	`ns-989.awsdns-59.net`
NS	`ns-1460.awsdns-54.org`
		A	2600:9000:5305:b400::1 ^{🇺🇸 Amazon}
			PTR	`ns-1460.awsdns-54.org`
		A	205.251.197.180^{🇺🇸 Amazon}
			PTR	`ns-1460.awsdns-54.org`
MX	`aspmx.l.google.com`
		A	2a00:1450:400c:c06::1b ^{🇧🇪 Google}
			PTR	`wb-in-f27.1e100.net`
			PTR	`wb-in-x1b.1e100.net`
		A	64.233.166.26^{🇺🇸 Google}
			PTR	`wm-in-f26.1e100.net`
NS	`ns-1726.awsdns-23.co.uk`
		A	2600:9000:5306:be00::1 ^{🇺🇸 Amazon}
			PTR	`ns-1726.awsdns-23.co.uk`
		A	205.251.198.190^{🇺🇸 Amazon}
			PTR	`ns-1726.awsdns-23.co.uk`
MX	`alt1.aspmx.l.google.com`
		A	2a00:1450:4013:c1c::1b ^{🇳🇱 Google}
			PTR	`yugrqog-in-f27.1e100.net`
		A	192.178.156.26^{🇺🇸 Google}
			PTR	`yugrqog-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`
		A	2a00:1450:4025:c01::1a ^{🇵🇱 Google}
			PTR	`rd-in-f26.1e100.net`
		A	142.250.147.26^{🇺🇸 Google}
			PTR	`rd-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`
		A	2a00:1450:4010:c0e::1a ^{🇫🇮 Google}
			PTR	`lu-in-f26.1e100.net`
			PTR	`lu-in-x1a.1e100.net`
		A	74.125.131.27^{🇺🇸 Google}
			PTR	`lu-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`
		A	2404:6800:4003:c06::1a ^{🇸🇬 Google}
			PTR	`sm-in-f26.1e100.net`
		A	142.250.4.27^{🇺🇸 Google}
			PTR	`sm-in-f27.1e100.net`
A	63.250.43.144^{🇺🇸 Namecheap}
		PTR	`ingress-haven.ewp.live`
A	63.250.43.145^{🇺🇸 Namecheap}
		PTR	`ingress-haven.ewp.live`

`ai`

	NS	`v0n0.nic.ai`
	NS	`v0n1.nic.ai`
	NS	`v0n2.nic.ai`
	NS	`v0n3.nic.ai`
	NS	`v2n0.nic.ai`
	NS	`v2n1.nic.ai`

Starts with same word
`nektar.no`
`nektar.fr`
`nektar.co.kr`
`nektar.eu`
`nektar.cz`
`nektar.at`
`nektar.co.uk`
`nektar.ru`
`nektar.buzz`
`nektar.info.pl`
`nektar.co.nz`
`nektar.co`
`nektar.cn`
`nektar.gr`
`nektar.pro`
`nektar.dk`
`nektar.info`
`nektar.com`
`nektar.us`
`nektar.ai`
`nektar.ca`
`nektar.de`
`nektar.com.pl`
`nektar.ee`
`nektar.ch`
`nektar.in`

Starts similarily
`aktren.at`
`karnet.com.tr`
`katren.org`
`karnet.krakow.pl`
`nektar.co`
`karnet.eu`
`tanker.sk`
`kranet.pl`
`rantek.fi`
`karent.jp`
`tanker.fund`
`trenka.co.at`
`trekan.net`
`rentka.cz`
`aktern.dk`
`karnet.pl`
`katren.net`
`kenart.co.jp`
`arkent.com`
`takern.se`
`karent.ru`
`netkar.com.br`
`arkent.web.tr`
`kanter.com`
`katren.info`
`tanker.io`
`aknert.se`
`nektar.cn`
`kanter.net`
`arknet.live`
`kanter.co`
`ntreak.com`
`arknet.com.pl`
`tanker.us`
`nektar.gr`
`entrak.pl`
`akrent.ee`
`arknet.info`
`enkart.com`
`kentra.org`
`arknet.de`
`trenka.org`
`karten.international`
`karten.biz`
`katren.su`
`nektar.pro`
`kranet.ca`
`netark.net`
`arknet.com.au`
`karten.ch`
`nektar.dk`
`nektra.dk`
`nektar.info`
`kanter.nl`
`karten.eu`
`katren.name`
`nektar.com`
`tanker.com.au`
`arknet.co.nz`
`ankert.net`
`katren.se`
`karent.org`
`tanker.ae`
`nektar.us`
`kretan.ro`
`tarken.net`
`entrak.nl`
`karten.com.mx`
`aktren.de`
`tanker.ca`
`nektar.ai`
`karten.nl`
`arknet.cn`
`karten.cn`
`katern.net`
`karnet.com`
`tkaner.com`
`netark.org`
`karnet.it`
`kanter.cn`
`terkan.com`
`karten.no`
`karent.dk`
`tekran.biz`
`nektra.de`
`netark.dk`
`nektar.ca`
`nektar.de`
`rantek.net`
`netkar.org`
`takern.com`
`kanter.eu`
`karten.farm`
`rkanet.com`
`karnet.xyz`
`kraten.com.br`
`arknet.co.uk`
`karnet.space`
`tanker.pro`
`ternak.org`

AI analysis

nektar.ai points to two IP numbers: 63.250.43.144 and 63.250.43.145.

IP numbers are shared between nektar.ai and other host names such as danwin1210.me, holisticwellnesshub.com, allmartech.com, company.liigo.world, and fawnheatingcooling.com.

Four name servers, ns-340.awsdns-42.com, ns-989.awsdns-59.net, ns-1460.awsdns-54.org, and ns-1726.awsdns-23.co.uk, are delegated to nektar.ai.

Name servers of nektar.ai are at least partially shared with other domains such as guardant360.com, mediaconvert.eu-west-2.amazonaws.com, federacy.com, tp-link.com.my, and tokyu-land.net.

The name servers ns-425.awsdns-53.com, ns-530.awsdns-02.net, ns-1862.awsdns-40.co.uk, ns-1537.awsdns-00.co.uk, ns-1203.awsdns-22.org, ns-319.awsdns-39.com, ns-1513.awsdns-61.org, ns-1383.awsdns-44.org, ns-1129.awsdns-13.org, and ns-947.awsdns-54.net are frequently used in tandem.

ns-340.awsdns-42.com, ns-989.awsdns-59.net, ns-1460.awsdns-54.org, and ns-1726.awsdns-23.co.uk each point to two IP numbers respectively: 2600:9000:5301:5400::1, 205.251.193.84; 2600:9000:5303:dd00::1, 205.251.195.221; 2600:9000:5305:b400::1, 205.251.197.180; 2600:9000:5306:be00::1, 205.251.198.190.

The five mail servers, aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, and alt4.aspmx.l.google.com, are responsible for handling nektar.ai.

Other domains such as thelittlegym.com.co, newfoss.eu, mimizun.com, rentict.com, and chartbeat.com share at least some mail servers with nektar.ai.

The mail servers aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com, and aspmx5.googlemail.com are commonly used in conjunction with these mail servers.

aspmx.l.google.com, 2a00:1450:400c:c06::1b, and 64.233.166.26 are associated with each other.

alt1.aspmx.l.google.com, 2a00:1450:4013:c1c::1b, and 192.178.156.26 are interconnected.

alt2.aspmx.l.google.com, 2a00:1450:4025:c01::1a, and 142.250.147.26 are linked together.

alt3.aspmx.l.google.com, 2a00:1450:4010:c0e::1a, and 74.125.131.27 are correlated.

alt4.aspmx.l.google.com, 2404:6800:4003:c06::1a, and 142.250.4.27 are related to each other.

dbq