WWW.RTSAK.COM - nmnet.link

Search for IP or hostnames:

nmnet.link checked at 2025-09-08T07:17:51.765Z 550ms 193/193/193 100% R:18

`nmnet.link`

NS	`ns-77.awsdns-09.com`
		A	2600:9000:5300:4d00::1 ^{🇺🇸 Amazon}
			PTR	`ns-77.awsdns-09.com`
		A	205.251.192.77^{🇺🇸 Amazon}
			PTR	`ns-77.awsdns-09.com`
NS	`ns-773.awsdns-32.net`
		A	2600:9000:5303:500::1 ^{🇺🇸 Amazon}
			PTR	`ns-773.awsdns-32.net`
		A	205.251.195.5^{🇺🇸 Amazon}
			PTR	`ns-773.awsdns-32.net`
NS	`ns-1483.awsdns-57.org`
		A	2600:9000:5305:cb00::1 ^{🇺🇸 Amazon}
			PTR	`ns-1483.awsdns-57.org`
		A	205.251.197.203^{🇺🇸 Amazon}
			PTR	`ns-1483.awsdns-57.org`
MX	`aspmx.l.google.com`
		A	2607:f8b0:4004:c21::1b ^{🇺🇸 Google}
			PTR	`pe-in-f27.1e100.net`
		A	142.250.31.26^{🇺🇸 Google}
			PTR	`bj-in-f26.1e100.net`
NS	`ns-1778.awsdns-30.co.uk`
		A	2600:9000:5306:f200::1 ^{🇺🇸 Amazon}
			PTR	`ns-1778.awsdns-30.co.uk`
		A	205.251.198.242^{🇺🇸 Amazon}
			PTR	`ns-1778.awsdns-30.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.27^{🇺🇸 Google}
			PTR	`dj-in-f27.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::1b ^{🇳🇱 Google}
			PTR	`yugrqog-in-f27.1e100.net`
		A	192.178.156.26^{🇺🇸 Google}
			PTR	`yugrqog-in-f26.1e100.net`
A	2600:9000:24f3:800:18:491e:6b00:93a1 ^{🇺🇸 Amazon}
A	2600:9000:24f3:5000:18:491e:6b00:93a1 ^{🇺🇸 Amazon}
A	2600:9000:24f3:7200:18:491e:6b00:93a1 ^{🇺🇸 Amazon}
A	2600:9000:24f3:c400:18:491e:6b00:93a1 ^{🇺🇸 Amazon}
A	2600:9000:24f3:ca00:18:491e:6b00:93a1 ^{🇺🇸 Amazon}
A	2600:9000:24f3:d800:18:491e:6b00:93a1 ^{🇺🇸 Amazon}
A	2600:9000:24f3:de00:18:491e:6b00:93a1 ^{🇺🇸 Amazon}
A	2600:9000:24f3:f600:18:491e:6b00:93a1 ^{🇺🇸 Amazon}
A	18.160.46.38^{🇺🇸 Amazon}
		PTR	`server-18-160-46-38.iad55.r.cloudfront.net`
A	18.160.46.88^{🇺🇸 Amazon}
		PTR	`server-18-160-46-88.iad55.r.cloudfront.net`
A	18.160.46.96^{🇺🇸 Amazon}
		PTR	`server-18-160-46-96.iad55.r.cloudfront.net`
A	18.160.46.105^{🇺🇸 Amazon}
		PTR	`server-18-160-46-105.iad55.r.cloudfront.net`

`link`

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

Starts with same word
`nmnet.net`
`nmnet.com`
`nmnet.sk`
`nmnet.org`
`nmnet.cz`
`nmnet.link`

Starts similarily
`ennmt.com`
`nmnet.org`
`netnm.net`
`metnn.com`
`mnnet.co.uk`
`ntemn.com`
`mennt.is`
`mennt.com`
`tnnme.com`
`nmnet.cz`
`etmnn.com`
`entnm.com`
`nmnet.link`
`nntme.com`
`mnnet.jp`
`nemtn.com`
`entmn.com`
`mentn.com`
`mnnet.com`
`mnnet.net`
`ntmen.cn`
`nmnet.net`
`mnnet.de`
`nmnet.com`
`nmnet.sk`
`mnent.com`
`ntmen.com`
`netmn.com`
`metnn.ru`
`tenmn.blogspot.com`
`mnnet.ddns.net`
`netnm.com`
`mnnet.eu`
`mnnet.com.br`

AI analysis

The domain nmnet.link resolves to the following IP addresses: 2600:9000:24f3:800:18:491e:6b00:93a1, 2600:9000:24f3:5000:18:491e:6b00:93a1, 2600:9000:24f3:7200:18:491e:6b00:93a1, 2600:9000:24f3:c400:18:491e:6b00:93a1, 2600:9000:24f3:ca00:18:491e:6b00:93a1, 2600:9000:24f3:d800:18:491e:6b00:93a1, 2600:9000:24f3:de00:18:491e:6b00:93a1, 2600:9000:24f3:f600:18:491e:6b00:93a1, 18.160.46.38, 18.160.46.88, 18.160.46.96, and 18.160.46.105.

IP numbers are shared between nmnet.link and other host names such as comparar.net, blocksmith.xyz, dev2.scd.vma-gdps-d.wfm.global, cftest.test.report.clinic, and d15bgubwjlnv1n.cloudfront.net.

Four name servers, ns-77.awsdns-09.com, ns-773.awsdns-32.net, ns-1483.awsdns-57.org, and ns-1778.awsdns-30.co.uk, are assigned to nmnet.link.

The domain nmnet.link shares name servers, at least partially, with other domains such as leadinginterantionalattorneys.com, d1wkosmjfl1tze.cloudfront.net, tax.digitale-steuerkanzlei.haufe.de, one.lumenlearning.com, and kucoinblog.com.

The name servers ns-1910.awsdns-46.co.uk, ns-225.awsdns-28.com, ns-776.awsdns-33.net, ns-1601.awsdns-08.co.uk, ns-66.awsdns-08.com, ns-1116.awsdns-11.org, ns-611.awsdns-12.net, ns-1903.awsdns-45.co.uk, ns-560.awsdns-06.net, and ns-1006.awsdns-61.net are frequently utilized in conjunction.

ns-77.awsdns-09.com, ns-773.awsdns-32.net, ns-1483.awsdns-57.org, and ns-1778.awsdns-30.co.uk all point to two IP numbers each: 2600:9000:5300:4d00::1 and 205.251.192.77, 2600:9000:5303:500::1 and 205.251.195.5, 2600:9000:5305:cb00::1 and 205.251.197.203, 2600:9000:5306:f200::1 and 205.251.198.242 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 nmnet.link.

Some mail servers are at least partially shared between nmnet.link and other domains, such as titangroup.co, designworkscollaborative.com, trackle.de, gero-net.ch, and hdrresources.com.

The mail servers aspmx2.googlemail.com and aspmx3.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:c21::1b and 142.250.31.26, 2a00:1450:400b:c02::1b and 172.253.116.27, 2a00:1450:400c:c00::1b and 173.194.76.26, 2a00:1450:4025:402::1b and 142.250.102.27, 2a00:1450:4013:c1c::1b and 192.178.156.26 respectively.

dbq