ngcomms.net - robtex.com
ngcomms.net
net
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| 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 | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1777018721 | ||||||
Subdomains
node1a.ngcomms.net |
ns1.ngcomms.net |
soap2.ngcomms.net |
ns2.ngcomms.net |
node2.ngcomms.net |
soap.ngcomms.net |
cluster.ngcomms.net |
node2b.ngcomms.net |
node2-1.ngcomms.net |
id.ngcomms.net |
node2-2.ngcomms.net |
node2a.ngcomms.net |
node1b.ngcomms.net |
Same first word
ngcomms.net |
DNS History
17 records (9 active, 8 former)
●NSdns31.cloudns.net2026-02-15 → 2026-04-24 · 3 obs
● 2026-02-15 17:31:32
● 2026-04-24 08:46:18
●NSdns32.cloudns.net2026-02-15 → 2026-04-24 · 3 obs
● 2026-02-15 17:31:32
● 2026-04-24 08:46:18
●NSdns33.cloudns.net2026-02-15 → 2026-04-24 · 3 obs
● 2026-02-15 17:31:32
● 2026-04-24 08:46:18
●NSdns34.cloudns.net2026-02-15 → 2026-04-24 · 3 obs
● 2026-02-15 17:31:32
● 2026-04-24 08:46:18
○NSns1.ngcomms.net2008-12-01 → 2016-12-16 · 4 obs
● 2016-12-16 01:14:04
○ 2026-02-15 17:31:32
○ 2026-04-24 08:46:18
○NSns2.ngcomms.net2008-12-01 → 2016-12-16 · 4 obs
● 2016-12-16 01:14:04
○ 2026-02-15 17:31:32
○ 2026-04-24 08:46:18
●MXcluster.ngcomms.net2008-12-01 → 2026-04-24 · 2 obs
● 2026-04-24 08:46:18
○MXfirewall.noggin.com.au2015-07-23 → 2016-12-16 · 5 obs
● 2015-07-23 10:38:58
● 2016-12-16 01:14:04
○ 2026-02-15 17:31:32
○ 2026-04-24 08:46:18
○MXfirewall.noggin.com.au.ngcomms.net2008-12-01 → 2008-12-01 · 3 obs
○ 2015-07-23 10:38:58
○ 2026-04-24 08:46:18
○MXnode1-1.ngcomms.net2008-12-01 → 2008-12-01 · 3 obs
○ 2015-07-23 10:38:58
○ 2026-04-24 08:46:18
○MXnode1-2.ngcomms.net2008-12-01 → 2008-12-01 · 3 obs
○ 2015-07-23 10:38:58
○ 2026-04-24 08:46:18
●MXnode1a.ngcomms.net2015-07-23 → 2026-04-24 · 3 obs
● 2015-07-23 10:38:58
● 2026-04-24 08:46:18
●MXnode1b.ngcomms.net2015-07-23 → 2026-04-24 · 3 obs
● 2015-07-23 10:38:58
● 2026-04-24 08:46:18
○MXnode2-1.ngcomms.net2008-12-01 → 2008-12-01 · 3 obs
○ 2015-07-23 10:38:58
○ 2026-04-24 08:46:18
○MXnode2-2.ngcomms.net2008-12-01 → 2008-12-01 · 3 obs
○ 2015-07-23 10:38:58
○ 2026-04-24 08:46:18
●MXnode2a.ngcomms.net2015-07-23 → 2026-04-24 · 3 obs
● 2015-07-23 10:38:58
● 2026-04-24 08:46:18
●MXnode2b.ngcomms.net2015-07-23 → 2026-04-24 · 3 obs
● 2015-07-23 10:38:58
● 2026-04-24 08:46:18
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | g.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net... | - |
| ngcomms.net | dns31.cloudns.net, dns32.cloudns.net, dns33.cloudns.net, dns34.cloudns.net | 8 records |
✅ Authoritative Response
Server:185.136.97.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: 160ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | dns33.cloudns.net, dns32.cloudns.net... |
| MX | 5 | node2b.ngcomms.net (pri: 40), node1b.ngcomms.net (pri: 50)... |
| TXT | 2 | _jibyfbw6yhqism7x2vcv65ovl2s1r97, v=spf1 -all |
| SOA | 1 | dns31.cloudns.net hostmaster.noggin.com. |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (dns31.cloudns.net, dns31.cloudns.net, dns32.cloudns.net...)
Analysis
Hierarchy
ngcomms.net is a parent of node1a.ngcomms.net, ns1.ngcomms.net, soap2.ngcomms.net, ns2.ngcomms.net, node2.ngcomms.net and a few other host names.
Name Servers
ngcomms.net is delegated to four name servers: dns31.cloudns.net, dns32.cloudns.net, dns33.cloudns.net and dns34.cloudns.net.
ngcomms.net at least partially shares name servers with other domains, for instance wnmu.edu, iflifewerearpg.com, jacc-mi.net, positivelyaware.com and rpaengineering.co.uk.
Host names with two IP numbers: 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.
Mail Servers
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 instance id.ngcomms.net, oca21-basemx.syd1.sec2-soa.nogginoca.com and oca21-syd1-sec2-mx.xdns.nogginoca.com.
these mail servers are commonly used together with 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 that point to 59.100.174.105: cluster.ngcomms.net and node1a.ngcomms.net.
Host names that point to 125.254.4.169: cluster.ngcomms.net and node2a.ngcomms.net.