NSLIST.NET - zing.care

Search for IP or hostnames:

zing.care checked at 2025-09-06T20:50:56.384Z 212ms 150/150/150 100% R:13

`zing.care`

NS	`ns-cloud-a1.googledomains.com`
		A	2001:4860:4802:32::6a ^{🇺🇸 Google}
			PTR	`ns-cloud-a1.googledomains.com`
		A	216.239.32.106^{🇺🇸 Google}
			PTR	`ns-cloud-a1.googledomains.com`
NS	`ns-cloud-a2.googledomains.com`
		A	2001:4860:4802:34::6a ^{🇺🇸 Google}
			PTR	`ns-cloud-a2.googledomains.com`
		A	216.239.34.106^{🇺🇸 Google}
			PTR	`ns-cloud-a2.googledomains.com`
NS	`ns-cloud-a3.googledomains.com`
		A	2001:4860:4802:36::6a ^{🇺🇸 Google}
			PTR	`ns-cloud-a3.googledomains.com`
		A	216.239.36.106^{🇺🇸 Google}
			PTR	`ns-cloud-a3.googledomains.com`
NS	`ns-cloud-a4.googledomains.com`
		A	2001:4860:4802:38::6a ^{🇺🇸 Google}
			PTR	`ns-cloud-a4.googledomains.com`
		A	216.239.38.106^{🇺🇸 Google}
			PTR	`ns-cloud-a4.googledomains.com`
MX	`aspmx.l.google.com`
		A	2607:f8b0:4004:c1b::1b ^{🇺🇸 Google}
			PTR	`wv-in-f27.1e100.net`
		A	142.251.163.26^{🇺🇸 Google}
			PTR	`wv-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`
		A	2a00:1450:400b:c02::1a ^{🇮🇪 Google}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google}
			PTR	`dj-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`
		A	2a00:1450:400c:c00::1b ^{🇧🇪 Google}
			PTR	`ws-in-f27.1e100.net`
			PTR	`ws-in-x1b.1e100.net`
		A	173.194.76.26^{🇺🇸 Google}
			PTR	`ws-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`
		A	2a00:1450:4025:402::1b ^{🇳🇱 Google}
			PTR	`rb-in-f27.1e100.net`
		A	142.250.102.26^{🇺🇸 Google}
			PTR	`rb-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`
		A	2a00:1450:4013:c1c::1b ^{🇳🇱 Google}
			PTR	`yugrqog-in-f27.1e100.net`
		A	192.178.156.27^{🇺🇸 Google}
			PTR	`yugrqog-in-f27.1e100.net`
A	198.49.23.144^{🇺🇸 SQUARESPACE}
A	198.49.23.145^{🇺🇸 SQUARESPACE}
A	198.185.159.144^{🇺🇸 SQUARESPACE}
A	198.185.159.145^{🇺🇸 SQUARESPACE}

`care`

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

Starts with same word
`zing.coffee`
`zing.es`
`zing.nu`
`zing.gg`
`zing.biz`
`zing.money`
`zing.org`
`zing.my`
`zing.co.uk`
`zing.kz`
`zing.cool`
`zing.center`
`zing.no`
`zing.ca`
`zing.network`
`zing.ch`
`zing.mx`
`zing.ro`
`zing.com`
`zing.com.pl`
`zing.net.nz`
`zing.de`
`zing.info.vn`
`zing.in`
`zing.news`
`zing.email`
`zing.biz.vn`
`zing.im`
`zing.eu`
`zing.si`
`zing.fr`
`zing.org.uk`
`zing.us`
`zing.vn`
`zing.solutions`
`zing.io`
`zing.tools`
`zing.se`
`zing.hu`
`zing.cz`
`zing.world`
`zing.ie`
`zing.space`
`zing.dk`
`zing.com.br`
`zing.kr`
`zing.vc`
`zing.net.au`
`zing.uk.com`
`zing.com.vn`
`zing.co.nz`
`zing.ru`
`zing.ws`
`zing.zapto.org`
`zing.life`
`zing.lt`
`zing.info`
`zing.net`
`zing.care`
`zing.tv`
`zing.services`

