NSLIST.NET - yonder.events

Search for IP or hostnames:

yonder.events checked at 2025-09-08T15:52:35.662Z 202ms 135/135/135 100% R:17

`yonder.events`

NS	`ns-cloud-d1.googledomains.com`
		A	2001:4860:4802:32::6d ^{🇺🇸 Google}
			PTR	`ns-cloud-d1.googledomains.com`
		A	216.239.32.109^{🇺🇸 Google}
			PTR	`ns-cloud-d1.googledomains.com`
NS	`ns-cloud-d2.googledomains.com`
		A	2001:4860:4802:34::6d ^{🇺🇸 Google}
			PTR	`ns-cloud-d2.googledomains.com`
		A	216.239.34.109^{🇺🇸 Google}
			PTR	`ns-cloud-d2.googledomains.com`
NS	`ns-cloud-d3.googledomains.com`
		A	2001:4860:4802:36::6d ^{🇺🇸 Google}
			PTR	`ns-cloud-d3.googledomains.com`
		A	216.239.36.109^{🇺🇸 Google}
			PTR	`ns-cloud-d3.googledomains.com`
NS	`ns-cloud-d4.googledomains.com`
		A	2001:4860:4802:38::6d ^{🇺🇸 Google}
			PTR	`ns-cloud-d4.googledomains.com`
		A	216.239.38.109^{🇺🇸 Google}
			PTR	`ns-cloud-d4.googledomains.com`
MX	`aspmx.l.google.com`
		A	2607:f8b0:4004:c19::1a ^{🇺🇸 Google}
			PTR	`bk-in-f26.1e100.net`
		A	142.251.179.26^{🇺🇸 Google}
			PTR	`pd-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`
		A	2607:f8b0:4023:100f::1b ^{🇺🇸 Google}
			PTR	`yudfwra-in-f27.1e100.net`
		A	192.178.220.26^{🇺🇸 Google}
			PTR	`yudfwra-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.27^{🇺🇸 Google}
			PTR	`ws-in-f27.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.26^{🇺🇸 Google}
			PTR	`yugrqog-in-f26.1e100.net`
A	212.71.245.194^{🇬🇧 Linode AS63949}
		PTR	`212-71-245-194.ip.linodeusercontent.com`

`events`

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

Starts with same word
`yonder.co`
`yonder.cloud`
`yonder.blue`
`yonder.it`
`yonder.co.uk`
`yonder.nu`
`yonder.co.in`
`yonder.equipment`
`yonder.com`
`yonder.biz`
`yonder.net.au`
`yonder.eu`
`yonder.media`
`yonder.nl`
`yonder.info`
`yonder.events`
`yonder.ca`
`yonder.coffee`
`yonder.tv`
`yonder.net`
`yonder.be`
`yonder.life`
`yonder.co.nz`
`yonder.me`
`yonder.ru`
`yonder.fr`
`yonder.io`
`yonder.ch`
`yonder.co.za`
`yonder.cn`
`yonder.at`

Starts similarily
`erodyn.de`
`endyor.com`
`ordyne.com`
`rydeon.net`
`yonder.nu`
`rodney.net`
`redyno.com`
`yonder.co.in`
`yendor.cn`
`reyond.com.cn`
`ondrey.de`
`rodney.pl`
`yonder.equipment`
`yonder.com`
`nordey.net`
`yonder.biz`
`rodnye.ru`
`yonder.net.au`
`reydon.fr`
`rodney.im`
`yonder.eu`
`reonyd.com`
`yonder.media`
`nordey.de`
`yonder.nl`
`donery.com`
`redyon.com`
`yonder.info`
`rodney.eu`
`rodney.govt.nz`
`nordey.com`
`yonder.events`
`yorden.ru`
`rodney.de`
`rodney.it`
`renody.com`
`rodney.dk`
`royend.com`
`rodney.id.au`
`yonder.ca`
`yendor.ca`
`enydro.com`
`royden.net`
`yonder.coffee`
`rodney.cn`
`enydro.gr`
`redony.net`
`donrey.com`
`yonder.tv`
`rodney.fund`
`nyoder.net`
`ryoden.co.jp`
`dorney.net`
`rodney.com.hk`
`rodney.me.uk`
`dorney.com`
`rodney.fr`
`denryo.com`
`yonder.net`
`yonder.be`
`yonder.life`
`yonder.co.nz`
`nyeord.dk`
`erodyn.com`
`rodney.info`
`redony.eu`
`dryone.de`
`ryoden.com`
`yonder.me`
`ryoden.net`
`yonder.ru`
`reydon.com`
`yonder.fr`
`denroy.com`
`yonder.io`
`dyrone.com`
`dryone.co.il`
`yonder.ch`
`yonder.co.za`
`rodney.ru`
`rodney.co.nz`
`yonder.cn`
`yonder.at`
`neodry.com`
`rodyne.com`
`rodney.in`
`yendor.us`
`yendor.org`
`rodney.co`
`yendor.net`
`rodney.com`
`yonder.co`
`yonder.cloud`
`rodney.nl`
`yendor.fr`
`yonder.blue`
`yonder.it`
`yonder.co.uk`
`denory.com`
`nyored.com`
`doryen.com`

AI analysis

212.71.245.194 is the IP address that yonder.events points to.

IP numbers are shared between other host names, such as 212-71-245-194.ip.linodeusercontent.com, and yonder.events.

Four name servers, ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, and ns-cloud-d4.googledomains.com, are delegated to yonder.events.

The domain yonder.events partially shares its name servers with other domains such as datahubcloud.com, acquacoltura.it, prust.com, wednesdayswithbeth.com, and inlatex.com.

ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, and ns-cloud-d4.googledomains.com each point to two IP numbers: 2001:4860:4802:32::6d and 216.239.32.109, 2001:4860:4802:34::6d and 216.239.34.109, 2001:4860:4802:36::6d and 216.239.36.109, 2001:4860:4802:38::6d and 216.239.38.109 respectively.

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 yonder.events.

Other domains such as sangerhall.com, stpeters-noctorum.wirral.sch.uk, baruncorp.com, thewildrose.ca, and asabun.com share at least partially some mail servers with yonder.events.

The mail servers aspmx2.googlemail.com and aspmx3.googlemail.com are typically utilized in combination.

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 respectively: 2607:f8b0:4004:c19::1a, 142.251.179.26; 2607:f8b0:4023:100f::1b, 192.178.220.26; 2a00:1450:400c:c00::1b, 173.194.76.27; 2a00:1450:4025:402::1b, 142.250.102.26; 2a00:1450:4013:c1c::1b, 192.178.156.26.

dbq