CF1757218927869-tsm20250906182357

DNSWHOIS.INFO - imxam.com

Search for IP or hostnames:

imxam.com checked at 2025-09-07T04:22:07.852Z 259ms 135/135/135 100% R:16

`imxam.com`

	NS	`ns-239.awsdns-29.com`
			A	2600:9000:5300:ef00::1 ^{🇺🇸 Amazon}
				PTR	`ns-239.awsdns-29.com`
			A	205.251.192.239^{🇺🇸 Amazon}
				PTR	`ns-239.awsdns-29.com`
	NS	`ns-960.awsdns-56.net`
			A	2600:9000:5303:c000::1 ^{🇺🇸 Amazon}
				PTR	`ns-960.awsdns-56.net`
			A	205.251.195.192^{🇺🇸 Amazon}
				PTR	`ns-960.awsdns-56.net`
	NS	`ns-1025.awsdns-00.org`
			A	2600:9000:5304:100::1 ^{🇺🇸 Amazon}
				PTR	`ns-1025.awsdns-00.org`
			A	205.251.196.1^{🇺🇸 Amazon}
				PTR	`ns-1025.awsdns-00.org`
	MX	`aspmx.l.google.com`
			A	2607:f8b0:4004:c1b::1a ^{🇺🇸 Google}
				PTR	`wv-in-f26.1e100.net`
			A	142.251.167.26^{🇺🇸 Google}
				PTR	`ww-in-f26.1e100.net`
	NS	`ns-1793.awsdns-32.co.uk`
			A	2600:9000:5307:100::1 ^{🇺🇸 Amazon}
				PTR	`ns-1793.awsdns-32.co.uk`
			A	205.251.199.1^{🇺🇸 Amazon}
				PTR	`ns-1793.awsdns-32.co.uk`
	MX	`alt1.aspmx.l.google.com`
			A	2a00:1450:400b:c02::1b ^{🇮🇪 Google}
				PTR	`dj-in-f27.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.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	51.15.221.184^{🇫🇷 Scaleway}
			PTR	`184-221-15-51.instances.scw.cloud`

`com`

	NS	`a.gtld-servers.net`
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`

Starts with same word
`imxam.com`

Starts similarily
`mimax.ru`
`mimax.se`
`immax.com.mx`
`mamix.de`
`miamx.fr`
`maxim.nl`
`mixam.nl`
`immax.be`
`maxim.fyi`
`maxim.tel`
`maxim.org.nz`
`miamx.com.mx`
`mamix.it`
`maxim.pe.kr`
`mimax.at`
`mixam.eu`
`mamix.com`
`maxim.ee`
`maxim.biz`
`aximm.be`
`maxim.it`
`maxim.com.tw`
`mimax.com`
`mixam.co.uk`
`maxim.co.th`
`maxim.is`
`mixam.de`
`maxim.lk`
`maxim.am`
`maxim.tv`
`imxam.com`
`mmxia.com`
`mimax.sk`
`maxim.im`
`maxim.te.ua`
`maxim.de`
`maxim.lv`
`maxim.ne.jp`
`immax.ru`
`mixma.se`
`xmmai.com`
`immax.sk`
`maxim.city`
`maxim.pt`
`maxim.co.id`
`mimax.dk`
`mamix.ru`
`maxim.cz`
`maxim.com`
`maxim.host`
`mamix.fr`
`mimax.de`
`immax.eu`
`maxim.bike`
`mamix.xyz`
`immax.at`
`mimax.it`
`maixm.com`
`maxim.co.in`
`aimxm.com`
`mamxi.com`
`maxim.lt`
`mimax.net`
`mixma.de`
`mixma.ru`
`aximm.fr`
`maxim.es`
`mimax.co.uk`
`maxim.com.ua`
`maxim.club`
`mixam.com`
`maxim.zp.ua`
`maxim.int.ru`
`xiamm.com`
`mimax.com.br`
`maxim.io`
`immax.cz`
`maxim.cat`
`maxim.se`
`mixam.co.il`
`xmami.com`
`mamix.sk`
`immax.de`
`mixam.fr`
`maxim.family`
`maxim.co.at`
`maxim.group`
`maxim.email`
`maxim.org.za`
`mimax.nl`
`maxim.pro`
`maxim.com.au`
`mimax.no`
`maxim.net`
`maxim.ru`
`maxim.me`
`mixam.fi`
`maxim.gallery`
`maxim.od.ua`
`maxim.nyc`

AI analysis

imxam.com is associated with a single IP address: 51.15.221.184.

Four name servers, ns-239.awsdns-29.com, ns-960.awsdns-56.net, ns-1025.awsdns-00.org, and ns-1793.awsdns-32.co.uk, are assigned to imxam.com.

The domain imxam.com shares name servers, at least partially, with other domains such as acronis.dk, arpakauppa.fi, yitup.com, myccwh.com, and augmented-staging-backend.autoi.co.

The name servers ns-187.awsdns-23.com, ns-949.awsdns-54.net, ns-1840.awsdns-38.co.uk, ns-1095.awsdns-08.org, ns-1671.awsdns-16.co.uk, ns-1731.awsdns-24.co.uk, and ns-647.awsdns-16.net are frequently utilized in conjunction.

ns-239.awsdns-29.com, ns-960.awsdns-56.net, ns-1025.awsdns-00.org, and ns-1793.awsdns-32.co.uk all point to two IP numbers each: 2600:9000:5300:ef00::1 and 205.251.192.239, 2600:9000:5303:c000::1 and 205.251.195.192, 2600:9000:5304:100::1 and 205.251.196.1, 2600:9000:5307:100::1 and 205.251.199.1 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 imxam.com.

Some mail servers are at least partially shared between imxam.com and other domains, such as lakewashingtonmasters.org, ttgems.com, embark.org, pfa.org.hk, and zinskin.com.

The mail servers aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com, and aspmx5.googlemail.com are frequently utilized in conjunction.

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 all point to two IP numbers each: 2607:f8b0:4004:c1b::1a and 142.251.167.26, 2a00:1450:400b:c02::1b and 172.253.116.26, 2a00:1450:400c:c00::1b and 173.194.76.27, 2a00:1450:4025:402::1a and 142.250.102.27, 2a00:1450:4013:c1c::1a and 192.178.156.26 respectively.

dbq

pybfUOf CF johedugfp 2025-09-07