tri-kobe.net - robtex.com
tri-kobe.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=1775981702 | ||||||
Same first word
Similar names
DNS History
9 records (6 active, 3 former)
●NSdns-x.sinet.ad.jp2015-06-28 → 2026-04-12 · 2 obs
● 2026-04-12 08:27:32
●NSns1-33.azure-dns.com2026-04-09 → 2026-04-12 · 3 obs
● 2026-04-09 06:27:32
● 2026-04-12 08:27:32
●NSns2-33.azure-dns.net2026-04-09 → 2026-04-12 · 3 obs
● 2026-04-09 06:27:32
● 2026-04-12 08:27:32
●NSns3-33.azure-dns.org2026-04-09 → 2026-04-12 · 3 obs
● 2026-04-09 06:27:32
● 2026-04-12 08:27:32
●NSns4-33.azure-dns.info2026-04-09 → 2026-04-12 · 3 obs
● 2026-04-09 06:27:32
● 2026-04-12 08:27:32
●NSnsnet1.tri-kobe.net2015-06-28 → 2026-04-12 · 2 obs
● 2026-04-12 08:27:32
○MXns1.tri-kobe.org2016-04-27 → 2026-04-11 · 5 obs
● 2016-04-27 01:00:44
○ 2026-04-09 06:27:32
● 2026-04-11 17:49:02
○ 2026-04-12 08:27:32
○MXnsnet1.tri-kobe.net2026-04-11 → 2026-04-11 · 3 obs
● 2026-04-11 17:49:02
○ 2026-04-12 08:27:32
○MXtrikobe-net0i.mail.protection.outlook.com2015-06-28 → 2016-01-27 · 4 obs
● 2016-01-27 03:40:54
○ 2016-04-27 01:00:44
○ 2026-04-12 08:27:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, j.gtld-servers.net... | - |
| tri-kobe.net | dns-x.sinet.ad.jp, ns3-33.azure-dns.org, ns4-33.azure-dns.info, ns1-33.azure-dns.com... | 2 records |
✅ Authoritative Response
Server:150.100.18.2
NS records: dns-x.sinet.ad.jp, ns3-33.azure-dns.org, ns4-33.azure-dns.info, ns1-33.azure-dns.com, ns2-33.azure-dns.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for tri-kobe.net (unsigned zone)
⏱️ Timing
Total: 783ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| SOA | 1 | nsnet1.tri-kobe.net sys_admn.tri-kobe.ne |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns2-33.azure-dns.net, ns2-33.azure-dns.net)
Analysis
Name Servers
tri-kobe.net is delegated to six name servers: ns1-33.azure-dns.com, ns4-33.azure-dns.info, ns2-33.azure-dns.net, nsnet1.tri-kobe.net, ns3-33.azure-dns.org and dns-x.sinet.ad.jp.
At least part of the name servers for tri-kobe.net are shared with other domains, for instance 107.153.192.in-addr.arpa, mydteprogram.com, ihs.kyushu-u.ac.jp, 114.30.133.in-addr.arpa and mvvmtoolkit.com.
Host names with six IP numbers:
dns-x.sinet.ad.jp points to: 2001:2f8:0:10::53, 2001:2f8:0:11::53, 2001:2f8:0:12::53, 150.100.18.2, 150.100.18.6 and 150.100.18.10.
Host names with two IP numbers:
ns1-33.azure-dns.com points to: 2603:1061:0:10::21 and 150.171.10.33.
ns4-33.azure-dns.info points to: 2620:1ec:bda:10::21 and 13.107.206.33.
ns2-33.azure-dns.net points to: 2620:1ec:8ec:10::21 and 150.171.16.33.
ns3-33.azure-dns.org points to: 2a01:111:4000:10::21 and 13.107.222.33.