NSLIST.NET - tep.events

Search for IP or hostnames:

tep.events checked at 2025-09-11T02:19:20.807Z 177ms 135/135/135 100% R:17

`tep.events`

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:c07::1b ^{🇺🇸 Google}
			PTR	`bc-in-f27.1e100.net`
		A	142.251.111.27^{🇺🇸 Google}
			PTR	`bk-in-f27.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::1a ^{🇧🇪 Google}
			PTR	`ws-in-f26.1e100.net`
			PTR	`ws-in-x1a.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.27^{🇺🇸 Google}
			PTR	`rb-in-f27.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	198.185.159.145^{🇺🇸 SQUARESPACE}

`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
`tep.ro`
`tep.ch`
`tep.in`
`tep.wiki`
`tep.ac.id`
`tep.events`
`tep.com`
`tep.be`
`tep.org.ua`
`tep.co.jp`
`tep.fr`
`tep.ua`
`tep.uk.com`
`tep.kr`
`tep.hr`
`tep.su`
`tep.uz`
`tep.si`
`tep.de`
`tep.dp.ua`
`tep.co.ir`
`tep.io`
`tep.org`
`tep.it`
`tep.mx`
`tep.com.tw`
`tep.diskstation.me`
`tep.cz`
`tep.at`
`tep.us`
`tep.fi`
`tep.com.ua`
`tep.party`
`tep.co`
`tep.ge`
`tep.com.gr`
`tep.no`
`tep.my`
`tep.se`
`tep.azurewebsites.net`
`tep.pl`
`tep.es`
`tep.pf`
`tep.info`
`tep.co.za`
`tep.sa`
`tep.by`
`tep.eu`
`tep.org.pl`
`tep.hk`
`tep.dk`

Starts similarily
`pte.gov.co`
`tpe.gov.tw`
`pet.chu.jp`
`pet.my`
`etp.us`
`etp.kz`
`pet.io`
`tpe.de`
`tep.su`
`etp.ventures`
`etp.jp`
`pet.institute`
`pet.ac.il`
`pet.in.ua`
`etp.dp.ua`
`pte.solutions`
`tpe.org`
`tep.uz`
`pte.dk`
`pte.us`
`tep.si`
`tep.de`
`pet.salon`
`pet.lk`
`tep.dp.ua`
`pet.boutique`
`pet.gs`
`pet.ac.jp`
`pte.fr`
`pet.hu`
`pte.io`
`pte.co.in`
`tep.co.ir`
`pte.bydgoszcz.pl`
`pet.gob.pe`
`tpe.com.vn`
`etp.co.il`
`pte.de`
`pet.tel`
`ept.sn`
`pet.land`
`etp.se`
`tep.io`
`pet.lc`
`ept.su`
`pet.ch`
`pet.ac`
`pet.fm`
`tep.org`
`tep.it`
`ept.com.sa`
`etp.cn`
`tpe.ca`
`pet.si`
`pte.edu.gr`
`pet.ru`
`etp.center`
`pte.by`
`tep.mx`
`etp.in`
`tpe.fi`
`ept.pt`
`tep.com.tw`
`pet.clinic`
`pte.com`
`etp.nl`
`pet.kim`
`etp.hu`
`ept.ee`
`pte.fi`
`tep.diskstation.me`
`etp.su`
`pet.asia`
`pet.group`
`tpe.org.br`
`tep.cz`
`ept.com.tr`
`tpe.cx`
`etp.fi`
`etp.co.kr`
`ept.tn`
`pet.ee`
`ept.com.br`
`pte.com.co`
`tep.at`
`etp.holdings`
`etp.fo`
`pet.guru`
`pte.opole.pl`
`tpe.ltd`
`pet.co.nz`
`etp.lk`
`pte.biz`
`pet.jewelry`
`tpe.com`
`etp.lv`
`tep.us`
`etp.es`
`tpe.ch`
`tpe.com.ec`

AI analysis

tep.events points to the IP address: 198.185.159.145.

IP numbers are shared between tep.events and other host names such as wellhive.com, boxboro.org, dustinseabrook.com, kanopyking.net, and graceplaceschool.org.

Four name servers, ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, and ns-cloud-a4.googledomains.com, are delegated to tep.events.

Name servers of tep.events are at least partially shared with other domains such as pellein.com, oceanicgardens.com, aeroiq.com, amk.enterprises, and ucct.com.

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

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

Other domains such as derbyinformer.com, discovergroningen.com, moldesunicose.com, solutiontime.net, and contactdermatitisinstitute.com share at least some mail servers with tep.events.

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

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

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

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

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

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

dbq