DNSWHOIS.INFO - layer.team

Search for IP or hostnames:

layer.team checked at 2025-09-06T03:50:52.009Z 285ms 143/143/143 100% R:15

`layer.team`

NS	`ns-cloud-c1.googledomains.com`
		A	2001:4860:4802:32::6c ^{🇺🇸 Google}
			PTR	`ns-cloud-c1.googledomains.com`
		A	216.239.32.108^{🇺🇸 Google}
			PTR	`ns-cloud-c1.googledomains.com`
NS	`ns-cloud-c2.googledomains.com`
		A	2001:4860:4802:34::6c ^{🇺🇸 Google}
			PTR	`ns-cloud-c2.googledomains.com`
		A	216.239.34.108^{🇺🇸 Google}
			PTR	`ns-cloud-c2.googledomains.com`
NS	`ns-cloud-c3.googledomains.com`
		A	2001:4860:4802:36::6c ^{🇺🇸 Google}
			PTR	`ns-cloud-c3.googledomains.com`
		A	216.239.36.108^{🇺🇸 Google}
			PTR	`ns-cloud-c3.googledomains.com`
NS	`ns-cloud-c4.googledomains.com`
		A	2001:4860:4802:38::6c ^{🇺🇸 Google}
			PTR	`ns-cloud-c4.googledomains.com`
		A	216.239.38.108^{🇺🇸 Google}
			PTR	`ns-cloud-c4.googledomains.com`
MX	`aspmx.l.google.com`
		A	2607:f8b0:4004:c1f::1b ^{🇺🇸 Google}
			PTR	`pd-in-f27.1e100.net`
		A	142.251.16.27^{🇺🇸 Google}
			PTR	`bl-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`
		A	2a00:1450:400b:c02::1b ^{🇮🇪 Google}
			PTR	`dj-in-f27.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.27^{🇺🇸 Google}
			PTR	`ws-in-f27.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.26^{🇺🇸 Google}
			PTR	`rb-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`
		A	2a00:1450:4013:c1c::1a ^{🇳🇱 Google}
			PTR	`yugrqog-in-f26.1e100.net`
		A	192.178.156.26^{🇺🇸 Google}
			PTR	`yugrqog-in-f26.1e100.net`
A	35.71.142.77^{🇺🇸 Amazon}
		PTR	`a0b1d980e1f2226c6.awsglobalaccelerator.com`
A	52.223.52.2^{🇺🇸 Amazon}
		PTR	`a0b1d980e1f2226c6.awsglobalaccelerator.com`

`team`

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

Up
`www.layer.team`

Starts with same word
`layer.digital`
`layer.no`
`layer.pl`
`layer.ru`
`layer.works`
`layer.hr`
`layer.it`
`layer.at`
`layer.com.uy`
`layer.de`
`layer.fi`
`layer.co`
`layer.info`
`layer.cl`
`layer.co.uk`
`layer.us`
`layer.guru`
`layer.marketing`
`layer.fr`
`layer.biz`
`layer.pro`
`layer.ca`
`layer.ltd`
`layer.porn`
`layer.email`
`layer.gr`
`layer.co.in`
`layer.team`
`layer.com`
`layer.style`
`layer.in`
`layer.to`
`layer.nl`
`layer.ro`
`layer.me`
`layer.si`
`layer.lv`
`layer.dk`
`layer.cz`
`layer.ae`
`layer.group`
`layer.org`
`layer.be`
`layer.co.il`
`layer.ch`
`layer.web.tr`
`layer.kz`
`layer.services`

Starts similarily
`relay.do`
`eyral.com`
`yeral.com`
`relay.com.tw`
`relay.co.za`
`elyra.org`
`early.group`
`early.biz`
`relay.ai`
`leray.info`
`relay.co`
`ayrle.net`
`relay.vc`
`layer.cl`
`leray.biz`
`relay.fi`
`arley.co.uk`
`relay.no`
`leyar.com`
`relay.es`
`yeral.net`
`eylar.com`
`relay.education`
`elrya.com`
`leary.ru`
`lyrae.org`
`layer.co.uk`
`relay.tel`
`layer.us`
`early.am`
`early.city`
`realy.nl`
`relay.kharkov.ua`
`early.co`
`relay.academy`
`early.academy`
`layer.guru`
`relay.video`
`alery.com`
`arely.de`
`layer.marketing`
`aleyr.com`
`layer.fr`
`leary.co.za`
`early.lc`
`yaler.co`
`relay.ro`
`relay.run`
`relay.spb.ru`
`alrey.com`
`relay.ie`
`relay.sumy.ua`
`layer.biz`
`relay.ks.ua`
`relay.net`
`ryale.com`
`layer.pro`
`relay.info`
`relay.net.ua`
`leary.email`
`elray.com`
`alery.fi`
`layer.ca`
`layer.ltd`
`layer.porn`
`eryla.org`
`relay.expert`
`layer.email`
`yaler.net`
`arely.cz`
`elray.de`
`relay.us`
`layer.gr`
`ylera.com`
`early.deals`
`arely.ro`
`layer.co.in`
`early.education`
`rayel.de`
`yelar.com`
`layer.team`
`elyar.co.uk`
`layer.com`
`leray.de`
`relay.io`
`relay.ch`
`relay.graphics`
`relay.house`
`lyrae.nl`
`early.be`
`layer.style`
`relay.km.ua`
`relay.nl`
`relay.com.br`
`layer.in`
`early.me`
`relay.fr`
`layer.to`
`realy.com.ua`
`elyra.com`

AI analysis

www.layer.team is a child of layer.team.

layer.team points to two IP numbers: 35.71.142.77 and 52.223.52.2.

IP numbers are shared between layer.team and other host names such as melissaneira.com, rocketmat.com, rakoo.com, perp.com, and cristian.nl.

Four name servers, ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, and ns-cloud-c4.googledomains.com, are delegated to layer.team.

Name servers of layer.team are at least partially shared with other domains such as consultnetinc.net, imoporto.pt, sweetkatiecakes.com, tennesseeaeroponicstechnologiescompany.com, and hungsty.com.

ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, and ns-cloud-c4.googledomains.com each point to two IP numbers respectively: 2001:4860:4802:32::6c, 216.239.32.108; 2001:4860:4802:34::6c, 216.239.34.108; 2001:4860:4802:36::6c, 216.239.36.108; 2001:4860:4802:38::6c, 216.239.38.108.

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 layer.team.

Other domains such as pcfix.cl, nbshops.nl, jouwweb.be, venturefactory.no, and gaflood.com share at least some mail servers with layer.team.

The mail servers aspmx2.googlemail.com and aspmx3.googlemail.com are frequently utilized in conjunction with these mail servers.

aspmx.l.google.com, 2607:f8b0:4004:c1f::1b, and 142.251.16.27 are associated with each other.

alt1.aspmx.l.google.com, 2a00:1450:400b:c02::1b, and 172.253.116.27 are interconnected.

alt2.aspmx.l.google.com, 2a00:1450:400c:c00::1b, and 173.194.76.27 are linked together.

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

alt4.aspmx.l.google.com, 2a00:1450:4013:c1c::1a, and 192.178.156.26 are related to each other.

dbq