DNSWHOIS.INFO - geomap.cloud

Search for IP or hostnames:

geomap.cloud checked at 2025-09-10T17:00:26.456Z 240ms 155/155/155 100% R:15

`geomap.cloud`

NS	`dns2.technorail.com`
		A	2a00:6d42:3:2096::f:1 ^{🇮🇹 Aruba}
			PTR	`dns2.technorail.com`
		A	95.110.136.8^{🇮🇹 Aruba}
			PTR	`dns2.technorail.com`
NS	`dns.technorail.com`
		A	2a00:6d40:2:2082::f:1 ^{🇮🇹 Aruba}
			PTR	`dns.technorail.com`
		A	94.177.210.13^{🇮🇹 Aruba}
			PTR	`dns.technorail.com`
NS	`dns4.arubadns.cz`
		A	2001:15e8:104:4::d8ee ^{🇨🇿 INTERNET CZ}
			PTR	`dns4.arubadns.cz`
		A	81.2.216.238^{🇨🇿 INTERNET CZ}
			PTR	`dns4.arubadns.cz`
NS	`dns3.arubadns.net`
		A	2a00:6d41:3:206e::f:1 ^{🇮🇹 Aruba}
			PTR	`dns3.arubadns.net`
		A	95.110.220.5^{🇮🇹 Aruba}
			PTR	`dns3.arubadns.net`
MX	`uinqlh2jx2lj7pr2d2hsmscw2sboijmsdgg2q5nerrkqa4cmiuvq.mx-verification.google.com`
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::1b ^{🇳🇱 Google}
			PTR	`rb-in-f27.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.27^{🇺🇸 Google}
			PTR	`yugrqog-in-f27.1e100.net`
A	35.178.20.78^{🇬🇧 Amazon}
		PTR	`ec2-35-178-20-78.eu-west-2.compute.amazonaws.com`
A	62.149.128.151^{🇮🇹 Aruba}
		PTR	`mxd6.aruba.it`
A	62.149.128.154^{🇮🇹 Aruba}
		PTR	`mxd7.aruba.it`
A	62.149.128.157^{🇮🇹 Aruba}
		PTR	`mxd8.aruba.it`
A	62.149.128.160^{🇮🇹 Aruba}
		PTR	`mxd1.aruba.it`
A	62.149.128.163^{🇮🇹 Aruba}
		PTR	`mxd2.aruba.it`

`cloud`

	NS	`ns01.trs-dns.com`
	NS	`ns01.trs-dns.info`
	NS	`ns01.trs-dns.net`
	NS	`ns01.trs-dns.org`

Up
`www.geomap.cloud`

Starts with same word
`geomap.no`
`geomap.pl`
`geomap.ie`
`geomap.de`
`geomap.at`
`geomap.awsapps.com`
`geomap.ca`
`geomap.com.br`
`geomap.ch`
`geomap.me`
`geomap.cloud`
`geomap.co`
`geomap.us`
`geomap.ee`
`geomap.se`
`geomap.immo`
`geomap.it`
`geomap.pulawy.pl`
`geomap.com`
`geomap.fi`
`geomap.si`
`geomap.net`
`geomap.com.eg`
`geomap.com.mx`
`geomap.eu`
`geomap.nl`

Starts similarily
`geomap.com.eg`
`mapego.org`
`gamepo.ru`
`opmega.com`
`geomap.com.mx`
`gameop.net`
`pagemo.org`
`geomap.eu`
`geomap.nl`
`opgame.cn`
`pemago.com`
`mapgeo.pl`
`opgame.com`
`geomap.no`
`geomap.pl`
`gameop.hu`
`geomap.ie`
`geomap.de`
`geomap.at`
`gameop.altervista.org`
`egomap.com`
`mapgeo.com`
`mapgeo.com.pl`
`pemago.de`
`opgame.net`
`pogame.net`
`geomap.awsapps.com`
`empago.com`
`pegamo.se`
`opgame.me`
`pogame.com`
`opgame.de`
`gopema.nl`
`gameop.de`
`pegamo.com`
`pegamo.es`
`geomap.ca`
`oegpam.at`
`geopam.com`
`pegamo.de`
`geomap.com.br`
`pomega.com`
`geomap.ch`
`goemap.com`
`apogem.com`
`gameop.com`
`ampego.com`
`megapo.st`
`mapgeo.cz`
`mopage.org`
`geomap.me`
`mapego.com`
`mapgeo.ch`
`geomap.cloud`
`gamepo.com`
`geomap.co`
`geomap.us`
`gamepo.de`
`epogam.de`
`geomap.ee`
`pagemo.com`
`omegap.com`
`pagemo.net`
`pegoma.de`
`peomag.by`
`mapgeo.cl`
`pagome.de`
`gepoma.nl`
`mapgeo.sk`
`gomeap.com`
`pegamo.mx`
`geomap.se`
`geomap.immo`
`empago.de`
`geomap.it`
`pegoma.com`
`geomap.pulawy.pl`
`mopage.ch`
`geomap.com`
`mapgeo.io`
`geomap.fi`
`megapo.com`
`poagem.com`
`geomap.si`
`mopage.de`
`geomap.net`

AI analysis

www.geomap.cloud has geomap.cloud as its parent.

The DNS record geomap.cloud directs to the following IP addresses: 35.178.20.78, 62.149.128.151, 62.149.128.154, 62.149.128.157, 62.149.128.160, and 62.149.128.163.

IP numbers are shared between geomap.cloud and other host names like corsophp.com, mx.ladri.com, mx.gestim.org, mx.isoplan.org, and alvp.it.

The four name servers delegated to geomap.cloud are dns2.technorail.com, dns.technorail.com, dns4.arubadns.cz, and dns3.arubadns.net.

The domain geomap.cloud shares its name servers, at least partially, with other domains such as prosacile.com, cst4u.com, fabriziogiannini.it, pandariders.com, and solms.it.

dns2.technorail.com, dns.technorail.com, dns4.arubadns.cz, and dns3.arubadns.net point to two IP numbers each: 2a00:6d42:3:2096::f:1 and 95.110.136.8, 2a00:6d40:2:2082::f:1 and 94.177.210.13, 2001:15e8:104:4::d8ee and 81.2.216.238, 2a00:6d41:3:206e::f:1 and 95.110.220.5 respectively.

Five mail servers, uinqlh2jx2lj7pr2d2hsmscw2sboijmsdgg2q5nerrkqa4cmiuvq.mx-verification.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com, are in charge of handling geomap.cloud.

Other domains such as imaasgroup.com, leylailman.com, davidson.me, pelicanpages.com, and pristineacres.com share some mail servers, at least partially, with geomap.cloud.

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

alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, and alt4.aspmx.l.google.com point to two IP numbers each: 2a00:1450:400b:c02::1a and 172.253.116.26, 2a00:1450:400c:c00::1b and 173.194.76.26, 2a00:1450:4025:402::1b and 142.250.102.27, 2a00:1450:4013:c1c::1a and 192.178.156.27 respectively.

dbq