NSLIST.NET - caring.name

Search for IP or hostnames:

caring.name checked at 2025-09-06T18:13:23.071Z 209ms 143/143/143 100% R:17

`caring.name`

NS	`ns-212.awsdns-26.com`
		A	2600:9000:5300:d400::1 ^{🇺🇸 Amazon}
			PTR	`ns-212.awsdns-26.com`
		A	205.251.192.212^{🇺🇸 Amazon}
			PTR	`ns-212.awsdns-26.com`
NS	`ns-879.awsdns-45.net`
		A	2600:9000:5303:6f00::1 ^{🇺🇸 Amazon}
			PTR	`ns-879.awsdns-45.net`
		A	205.251.195.111^{🇺🇸 Amazon}
			PTR	`ns-879.awsdns-45.net`
NS	`ns-1368.awsdns-43.org`
		A	2600:9000:5305:5800::1 ^{🇺🇸 Amazon}
			PTR	`ns-1368.awsdns-43.org`
		A	205.251.197.88^{🇺🇸 Amazon}
			PTR	`ns-1368.awsdns-43.org`
MX	`aspmx.l.google.com`
		A	2607:f8b0:4004:c19::1b ^{🇺🇸 Google}
			PTR	`bk-in-f27.1e100.net`
		A	172.253.115.26^{🇺🇸 Google}
			PTR	`bg-in-f26.1e100.net`
NS	`ns-1874.awsdns-42.co.uk`
		A	2600:9000:5307:5200::1 ^{🇺🇸 Amazon}
			PTR	`ns-1874.awsdns-42.co.uk`
		A	205.251.199.82^{🇺🇸 Amazon}
			PTR	`ns-1874.awsdns-42.co.uk`
MX	`alt1.aspmx.l.google.com`
		A	2a00:1450:400b:c02::1a ^{🇮🇪 Google}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google}
			PTR	`dj-in-f26.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::1a ^{🇳🇱 Google}
			PTR	`rb-in-f26.1e100.net`
		A	142.250.102.27^{🇺🇸 Google}
			PTR	`rb-in-f27.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.26^{🇺🇸 Google}
			PTR	`yugrqog-in-f26.1e100.net`
A	3.88.83.143^{🇺🇸 Amazon}
		PTR	`ec2-3-88-83-143.compute-1.amazonaws.com`
A	52.73.170.37^{🇺🇸 Amazon}
		PTR	`ec2-52-73-170-37.compute-1.amazonaws.com`

`name`

	NS	`ac1.nstld.com`
	NS	`ac2.nstld.com`
	NS	`ac3.nstld.com`
	NS	`ac4.nstld.com`

Starts with same word
`caring.ca`
`caring.amsterdam`
`caring.me`
`caring.pet`
`caring.co.kr`
`caring.capital`
`caring.org`
`caring.agency`
`caring.com`
`caring.tv`
`caring.name`
`caring.co`
`caring.sg`
`caring.be`
`caring.net`
`caring.community`
`caring.fund`
`caring.ir`

Starts similarily
`racing.life`
`caring.co.kr`
`granic.cn`
`racing.co.uk`
`racing.io`
`cngair.com`
`ingcar.com`
`caring.capital`
`raginc.com`
`racing.se`
`caingr.com`
`caring.org`
`ncgair.com.au`
`rancig.com`
`racing.fi`
`garcin.ch`
`racing.biz`
`canrig.com`
`caring.agency`
`racing.ca`
`racing.de`
`crigan.us`
`caring.com`
`racing.agency`
`racing.academy`
`racing.app`
`racing.hu`
`racing.management`
`racing.coach`
`racing.gs`
`caring.tv`
`rignac.com`
`racing.ir`
`racing.dog`
`cignar.com`
`garcin.us`
`cargin.com`
`racing.ch`
`cargin.net`
`garcin.org`
`caring.name`
`grinca.com`
`craing.com`
`gracin.info`
`racing.media`
`gincar.ru`
`caring.co`
`irancg.com`
`caring.sg`
`agricn.net`
`grainc.net`
`agrinc.gov.za`
`racing.kz`
`racing.dk`
`cangir.com.tr`
`racing.team`
`racing.mobi`
`racing.org`
`granic.de`
`caring.be`
`caring.net`
`incgar.com`
`racing.com.tw`
`arcing.com`
`racing.gp`
`caring.community`
`racing.mx`
`carnig.com`
`gciran.com`
`racing.racing`
`crigan.com`
`racing.org.nz`
`cringa.com.br`
`caring.fund`
`racing.zone`
`racing.no`
`caring.ir`
`garnic.com`
`racing.qld.gov.au`
`racing.photos`
`craign.com`
`cgrain.se`
`granic.com`
`gracin.eu`
`racing.cl`
`rangic.com`
`racing.bet`
`racing.by`
`granic.net`
`rignac.fr`
`arcing.de`
`caring.ca`
`caring.amsterdam`
`cangir.com`
`racing.digital`
`racing.com`
`granic.us`
`racing.edu.pl`
`racing.blob.core.windows.net`
`racing.lt`

AI analysis

caring.name is configured to point to two IP addresses: 3.88.83.143 and 52.73.170.37.

IP numbers are shared by caring.name with other host names like ec2-3-88-83-143.compute-1.amazonaws.com, ec2-52-73-170-37.compute-1.amazonaws.com, and caring.com.

Four name servers, ns-212.awsdns-26.com, ns-879.awsdns-45.net, ns-1368.awsdns-43.org and ns-1874.awsdns-42.co.uk, are delegated to caring.name.

The name servers of caring.name are at least partially shared with other domains such as marriotthotels.de, hitched.ca, qumulex.com, tracorp.com, and alet.nl.

Often, the name servers ns-1774.awsdns-29.co.uk, ns-519.awsdns-00.net, ns-1090.awsdns-08.org, ns-861.awsdns-43.net, ns-1420.awsdns-49.org, ns-1761.awsdns-28.co.uk, ns-1007.awsdns-61.net, ns-1439.awsdns-51.org, ns-1958.awsdns-52.co.uk, and ns-1195.awsdns-21.org are used together.

ns-212.awsdns-26.com, ns-879.awsdns-45.net, ns-1368.awsdns-43.org, and ns-1874.awsdns-42.co.uk each point to two IP numbers: 2600:9000:5300:d400::1 and 205.251.192.212, 2600:9000:5303:6f00::1 and 205.251.195.111, 2600:9000:5305:5800::1 and 205.251.197.88, 2600:9000:5307:5200::1 and 205.251.199.82 respectively.

Five mail servers, namely 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, manage caring.name.

Domains such as gocekonline.com, metatmo.com, hairstyle.life, honeypublicrelations.com, and softwaresuggest.com share at least some mail servers partially with caring.name.

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

aspmx.l.google.com, 2607:f8b0:4004:c19::1b, and 172.253.115.26 are associated.

alt1.aspmx.l.google.com, 2a00:1450:400b:c02::1a, and 172.253.116.26 are associated.

alt2.aspmx.l.google.com, 2a00:1450:400c:c00::1b, and 173.194.76.26 are associated.

alt3.aspmx.l.google.com, 2a00:1450:4025:402::1a, and 142.250.102.27 are associated.

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

dbq