telemetry.cloud - dns.ninja
telemetry.cloud
| DNSSEC | ⚠️ Not signed | ||||||
| A | 103.224.90.68🇦🇺 COLO-AS-AP103.224.88.0/22 Nexcess.net, LLC | ||||||
| PTR | cloudhost-118416.au-south-1.nxcli.net | ||||||
| NS | ns1.nexcess.net ⭐ | ||||||
| A | 2607:f7c0:8001::a🇺🇸 NEXCESS-012607:f7c0:8001::/48 Proxy route | ||||||
| A | 192.240.188.188🇺🇸 NEXCESS-01192.240.188.0/24 Customer route registered by AS63956 | ||||||
| NS | ns2.nexcess.net | ||||||
| A | 2607:f7c0:8002::a🇺🇸 NEXCESS-012607:f7c0:8002::/48 Proxy route | ||||||
| A | 192.240.188.166🇺🇸 NEXCESS-01192.240.188.0/24 Customer route registered by AS63956 | ||||||
| NS | ns3.nexcess.net | ||||||
| A | 2607:f7c0:8001::b🇺🇸 NEXCESS-012607:f7c0:8001::/48 Proxy route | ||||||
| A | 192.240.188.144🇺🇸 NEXCESS-01192.240.188.0/24 Customer route registered by AS63956 | ||||||
| NS | ns4.nexcess.net | ||||||
| A | 2607:f7c0:8002::b🇺🇸 NEXCESS-012607:f7c0:8002::/48 Proxy route | ||||||
| A | 192.240.188.122🇺🇸 NEXCESS-01192.240.188.0/24 Customer route registered by AS63956 | ||||||
| SOA | ns1.nexcess.nethostmaster@telemetry.cloud serial=1633583373 | ||||||
cloud
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns01.trs-dns.com ⭐ | ||||||
| NS | ns.trs-dns.com | ||||||
| NS | ns01.trs-dns.net | ||||||
| NS | ns10.trs-dns.info | ||||||
| NS | ns10.trs-dns.org | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1781813430 | ||||||
Same first word
Similar names
DNS History
5 records (5 active, 0 former)
●NSns1.nexcess.net2026-03-04 → 2026-06-18 · 2 obs
● 2026-06-18 20:37:40
●NSns2.nexcess.net2026-03-04 → 2026-06-18 · 2 obs
● 2026-06-18 20:37:40
●NSns3.nexcess.net2026-03-04 → 2026-06-18 · 2 obs
● 2026-06-18 20:37:40
●NSns4.nexcess.net2026-03-04 → 2026-06-18 · 2 obs
● 2026-06-18 20:37:40
●A103.224.90.682026-03-04 → 2026-06-18 · 2 obs
● 2026-06-18 20:37:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cloud | ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info | - |
| telemetry.cloud | ns1.nexcess.net, ns2.nexcess.net, ns3.nexcess.net, ns4.nexcess.net | - |
✅ Authoritative Response
Server:192.240.188.122
NS records: ns1.nexcess.net, ns2.nexcess.net, ns3.nexcess.net, ns4.nexcess.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for telemetry.cloud (unsigned zone)
⏱️ Timing
Total: 761ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 103.224.90.68 |
| NS | 4 | ns3.nexcess.net, ns1.nexcess.net... |
| SOA | 1 | ns1.nexcess.net hostmaster.telemetry.clo |
Analysis
IP Addresses
telemetry.cloud has exactly one IP address — 103.224.90.68.
pertel.net, mail.adventd.com, mail.sethdiva.com plus two other host names have IP numbers in common with telemetry.cloud.
Name Servers
Four name servers handle the delegation for telemetry.cloud: ns1.nexcess.net, ns2.nexcess.net, ns3.nexcess.net and ns4.nexcess.net.
telemetry.cloud has at least partial name server overlap with other domains, such as columbuswoodworks.com, thespringsevents.com, threefeathersestate.com and two others.
It is common to find these name servers paired with the name servers ns5.nexcess.net, ns6.nexcess.net, ns7.nexcess.net and ns8.nexcess.net.
ns1.nexcess.net, ns2.nexcess.net, ns3.nexcess.net and ns4.nexcess.net all point to exactly two IP numbers each: ns1.nexcess.net → 192.240.188.188 and 2607:f7c0:8001::a; ns2.nexcess.net → 192.240.188.166 and 2607:f7c0:8002::a; ns3.nexcess.net → 192.240.188.144 and 2607:f7c0:8001::b; ns4.nexcess.net → 192.240.188.122 and 2607:f7c0:8002::b.