DNSWHOIS.INFO - nom.zone

Search for IP or hostnames:

nom.zone checked at 2025-09-06T03:45:01.142Z 351ms 162/162/162 100% R:15

`nom.zone`

MX	`in1-smtp.messagingengine.com`
		A	103.168.172.216^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-01.messagingengine.com`
		A	103.168.172.217^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-02.messagingengine.com`
		A	103.168.172.218^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-03.messagingengine.com`
		A	103.168.172.219^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-04.messagingengine.com`
		A	103.168.172.220^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-05.messagingengine.com`
		A	103.168.172.221^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-06.messagingengine.com`
		A	103.168.172.222^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-07.messagingengine.com`
		A	103.168.172.223^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-08.messagingengine.com`
MX	`in2-smtp.messagingengine.com`
		A	202.12.124.216^AS5716
			PTR	`stl-mx-01.messagingengine.com`
		A	202.12.124.217^AS5716
			PTR	`stl-mx-02.messagingengine.com`
NS	`riya.ns.cloudflare.com`
		A	2606:4700:50::a29f:269b ^{🇺🇸 Cloudflare}
			PTR	`riya.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c29b ^{🇨🇷 Cloudflare}
			PTR	`riya.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:229b ^{🇺🇸 Cloudflare}
			PTR	`riya.ns.cloudflare.com`
		A	108.162.194.155^{🇺🇸 Cloudflare}
			PTR	`riya.ns.cloudflare.com`
		A	162.159.38.155^Cloudflare
			PTR	`riya.ns.cloudflare.com`
		A	172.64.34.155^{🇺🇸 Cloudflare}
			PTR	`riya.ns.cloudflare.com`
NS	`syeef.ns.cloudflare.com`
		A	2606:4700:58::a29f:2cee ^{🇺🇸 Cloudflare}
			PTR	`syeef.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c3ee ^{🇨🇷 Cloudflare}
			PTR	`syeef.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:23ee ^{🇺🇸 Cloudflare}
			PTR	`syeef.ns.cloudflare.com`
		A	108.162.195.238^{🇺🇸 Cloudflare}
			PTR	`syeef.ns.cloudflare.com`
		A	162.159.44.238^Cloudflare
			PTR	`syeef.ns.cloudflare.com`
		A	172.64.35.238^{🇺🇸 Cloudflare}
			PTR	`syeef.ns.cloudflare.com`
A	2606:4700:3032::ac43:9c2f ^{🇺🇸 Cloudflare}
A	2606:4700:3034::6815:30cd ^{🇺🇸 Cloudflare}
A	104.21.48.205^Cloudflare
A	172.67.156.47^{🇺🇸 Cloudflare}

`zone`

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

Starts with same word
`nom.mk`
`nom.works`
`nom.cc`
`nom.plus`
`nom.net`
`nom.sg`
`nom.biz`
`nom.ne.jp`
`nom.is`
`nom.hk`
`nom.ca`
`nom.ni`
`nom.no`
`nom.menu`
`nom.ag`
`nom.co.jp`
`nom.com.tr`
`nom.center`
`nom.kr`
`nom.media`
`nom.fi`
`nom.ua`
`nom.am`
`nom.ae`
`nom.ma`
`nom.im`
`nom.pt`
`nom.org`
`nom.co.in`
`nom.nl`
`nom.boutique`
`nom.codes`
`nom.cz`
`nom.ai`
`nom.nu`
`nom.co.com`
`nom.cl`
`nom.fish`
`nom.pe`
`nom.se`
`nom.dk`
`nom.uy`
`nom.ch`
`nom.br`
`nom.mn`
`nom.es`
`nom.dz`
`nom.pl`
`nom.cheap`
`nom.in`
`nom.eu`
`nom.co.kr`
`nom.si`
`nom.com.ua`
`nom.be`
`nom.tr`
`nom.co.nz`
`nom.rs`
`nom.tv`
`nom.gr.jp`
`nom.name`
`nom.nom.es`
`nom.ph`
`nom.li`
`nom.github.io`
`nom.vg`
`nom.zone`
`nom.lt`

