`node1-1.ngcomms.net`

DNSSEC	⚠️ Not signed
A	59.100.174.105^{🇦🇺 ASN-CONNECT-NET59.100.0.0/15 AAPT Ltd}
		PTR	`node1a.ngcomms.net`
TXT	`v=spf1 a ip4:59.100.174.105 ip4:203.221.90.201 ip4:125.254.4.169 ip4:203.174....`

`ngcomms.net`

	DNSSEC	⚠️ Not signed
	NS	`dns31.cloudns.net` ⭐
	NS	`dns32.cloudns.net`
	NS	`dns33.cloudns.net`
	NS	`dns34.cloudns.net`
	MX	`cluster.ngcomms.net` ⭐
	MX	`node2a.ngcomms.net`⁽²⁰⁾
	MX	`node1a.ngcomms.net`⁽³⁰⁾
	MX	`node2b.ngcomms.net`⁽⁴⁰⁾
	MX	`node1b.ngcomms.net`⁽⁵⁰⁾
	TXT	`_jibyfbw6yhqism7x2vcv65ovl2s1r97`
	TXT	`v=spf1 -all`
	SOA	`dns31.cloudns.net`hostmaster@noggin.com.au 2025-09-08 #5

Previously MX for

ngcomms.net

DNS History

3 records (1 active, 2 former)

○A202.171.161.412008-12-01 → 2008-12-01 · 3 obs

● 2008-12-01 23:16:42
○ 2015-06-14 14:46:48
○ 2026-04-24 11:40:42

○A220.233.197.1692015-06-14 → 2016-09-14 · 4 obs

○ 2008-12-01 23:16:42
● 2015-06-14 14:46:48
● 2016-09-14 10:51:52
○ 2026-04-24 11:40:42

●A59.100.174.1052026-04-24 → 2026-04-24 · 2 obs

○ 2016-09-14 10:51:52
● 2026-04-24 11:40:42

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
ngcomms.net	dns31.cloudns.net, dns32.cloudns.net, dns33.cloudns.net, dns34.cloudns.net	8 records

✅ Authoritative Response

Server:185.136.99.100

NS records: dns31.cloudns.net, dns32.cloudns.net, dns33.cloudns.net, dns34.cloudns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ngcomms.net (unsigned zone)

⏱️ Timing

Total: 225ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`59.100.174.105`
TXT	1	`v=spf1 a ip4:59.100.174.105 ip4:203.221.`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (dns31.cloudns.net, dns31.cloudns.net, dns32.cloudns.net...)

Analysis

IP Addresses

node1-1.ngcomms.net points to a single IP address: 59.100.174.105.

Other host names such as node1a.ngcomms.net, ns1.ngcomms.net and cluster.ngcomms.net share IP numbers with node1-1.ngcomms.net.

node1-1.ngcomms.net - robtex.com