ringdata.no - dns.ninja
ringdata.no
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns1.datacity.no ⭐ | ||||||
| A | 2a01:79a:202:4::12🇳🇴 Altibox_AS2a01:798::/29 Altibox IPv6 prefix | ||||||
| A | 79.160.32.172🇳🇴 Altibox_AS79.160.0.0/15 Altibox AS | ||||||
| PTR | 79.160.32.172.static.lyse.net | ||||||
| NS | ns2.datacity.no | ||||||
| A | 20.251.153.196🇳🇴 Microsoft20.192.0.0/10 | ||||||
| SOA | ns1.datacity.nohostmaster@datacity.no 2025-08-31 #12 | ||||||
no
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | charm.norid.no ⭐ | ||||||
| NS | i.nic.no | ||||||
| NS | njet.norid.no | ||||||
| NS | not.norid.no | ||||||
| NS | x.nic.no | ||||||
| NS | y.nic.no | ||||||
| NS | z.nic.no | ||||||
| SOA | charm.norid.nohostmaster@norid.no 2026-06-21 #45 | ||||||
Same first word
Similar names
DNS History
10 records (2 active, 8 former)
○NSns.hyp.net2015-08-14 → 2015-08-14 · 3 obs
○ 2015-12-03 13:55:58
○ 2026-06-21 13:58:10
○NSns01.zpartner.net2015-08-14 → 2015-08-14 · 3 obs
○ 2015-12-03 13:55:58
○ 2026-06-21 13:58:10
○NSns02.zpartner.net2015-08-14 → 2015-08-14 · 3 obs
○ 2015-12-03 13:55:58
○ 2026-06-21 13:58:10
●NSns1.datacity.no2026-05-17 → 2026-06-21 · 3 obs
● 2026-05-17 03:54:12
● 2026-06-21 13:58:10
○NSns1.hyp.net2015-12-03 → 2017-04-05 · 5 obs
● 2015-12-03 13:55:58
● 2017-04-05 08:09:08
○ 2026-05-17 03:54:12
○ 2026-06-21 13:58:10
●NSns2.datacity.no2026-05-17 → 2026-06-21 · 3 obs
● 2026-05-17 03:54:12
● 2026-06-21 13:58:10
○NSns2.hyp.net2015-12-03 → 2017-04-05 · 5 obs
● 2015-12-03 13:55:58
● 2017-04-05 08:09:08
○ 2026-05-17 03:54:12
○ 2026-06-21 13:58:10
○NSns3.hyp.net2015-12-03 → 2017-04-05 · 5 obs
● 2015-12-03 13:55:58
● 2017-04-05 08:09:08
○ 2026-05-17 03:54:12
○ 2026-06-21 13:58:10
○MXmx2.zpartner.net2015-08-14 → 2017-04-05 · 4 obs
● 2017-04-05 08:09:08
○ 2026-05-17 03:54:12
○ 2026-06-21 13:58:10
○A109.247.87.1602015-08-14 → 2017-04-05 · 4 obs
● 2017-04-05 08:09:08
○ 2026-05-17 03:54:12
○ 2026-06-21 13:58:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| no | z.nic.no, not.norid.no, i.nic.no, y.nic.no... | 11 records |
| ringdata.no | ns2.datacity.no, ns1.datacity.no | 3 records |
✅ Authoritative Response
Server:79.160.32.172
NS records: ns2.datacity.no, ns1.datacity.no
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 990ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | ns2.datacity.no, ns1.datacity.no |
| SOA | 1 | ns1.datacity.no hostmaster.datacity.no |
📌 Glue Records Collected
Total: 14
In-bailiwick: 11 (i.nic.no, x.nic.no, y.nic.no...)
Out-of-bailiwick: 3 (ns1.datacity.no, ns1.datacity.no, ns2.datacity.no)
Analysis
Name Servers
ringdata.no is served by two delegated name servers, ns1.datacity.no and ns2.datacity.no.
ringdata.no has the same name server delegation as a number of other domains, such as ringbillett.no, datagrid.no, digitalia.no and two more.
Hosts with two IP numbers each:
ns1.datacity.no maps to two IP addresses — 79.160.32.172 and 2a01:79a:202:4::12.
Hosts that resolve to one IP address:
ns2.datacity.no points to the IP address 20.251.153.196.