Starts similarily
`omn.be`
`mon.archi`
`onm.com.au`
`omn.red`
`mno.de`
`mon.ie`
`mon.tv`
`mon.org.br`
`mon.es`
`omn.ro`
`mon.email`
`nmo.org.nz`
`nom.codes`
`nom.cz`
`nmo.com`
`mno.co`
`mon.style`
`nmo.eu`
`mno.fr`
`mon.gov.pl`
`nom.ai`
`onm.at`
`nom.nu`
`mon.tg`
`mon.voyage`
`nmo.hu`
`nmo.dk`
`mon.sk`
`nom.co.com`
`nom.cl`
`nom.fish`
`nom.pe`
`nom.se`
`nom.dk`
`mon.tel`
`onm.se`
`nom.uy`
`mno.fi`
`nom.ch`
`nom.br`
`nom.mn`
`omn.de`
`mon.net.br`
`nom.es`
`mon.is`
`nom.dz`
`nmo.se`
`nom.pl`
`nmo.co.za`
`mno.hu`
`nom.cheap`
`mon.support`
`mon.kr`
`nom.in`
`nom.eu`
`omn.mi.it`
`mno.be`
`omn.eu`
`nom.co.kr`
`mno.pl`
`mon.in.th`
`omn.me`
`nom.si`
`mno.com.au`
`mon.mn`
`mon.lt`
`nmo.ch`
`onm.info`
`nmo.org`
`mon.world`
`nom.com.ua`
`mno.nl`
`nmo.com.ph`
`omn.cz`
`nom.be`
`mon.center`
`nom.tr`
`nom.co.nz`
`mno.it`
`omn.in`
`nom.rs`
`onm.ch`
`mno.no`
`mno.org`
`onm.nl`
`nom.tv`
`mon.co.at`
`nom.gr.jp`
`nom.name`
`mon.kz`
`omn.org`
`nom.nom.es`
`mno.link`
`mon.co`
`mno.ru`
`nom.ph`
`mno.su`
`mno.cz`
`omn.ie`
`nmo.kr`

AI analysis

nom.zone is associated with the following IP addresses: 2606:4700:3032::ac43:9c2f, 2606:4700:3034::6815:30cd, 104.21.48.205, and 172.67.156.47.

The IP numbers are shared between nom.zone and other host names such as oiledxxx.com, smtp.birthdayalarm.com, lokeel.com, vmta29.birthdayalarm.com, and vpn01-border.birthdayalarm.com.

Two name servers, riya.ns.cloudflare.com and syeef.ns.cloudflare.com, are delegated to nom.zone.

The name server setup of nom.zone is shared with other domains such as baro.dk, pamamed.com, gittesass.dk, ossirk.com, and evomin.com.

The domain nom.zone partially shares name servers with other domains such as hurtmedyczny.pl, sunshengda.com, kskamenka.com.ua, imari-ds.com, and plastiform-dallas.com.

The name servers michael.ns.cloudflare.com and trevor.ns.cloudflare.com are frequently used in conjunction with these name servers.

riya.ns.cloudflare.com points to the following IP numbers: 2606:4700:50::a29f:269b, 2803:f800:50::6ca2:c29b, 2a06:98c1:50::ac40:229b, 108.162.194.155, 162.159.38.155, and 172.64.34.155, while syeef.ns.cloudflare.com points to: 2606:4700:58::a29f:2cee, 2803:f800:50::6ca2:c3ee, 2a06:98c1:50::ac40:23ee, 108.162.195.238, 162.159.44.238, and 172.64.35.238.

Two mail servers, in1-smtp.messagingengine.com and in2-smtp.messagingengine.com, manage nom.zone.

Just like the domains danm.io, artigraf.com.pl, www.jfk.cc, moritzkornher.de, and ns2.momath.org, nom.zone also has the same mail server setup.

Other domains such as benhales.net and ajh.id.au share at least some mail servers with nom.zone.

in1-smtp.messagingengine.com points to the following eight IP numbers: 103.168.172.216, 103.168.172.217, 103.168.172.218, 103.168.172.219, 103.168.172.220, 103.168.172.221, 103.168.172.222, and 103.168.172.223. Meanwhile, in2-smtp.messagingengine.com points to two IP numbers: 202.12.124.216 and 202.12.124.217.

dbq