Starts similarily
`zing.money`
`ginz.cn`
`zing.org`
`zing.my`
`ingz.de`
`zing.co.uk`
`zing.kz`
`zing.cool`
`zign.mx`
`gzin.cz`
`zngi.cn`
`zing.center`
`gizn.com`
`gniz.com`
`zing.no`
`zign.info`
`ginz.com`
`izgn.com`
`gzin.com`
`zing.ca`
`gniz.no`
`ginz.it`
`zing.network`
`zign.pt`
`zing.ch`
`zign.org`
`ingz.net`
`gzin.info`
`zing.mx`
`zign.com`
`zing.ro`
`zing.com`
`ngiz.com`
`ginz.jp`
`ginz.nl`
`ingz.com`
`zing.com.pl`
`nigz.nl`
`zign.jp`
`zing.net.nz`
`zing.de`
`nzig.co.nz`
`zing.info.vn`
`zing.in`
`zign.at`
`zing.news`
`zngi.com`
`zing.email`
`zign.no`
`zing.biz.vn`
`ginz.de`
`zign.io`
`zign.in`
`zing.im`
`zing.eu`
`zign.lu`
`zgni.net`
`zing.si`
`zing.fr`
`ginz.co.nz`
`zign.fi`
`zing.org.uk`
`zing.us`
`zign.de`
`ingz.ru`
`ngiz.nl`
`zign.ca`
`zing.vn`
`zing.solutions`
`zign.gr`
`zing.io`
`zing.tools`
`ignz.com`
`zign.hu`
`zing.se`
`zing.hu`
`ginz.net`
`zing.cz`
`zing.world`
`zign.us`
`ngzi.ws`
`zing.ie`
`gzni.com`
`zign.dk`
`zing.space`
`zing.dk`
`zing.com.br`
`zing.kr`
`zing.vc`
`zign.it`
`zign.ru`
`zign.cz`
`zing.net.au`
`nzig.com`
`zgin.de`
`zign.co.uk`
`zign.ch`
`zgni.com`
`izng.cn`
`zing.uk.com`

AI analysis

zing.care is configured to point to the following four IP addresses: 198.49.23.144, 198.49.23.145, 198.185.159.144, and 198.185.159.145.

IP numbers are shared between zing.care and other host names, such as fairfieldathleticclub.com, sheung-king.com, tv-cm.com, poorline.com, and jay-alexander.com.

Four name servers, ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, and ns-cloud-a4.googledomains.com, have been delegated to zing.care.

The domain zing.care shares name servers, at least partially, with other domains such as whoalubbock.org, duckman-proofreading.com, latrevstudio.com, njarvis.com, and gaptire.com.

ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, and ns-cloud-a4.googledomains.com all point to two IP numbers each: 2001:4860:4802:32::6a and 216.239.32.106; 2001:4860:4802:34::6a and 216.239.34.106; 2001:4860:4802:36::6a and 216.239.36.106; 2001:4860:4802:38::6a and 216.239.38.106, respectively.

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 zing.care.

Other domains like aslaveslife.com, letu.ru, marketnewsletters.com, hyzone.co.uk, and cecamp-es.com.br share some mail servers, at least partially, with zing.care.

The mail servers aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com, aspmx5.googlemail.com, and smtp.google.com are commonly utilized in conjunction.

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 each point to two IP numbers: 2607:f8b0:4004:c1b::1b/142.251.163.26, 2a00:1450:400b:c02::1a/172.253.116.27, 2a00:1450:400c:c00::1b/173.194.76.26, 2a00:1450:4025:402::1b/142.250.102.26, and 2a00:1450:4013:c1c::1b/192.178.156.27 respectively.

dbq