ROBTEX.COM - mok2.com

Search for stuff

mok2.com checked at 2025-12-10T12:21:30.571Z 1767ms 118/118/118 100% R:10 allDone:true timedOut:false

`mok2.com`

	NS	`ns17.domaincontrol.com`
			A	2603:5:21c0::9^{🇺🇸 GODADDY-DNS-GLOBAL}
				PTR	`ns17.domaincontrol.com`
			A	97.74.108.9^{🇺🇸 GODADDY-DNS-GLOBAL}
				PTR	`ns17.domaincontrol.com`
	NS	`ns18.domaincontrol.com`
			A	2603:5:22c0::9^{🇺🇸 GODADDY-DNS-GLOBAL}
				PTR	`ns18.domaincontrol.com`
			A	173.201.76.9^{🇺🇸 GODADDY-DNS-GLOBAL}
				PTR	`ns18.domaincontrol.com`
	MX	`aspmx2.googlemail.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	`aspmx3.googlemail.com`
			A	2a00:1450:4009:c0f::1a^{🇬🇧 Google}
				PTR	`yulhrs-in-f26.1e100.net`
			A	192.178.223.27^{🇺🇸 Google}
				PTR	`yulhrs-in-f27.1e100.net`
	MX	`aspmx.l.google.com`
			A	2607:f8b0:4004:c23::1b^{🇺🇸 Google}
				PTR	`yuiadrs-in-f27.1e100.net`
			A	172.253.63.27^{🇺🇸 Google}
				PTR	`bi-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.26^{🇺🇸 Google}
				PTR	`dj-in-f26.1e100.net`
	MX	`alt2.aspmx.l.google.com`
			A	2a00:1450:4009:c0f::1b^{🇬🇧 Google}
				PTR	`yulhrs-in-f27.1e100.net`
			A	192.178.223.26^{🇺🇸 Google}
				PTR	`yulhrs-in-f26.1e100.net`
	A	198.202.211.1^{🇺🇸 CLOUDFLARESPECTRUM}

`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

mok2.com

mok2.co.jp

Starts similarily

okm2.com

kom2.com

2kom.fr

2kmo.com

2kom.de

k2mo.be

kom2.de

2kom.tv

ko2m.com

mok2.com

2mko.com

m2ok.com

mo2k.de

kom2.ru

kom2.immo

2kom.ru

mo2k.com

m2ko.com

mok2.co.jp

kom2.dk

AI analysis

mok2.com points to IP number 198.202.211.1.

For instance, other host names em-l.ch, p1sec.com, lumenaza.de, meri.co and trusthomecare.com share IP numbers with mok2.com.

mok2.com is delegated to two name servers: ns17.domaincontrol.com and ns18.domaincontrol.com.

mok2.com uses the same name server setup as other domains such as cake.nyc, usafis.org, reproconnect.com, lawniti.com and phoneco.us.

mok2.com shares name servers with other domains at least partially, for example npu-usa.com.

Host names with two IP numbers:

ns17.domaincontrol.com points to 2603:5:21c0::9 and 97.74.108.9; ns18.domaincontrol.com points to 2603:5:22c0::9 and 173.201.76.9.

Five mail servers handle mok2.com: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com.

mok2.com shares mail servers with other domains at least partially; for instance leemasinc.com, cgrecord.net, well-read.com, atdjapan.co.jp and miel-suisse.ch.

These mail servers are often used alongside alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx4.googlemail.com and aspmx5.googlemail.com.

Hosts with two IPs

aspmx2.googlemail.com resolves to 2a00:1450:400b:c02::1a and 172.253.116.26

aspmx3.googlemail.com resolves to 2a00:1450:4009:c0f::1a and 192.178.223.27

aspmx.l.google.com resolves to 2607:f8b0:4004:c23::1b and 172.253.63.27

alt1.aspmx.l.google.com resolves to 2a00:1450:400b:c02::1a and 172.253.116.26

alt2.aspmx.l.google.com resolves to 2a00:1450:4009:c0f::1b and 192.178.223.26

Names resolving to 2a00:1450:400b:c02::1a: aspmx2.googlemail.com and alt1.aspmx.l.google.com

Names resolving to 172.253.116.26: aspmx2.googlemail.com and alt1.aspmx.l.google.com