DNSWHOIS.INFO - nodacm.com

Search for IP or hostnames:

nodacm.com checked at 2025-09-11T17:40:34.313Z 283ms 138/138/138 100% R:18

`nodacm.com`

NS	`ns1.domainking.cloud`
		A	157.120.112.237^{🇯🇵 GMOHS-CL}
		A	157.120.113.237^{🇯🇵 GMOHS-CL}
		A	157.120.114.237^{🇯🇵 GMOHS-CL}
NS	`ns2.domainking.cloud`
		A	157.120.112.237^{🇯🇵 GMOHS-CL}
		A	157.120.113.237^{🇯🇵 GMOHS-CL}
		A	157.120.114.237^{🇯🇵 GMOHS-CL}
MX	`aspmx.l.google.com`
		A	2a00:1450:400c:c02::1b ^{🇧🇪 Google}
			PTR	`wn-in-f27.1e100.net`
			PTR	`wn-in-x1b.1e100.net`
		A	108.177.15.27^{🇺🇸 Google}
			PTR	`wr-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.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	216.239.32.21^{🇺🇸 Google}
		PTR	`any-in-2015.1e100.net`
A	216.239.34.21^{🇺🇸 Google}
		PTR	`any-in-2215.1e100.net`
A	216.239.36.21^{🇺🇸 Google}
		PTR	`any-in-2415.1e100.net`
A	216.239.38.21^{🇺🇸 Google}
		PTR	`any-in-2615.1e100.net`

`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
`nodacm.com`

Starts similarily
`comand.ie`
`andcom.info`
`domanc.com`
`candom.org`
`cadmon.net`
`damcon.ru`
`dancom.us`
`macdon.org`
`donmac.net`
`adncom.eu`
`andcom.de`
`andcom.ru`
`docman.gr`
`dancom.com.my`
`dancom.eu`
`macdon.nl`
`comand.info`
`camond.com`
`camdon.com`
`comand.fr`
`adncom.com`
`mandco.net`
`codman.website`
`docman.ru`
`docman.co`
`macdon.eu`
`macdon.mobi`
`comand.co.jp`
`admcon.es`
`comand.net`
`comand.su`
`macdon.biz`
`docman.com.au`
`nadcom.co.uk`
`docman.tech`
`comand.systems`
`macdon.com`
`docman.biz`
`dnacom.de`
`docman.de`
`madcon.no`
`conadm.com`
`codman.jp`
`codman.net`
`dancom.ca`
`macdon.cn`
`admcon.net`
`comand.com`
`dcaonm.com`
`comand.co`
`damnco.fr`
`macdon.ca`
`andcom.it`
`nodmca.com`
`madcon.gr`
`comand.nl`
`dancom.ee`
`admcon.com.br`
`dancom.de`
`dancom.ru`
`dancom.it`
`mandco.ru`
`damcon.us`
`docman.ae`
`dancom.su`
`macdon.co`
`cdanmo.com.cn`
`damcon.co`
`codman.com`
`docman.nl`
`damcon.cn`
`comand.dk`
`comand.ro`
`comand.co.uk`
`cmadon.com`
`dancom.com.pk`
`docman.online`
`madcon.org`
`comand.srl`
`dancom.com`
`docman.ro`
`comand.me`
`mandco.org`
`docman.co.uk`
`andcom.co.uk`
`docman.se`
`comand.de`
`andcom.at`
`dancom.jp`
`madonc.com`
`madcon.com`
`madcon.world`
`docman.in`
`cdanmo.com`
`comand.cl`
`docman.com`
`docman.net`
`candom.ir`
`cmando.com`
`codman.us`
`damcon.eu`
`comand.ru`
`damcon.info`
`adncom.fr`
`dacomn.com`
`camdon.ca`
`comand.it`
`dancom.net.au`
`adncom.es`
`mandco.com`
`docman.us`
`dnacom.com`
`ncmoda.com`
`docman.fr`
`mandco.co.uk`
`condam.net`
`damcon.com.pk`
`comand.org`
`dnacom.nl`
`doncam.net.vn`
`dancom.mc`
`nodacm.com`
`andcom.gr`
`docman.org`
`madcon.net`
`damcon.net`
`adncom.cz`
`docman.cn`
`modcan.com`
`codman.biz`
`nadcom.hu`
`admcon.com`
`andcom.pl`
`macdon.fr`
`docman.cc`
`macdon.co.za`
`admcon.blogspot.com`
`docman.eu`
`macdon.com.br`
`codman.org`
`nodmca.net`
`ncmdao.org`
`damcon.de`
`andcom.net.pl`

AI analysis

nodacm.com is configured to point to the following four IP addresses: 216.239.32.21, 216.239.34.21, 216.239.36.21, and 216.239.38.21.

IP numbers are shared between nodacm.com and other host names, such as pelawi.com, 4sightfa.com, tardina.com, rhineriverproperties.com, and traveltrademarketing.com.

Two name servers, ns1.domainking.cloud and ns2.domainking.cloud, are assigned the delegation of nodacm.com.

Other domains, such as uchida-chemical.com, stormmachine.net, systemadvance.jp, schein.jp, and jupiter3.net, share the same name server setup as nodacm.com.

ns1.domainking.cloud and ns2.domainking.cloud both point to the same three IP numbers: 157.120.112.237, 157.120.113.237, and 157.120.114.237.

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 nodacm.com.

Other domains like bounchy.com, lacito.com, transport-sales.com, sinhalaya.net, and latlong.net.in share some mail servers, at least partially, with nodacm.com.

The mail servers aspmx2.googlemail.com, aspmx3.googlemail.com, and smtp.google.com are commonly used in conjunction with these.

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: 2a00:1450:400c:c02::1b/108.177.15.27, 2a00:1450:400b:c02::1b/172.253.116.26, 2a00:1450:400c:c00::1b/173.194.76.27, 2a00:1450:4025:402::1a/142.250.102.27, and 2a00:1450:4013:c1c::1a/192.178.156.26 respectively.

dbq