WWW.RTSAK.COM - ngcomms.net

Search for IP or hostnames:

ngcomms.net checked at 2025-09-25T23:45:11.997Z 1164ms 114/114/114 100% R:17

`ngcomms.net`

NS	`dns31.cloudns.net`
		A	2a06:fb00:1::1:100 ^{🇧🇬 ClouDNS}
			PTR	`dns31.cloudns.net`
		A	185.136.96.100^{🇺🇸 ClouDNS}
			PTR	`dns31.cloudns.net`
NS	`dns32.cloudns.net`
		A	2a06:fb00:1::2:100 ^{🇧🇬 ClouDNS}
			PTR	`dns32.cloudns.net`
		A	185.136.97.100^ClouDNS
			PTR	`dns32.cloudns.net`
NS	`dns33.cloudns.net`
		A	2a06:fb00:1::3:100 ^{🇧🇬 ClouDNS}
			PTR	`dns33.cloudns.net`
		A	185.136.98.100^{🇺🇸 ClouDNS}
			PTR	`dns33.cloudns.net`
NS	`dns34.cloudns.net`
		A	2a06:fb00:1::4:100 ^{🇧🇬 ClouDNS}
			PTR	`dns34.cloudns.net`
		A	185.136.99.100^ClouDNS
			PTR	`dns34.cloudns.net`
MX	`cluster.ngcomms.net`
		A	59.100.174.105^{🇦🇺 AAPT AS2764}
			PTR	`node1a.ngcomms.net`
		A	125.254.4.169^{🇦🇺 COMINDICO-AP}
			PTR	`node2a.ngcomms.net`
MX	`node1a.ngcomms.net`
		A	59.100.174.105^{🇦🇺 AAPT AS2764}
			PTR	`node1a.ngcomms.net`
MX	`node1b.ngcomms.net`
		A	203.221.90.201^{🇦🇺 COMINDICO-AP}
			PTR	`node1b.ngcomms.net`
MX	`node2a.ngcomms.net`
		A	125.254.4.169^{🇦🇺 COMINDICO-AP}
			PTR	`node2a.ngcomms.net`
MX	`node2b.ngcomms.net`
		A	203.174.171.249^{🇦🇺 AAPT AS2764}
			PTR	`node2b.ngcomms.net`

`net`

	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`

Up

node1a.ngcomms.net

ns1.ngcomms.net

soap2.ngcomms.net

ns2.ngcomms.net

soap.ngcomms.net

cluster.ngcomms.net

node2b.ngcomms.net

id.ngcomms.net

node2-2.ngcomms.net

node2a.ngcomms.net

node1b.ngcomms.net

Starts with same word

ngcomms.net

Starts similarily

ngcomms.net

AI analysis

ngcomms.net is a parent of node1a.ngcomms.net, ns1.ngcomms.net, soap2.ngcomms.net, ns2.ngcomms.net, soap.ngcomms.net and a few other host names.

ngcomms.net's delegation is handled by four name servers: dns31.cloudns.net, dns32.cloudns.net, dns33.cloudns.net and dns34.cloudns.net.

ngcomms.net partially shares name servers with other domains; examples include wnmu.edu, vlk-fast.com, iflifewerearpg.com, jacc-mi.net and mdynews.xyz.

these name servers are commonly used with the name servers ns-196.awsdns-24.com.

Host names with two IPs:

dns31.cloudns.net points to 2a06:fb00:1::1:100 and 185.136.96.100

dns32.cloudns.net points to 2a06:fb00:1::2:100 and 185.136.97.100

dns33.cloudns.net points to 2a06:fb00:1::3:100 and 185.136.98.100

dns34.cloudns.net points to 2a06:fb00:1::4:100 and 185.136.99.100

Five mail servers handle ngcomms.net: cluster.ngcomms.net, node1a.ngcomms.net, node1b.ngcomms.net, node2a.ngcomms.net and node2b.ngcomms.net.

ngcomms.net shares some mail servers with other domains, for example id.ngcomms.net, oca21-basemx.syd1.sec2-soa.nogginoca.com and oca21-syd1-sec2-mx.xdns.nogginoca.com.

These mail servers are often used with the mail servers firewall.noggin.com.au.

Host names with two IP numbers:

cluster.ngcomms.net points to: 59.100.174.105 and 125.254.4.169.

Host names with one IP number:

node1a.ngcomms.net points to: 59.100.174.105.

node1b.ngcomms.net points to: 203.221.90.201.

node2a.ngcomms.net points to: 125.254.4.169.

node2b.ngcomms.net points to: 203.174.171.249.

Host names pointing to 59.100.174.105: cluster.ngcomms.net and node1a.ngcomms.net.

Host names pointing to 125.254.4.169: cluster.ngcomms.net and node2a.ngcomms.net.

dbq